[00:03] <vhaarr> crimsun: downgrading those packages to -ubuntu1 and then reinstalling the nvidia driver "fixed" it here
[01:35] <_Groo_> hi/2 all
[03:11] <sirninja> I'm using the lucid alpha. Mostly everything works great, but when use the volume control keys on my laptop, it controls the pulse audio volume, not the master track volume, what happens is once I get a little below halfway pulseaudio brings the master track down to 0 so I don't hear anything. I resolved this same issue in Karmic by editing some file, I just can't remember which one. Does anybody know what file I need to edit to
[03:11] <sirninja> fix this?
[03:46] <alex_mayorga> is there a GUI to configure notifications behavior?
[03:47] <RAOF> For notify-osd?  No.
[03:47] <RAOF> There is no configuration for notify-osd notifications.
[03:49] <alex_mayorga> RAOF, that's bad I guess
[03:49] <bjsnider> DanaG has also complained about that
[03:49] <alex_mayorga> notifications won't show on top of a full screen Firefox window for example
[03:50] <alex_mayorga> I'd like to have a saying on that behavior
[03:50] <alex_mayorga> DanaG: did you reported it as bug?
[03:51] <RAOF> alex_mayorga: Urgent notifications should show on top of everything, but full-screen firefox should trigger the “disable non-urgent notifications when in a presentation” mode.
[03:51] <RAOF> So, that'd be expected & intended behaviour.
[03:52] <bjsnider> what is an urgent notification?
[03:52] <RAOF> Something that's been tagged urgent :)
[03:52] <RAOF> For example, the your-battery-is-about-to-die notification is tagged urgent.
[03:52] <RAOF> But song change notifications aren't.
[03:53] <bjsnider> restart required because of a kernel update?
[03:53] <RAOF> IIRC there are 3 priorities for notifications, but I think we only use urgent/not-urgent.
[03:53] <RAOF> I don't think that should be urgent.
[03:54] <alex_mayorga> RAOF, it would be cool if I get a saying on "urgency"
[03:54] <RAOF> You'll notice that Lucid's notify-osd has all sorts of debugging displayed?  The blue bar at the top says “low - report incorrect urgency” for most notifications; that's what this is.
[03:55] <RAOF> alex_mayorga: Possibly?  What would you actually like to do with it?
[03:55] <alex_mayorga> mail or twitter might be "urgent" for me, but powers that be decided they're "low"
[03:55] <alex_mayorga> or I might have to want to see everything even with a full-screen app
[03:56] <RAOF> At the moment, that means you don't want to use notify-osd.
[03:56] <alex_mayorga> I bet there are many more valid user cases
[03:57] <alex_mayorga> so configuration is out of the question?
[03:57] <RAOF> At the moment, yes.
[03:57] <alex_mayorga> RAOF, I'll take it as it is then
[03:57] <RAOF> alex_mayorga: Bring up your use-cases on the atayana list; maybe they'll be able to work something out.
[03:57] <alex_mayorga> is the're a config file somewhere?
[03:58] <RAOF> Notify-osd is deliberately unconfigurable at the moment to make it more likely that people will make the default behaviour right.
[03:58] <DanaG> But it my case, it instead makes things really bad.
[03:58] <DanaG> Guess how long it takes me to read the following notification... and how long it leaves it on the screen...
[03:58] <DanaG> Ambient Light Sensor:
[03:58] <DanaG> ON
[03:59] <DanaG> Takes me, oh, 1/8 to 1/4 second to read.... but it stays on the screen for 10 seconds!
[04:00] <bjsnider> they can certainly code in a correlation between length of message and length of display time
[04:00] <bjsnider> even if it's something simple like 1 second per word
[04:01] <DanaG> The default minimum-time is also way too long.
[04:01] <DanaG> It doesn't take 10 seconds to read a track-change notification (example: quodlibet).
[04:01] <DanaG> Skip 6 tracks... and it'll take a full minute before it shows the track you're actually on!
[04:03] <bjsnider> ah, i see why that doesn't apply to me. banshee doesn't support libnotify
[04:03] <bjsnider> yet
[04:03] <RAOF> Yes it does.
[04:04] <RAOF> Is yours not displaying track change notifications?
[04:04] <bjsnider> negative
[04:04] <bjsnider> but i'm on karmic
[04:05] <bjsnider> it's not in the extensions list
[04:05] <RAOF> Works on my Karmic install.
[04:06] <RAOF> It's in the “Notification area” extension; it's not an extension of its own.
[04:06] <alex_mayorga> I think is plainly arrogant to decide for users, what's important or not or how fast they should read and such
[04:06] <RAOF> It perhaps should be.
[04:06] <bjsnider> is it an extension or is it a feature?
[04:06] <bjsnider> ok, that explains it. i disable all notification area icons
[04:06] <DanaG> Yeah, arrogant is a good word.
[04:08] <RAOF> alex_mayorga: So, how would you set the importance?  Would you have each application that raises a notification have an option to set its importance?
[04:08] <RAOF> The importance has to come from _somewhere_
[04:08] <alex_mayorga> DanaG: that's how I felt the moment I discovered I didn't have any for of saying on the "feature" logic
[04:09] <bjsnider> but you don't want to expose things to users that let them screw up the system without being able to easily fix it, ie. the kde approach
[04:09] <alex_mayorga> RAOF, ask me the first time an app wants to notify
[04:09] <RAOF> What if the app has multiple different types of notifications?
[04:09] <DanaG> I do see the overly-configurable bit... check out the qtcurve settings.  At the very least, they should have the presets more easily accessible instead of buried with the oodles of settings being the main thing.
[04:09] <alex_mayorga> let me say OK I want to see these notifications, or I don't care at all
[04:10] <RAOF> “New email arrived” and “Sending email failed” and ...
[04:10] <bjsnider> DanaG, isn't everything in kde buried in oodles of options?
[04:10] <RAOF> alex_mayorga: And if you now want to turn those notifications back on?  Where's the option hidden?
[04:11] <bjsnider> probably in a giant page full of incomprehensible options
[04:11] <alex_mayorga> RAOF: System > Preferences > Notifications is what I was looking for
[04:11] <ChogyDan> are the wifi notifications changes at all?  I haven't started testing yet...
[04:11] <RAOF> alex_mayorga: And that would list every application that has ever sent at least one notification?
[04:11] <bjsnider> it would have to, to be consistent
[04:12] <alex_mayorga> RAOF: how about all the ones that are running at the moment?
[04:12] <bjsnider> it would also violate gnome's rules on these things
[04:12] <RAOF> alex_mayorga: There's no way to work that out.
[04:13] <RAOF> Apps don't register with the notification daemon, they just say “hey, display this now”.
[04:14] <alex_mayorga> it's tricky business I know, but not having any kind of saying is baffling IMHO
[04:14] <RAOF> I don't find it particularly baffling; I don't want to have to mess around with this stuff.  It should just work, and not get in the way.
[04:14] <alex_mayorga> it all started to copy growl if I'm not mistaken, and I believe growl is configurable
[04:15] <RAOF> No, notify-osd wasn't intended to copy growl.
[04:15] <alex_mayorga> RAOF, what works for one person might be intolerable to another
[04:15] <RAOF> Indeed.  But that's surprisingly uncommon.
[04:16] <RAOF> For something as basically insignificant as notifications it *should* be possible to get something that works well for 99% of users.
[04:17] <alex_mayorga> if you let me pick what notifications to receive it would work for a 100% DanaG and me might be the 1% that do want to fiddle with the details
[04:17] <RAOF> The 1% not covered can either install upstream notification-daemon or notify-osd can grow some configuration, but the goal is to get to 99% first, so people complain.
[04:17] <DanaG> My problem is that their minimum time is way too **** long!
[04:18] <RAOF> DanaG: Is there a bug report for that?
[04:18] <DanaG> 10 seconds to glance at 3 words.  Reasoning fail there.
[04:18] <RAOF> Or have you brought it up on the atayana list?  I haven't noticed, but I may have missed it.
[04:18] <DanaG> yup, digging it up now.
[04:18] <DanaG> https://bugs.launchpad.net/debian/+bug/423314
[04:19] <DanaG> Not sure why it's in Debian, and not in Ubuntu.
[04:19] <alex_mayorga> how about if the user is a kid learning to read? 10 sec for 1 word might be too little
[04:19] <DanaG> Would a little kid be using notify-send?
[04:20] <DanaG> Or are you just playing devil's advocate, or such?
[04:20] <DanaG> =þ
[04:20] <DanaG> Or whatever the term is.  Taking arguments to the extreme.
[04:20] <alex_mayorga> I participate on a foundation that tries to get Edubuntu for 1st to 6th graders, so yes
[04:21] <alex_mayorga> hopefully they will
[04:21] <DanaG> hmm, then they should make it NOT ignore the time specified!
[04:21] <DanaG> That'd fix things.
[04:21] <DanaG> There's already a solution... that they chose to throw away.
[04:22] <alex_mayorga> So I should bug every app that uses notifications for controls?
[04:22] <DanaG> No, I mean more just for notify-send, specifically.
[04:23] <RAOF> Many apps that use notifications for controls are currently broken, yes.  They should get bugs.
[04:24] <DanaG>  while (true); do notify-send this sucks;done;
[04:24] <DanaG> And watch it take 15 minutes for them all to go away.
[04:24] <RAOF> That's a part of the specification that's yet to been implemented, yes.
[04:25] <alex_mayorga> also the fact that the notification dissipate when I mouse over it is counter intuitive, but I guess SABFL knew better
[04:25] <RAOF> You have different intuition to me, clearly :)
[04:25] <DanaG> oh, and now try moving your cursor over that stream of notifications.
[04:25] <DanaG> It stops blurring.
[04:26] <DanaG> Even if you jiggle the mouse.
[04:26] <RAOF> So, that's a bug.
[04:26] <DanaG> oh, and notify-osd is reeeeeeeeeeally really tiny for me, since I use half-integer font size 8.5.
[04:27] <DanaG> Instead of 8 or 9 points, it looks more like I get, oh, 3 points.
[04:27] <DanaG> Or 4.
[04:27] <alex_mayorga> when a human is alerted to something the natural reaction is to try to respond if I'm not mistaken
[04:27] <RAOF> Wheras one of the goals of notify-osd is to not distract people.
[04:28] <DanaG> I'd say it fails at that, too. =þ
[04:28] <RAOF> It's not so bad; maybe it could be better.
[04:29] <alex_mayorga> again, if I don't get to pick how often or with what do I get distracted, then don't bother
[04:29] <DanaG> And gnome-shell takes things to an extreme.
[04:29] <RAOF> You can engage the don't bother me mode, and then you'll only get high priority notifications :)
[04:30] <DanaG> http://users.csc.calpoly.edu/~dgoyette/Screenshot.png
[04:30] <DanaG> gdm on another computer I have around here: http://users.csc.calpoly.edu/~dgoyette/GDM-Screenshot.png
[04:31] <alex_mayorga> RAOF, I meant don't bother trying ;)
[04:31] <DanaG> heh, notify-osd is like the energizer rabbit.  It just keeps going and going and <copy, paste>, <select, copy, paste>, <select more and get exponential copy-and-paste>
[04:31] <alex_mayorga> besides what's the point if I didn't choose the priorities either
[04:32] <RAOF> Because applications generally have a reasonably good idea of what the priority of their messages should be?
[04:36] <alex_mayorga> I guess I need to go through https://wiki.ubuntu.com/NotifyOSD
[04:39] <alex_mayorga> Seems like I've found a Firefox bug then, as "Popular applications that have a full-screen mode (Firefox, Totem, OpenOffice.org, Vino) should have a visible option for whether/when to inhibit non-critical notifications when a window of that application is full-screen and focused."
[04:40] <DanaG> Oh, and Flash fails, too... changing volume makes things un-fullscreen.
[04:40] <RAOF> Yay, flash :(
[04:52] <alex_mayorga> I guess I'll need to inspire myself and chip-in at https://wiki.ubuntu.com/NotifyOSD/Comments
[04:58] <alex_mayorga> after going through all the comments seems like mpt stopped answering to comments there anyway
[05:00] <RAOF> Quite possibly; you'd probably be better served contributing to the atayana list.
[05:00] <RAOF> launchpad.net/~atayana.
[05:01] <alex_mayorga> RAOF, do you think they keep an eye on this room log?
[05:04] <RAOF> No.
[05:05] <alex_mayorga> I guess I'll at least mail them the log tomorrow then
[05:05] <alex_mayorga> FWIW
[05:06] <RAOF> You can find them on #ayatana, though.
[05:09] <alex_mayorga> I see you there :)
[05:10] <alex_mayorga> RAOF, are you part of the initiative?
[05:10] <RAOF> No, not really.
[05:10] <RAOF> I'm not on the DX team, no.
[05:42] <vish> alex_mayorga: Bug #428509
[05:59] <DanaG> http://users.csc.calpoly.edu/~dgoyette/bootcharts/
[06:00] <DanaG> there's my bootchart collection.
[06:01] <bjsnider> how much webspace does cal poly give you?
[06:02] <DanaG> eh, only 300 megs for my total everything, including my roaming profile.  It used to be much more... but then they cut it way down.
[06:03] <bjsnider> did you have to ask them for it, or did they send you instructions and so forth?
[06:03] <alkisg> teeworlds complains "error while loading shared libraries: libGLU.so.1". I see that it was moved /usr/lib/libGLU.so.1 to /usr/lib/mesa/libGLU.so.1, should there be a symlink or something now that's moved?
[06:03] <alkisg> *from
[06:04] <DanaG> It's automatic -- anything in your www dir is made internet-accessible; I just set .htaccess to allow directory listing.
[06:05] <DanaG> Computer Sci and Computer Engineering majors get profiles to use on the computer labs.
[06:24] <bjsnider> DanaG, do they work on linux in any way in their studies?
[06:24] <DanaG> Yeah, all the programming stuff we do is on Linux; Windows-specific programming hasn't been taught in any of my classes, at least.
[06:25] <DanaG> They also used to have Solaris boxes; those were weird.
[06:25] <DanaG> Different interpretations of POSIX.
[06:25] <bjsnider> so in a sense, they're training you to be linux developers
[06:25] <DanaG> Or something like that.
[11:32] <BUGabundo_work> morning
[11:53] <alkisg> Firefox gives me an .xml problem when trying to display its "certificates error" page: http://pastebin.ubuntu.com/354983/
[11:54] <alkisg> (I got this by just visiting https://bugs.freedesktop.org/show_bug.cgi?id=20490 from Lucid..)
[14:02] <om26er> !test
[14:13] <BUGabundo_work> ehe om26er
[14:13] <BUGabundo_work> we dont usually go so long so quiet, right?
[14:16] <yofel> BUGabundo_work: got some time to do some bash-completion testing?
[14:17] <yofel> bug 218933
[14:19] <BUGabundo_work> yofel: nope. too much work today.... darn svn :(
[14:19] <yofel> ^^
[14:23] <BUGabundo_work> yofel: err wasnt that my bug from the other day?
[14:24] <BUGabundo_work> nope
[14:24] <BUGabundo_work> its older
[14:24] <yofel> well, I only noticed it today since Rory posted a comment and I subscribed to apport mail a while ago
[14:27] <BUGabundo_work> eheh
[14:30] <om26er> BUGabundo_work, its all quite out here
[14:30] <om26er> the kernel update that arrived today what version is it?
[14:30] <om26er> 2.6.32.x?
[14:31] <yofel> -10?
[14:31] <om26er> and if talking upstream
[14:31] <om26er> 2.6.32.3?
[14:31] <BUGabundo_work> !info linux
[14:32]  * om26er thought canonical was no longer supporting lpia
[14:32]  * yofel too
[14:33] <yofel> at least the ppa machines don't build lpia any more
[14:33] <yofel> *for lucid
[14:37] <om26er> what rhythmbox is playing becomes the status of empathy is it a feature?
[14:40] <IdleOne> om26er: yes, it's allow $application to change my status to $song that is playing.
[14:40] <IdleOne> it sucks
[14:40] <om26er> i think it was a feature of MeMenu
[14:40] <IdleOne> should be able to disable that in prefs
[14:41] <om26er> IdleOne, https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/505562
[14:43] <om26er> it was supposed to be a future work in MeMenu  https://wiki.ubuntu.com/MeMenu
[15:01] <BluesKaj> well, kde failed on my last update/upgrade and now I'm forced to use gnome . I have a long list of unmet dependencies if i try to install kubuntu-desktop. Any suggestions from you kde fans/users ?
[15:02] <yofel> as most kde packages are still FTBS I don't think there's much hope
[15:03] <yofel> I hope they'll get this sorted out till alpha2...
[15:03] <BluesKaj> I even tried to reinstall on / , but the kubuntu lucid installer on the live cd fails to launch.
[15:04] <BUGabundo_work> [14:58]  * micahg suggests pinning all PPAs at 450 to insure you choose to install a specific package vs overwriting the package from the archive
[15:04] <BUGabundo_work> [15:03]  * BUGabundo_work supports micahg idea
[15:04] <BUGabundo_work> [15:03] <BUGabundo_work> micahg: would be great if mvo would expose that via  software-sources
[15:04] <BUGabundo_work> [15:03] <BUGabundo_work> maybe right a spec for 10.10
[15:06] <yofel> and how would you pin all ppa packages? or do you want to add a pin per ppa?
[15:07] <BUGabundo_work> yofel: u can already
[15:07] <BUGabundo_work> pin all PPAs
[15:07] <yofel> huh? where?
[15:07] <BUGabundo_work> [15:00] <micahg> nasam: http://pastebin.ubuntu.com/355048/ [15:00] <micahg> add that to /etc/apt/preferences [15:00] <micahg> you might have to create the file [15:01] <micahg> or you can add it to /etc/apt/preferences.d/ppa
[15:07] <BluesKaj> yofel,  FTBS?
[15:08] <BUGabundo_work> but directly in APT db, would be great
[15:08] <BUGabundo_work> so even sources.list would have it inline
[15:09] <yofel> BluesKaj: https://edge.launchpad.net/ubuntu/+source/kdebase-workspace/4:4.3.90-0ubuntu1
[15:11] <yofel> ah, pin per origin, makes sense :)
[15:20] <joaopinto> BUGabundo_work, that will also stop you from getting updates form the ppa
[15:20] <joaopinto> from
[15:20] <hggdh> fooroom
[15:24] <meatbun> when u kill 9483 is there a way to confirm it before killig it? like print out the name of the service?
[15:25] <Pici> meatbun: Are you running Lucid?
[15:25] <meatbun> Pici: no
[15:26] <Pici> meatbun: Then you should wait for an answer in #ubuntu.  #ubuntu+1 is only for Lucid support.
[15:26] <Ian_Corne> how should we know what 9483 is?
[15:27] <meatbun> Ian_Corne: that's the process ID in ps aux
[15:28] <Ian_Corne> ok..
[15:29] <Ian_Corne> well i'll stand by Pici 's statement :)
[16:56] <knittl> yay, nvidia drivers in the archives! :)
[16:57] <yofel> yep, finally ^^
[16:58] <BluesKaj> which nvidia drivers?
[16:58] <knittl> pulling the last upgrades, then installing nvidia-common, then rebooting, then use jockey, reboot. yehaa :D
[16:59] <BluesKaj> using the glx-190 here
[17:00] <yofel> BluesKaj: the old drivers are outdated, the new 'nvidia-current' package replaces it
[17:01] <yofel> 190.53 at the moment
[17:01] <BluesKaj> but I'm not very impressed with the framerate ..about 1/20th the speed of the previous
[17:01] <knittl> btw, general question regarding ubuntu: everytime there is a kernelupdate i have to run dist-ugpgrade
[17:01] <knittl> i guess i once installed a specific version, and since then ubuntu is complaining. or is this normal behavior?
[17:02] <knittl> /var/lib/dpkg/info/nvidia-common.config: line 11: [: too many arguments
[17:02] <knittl> what's this?
[17:02] <BluesKaj> yofel, are you recommending I drop the seven machines ppa repository ?
[17:02] <yofel> BluesKaj: afaik yes, but you should ask bjsnider for more accurate infomation
[17:02] <Ian_Corne> no that's normal knittl
[17:03] <BluesKaj> I thought bjsnider was just =concerned with his flash devs
[17:03] <Ian_Corne> i meant the dist-upgrade part
[17:03] <knittl> Ian_Corne: ok :)
[17:03] <knittl> there are quotation marks missing in the nvidia-common.config script
[17:03] <knittl> should be /var/lib/dpkg/info/nvidia-common.config: line 11: [: too many arguments
[17:03] <knittl> wah
[17:04] <knittl> should be if [ "${LATEST}" != "none" ]; then in line 11
[17:08] <yofel> knittl: true
[17:08] <knittl> yofel: just posted it in #ubuntu-x
[17:08] <yofel> but another funny thing, I actually ran that script after fixing it and got: http://yofel.pastebin.com/f7b3ab945
[17:08] <knittl> please install none none?
[17:08] <yofel> intersting package, this 'none none'
[17:09] <knittl> that's what i got right now :D
[17:09] <knittl> after fixing it ...
[17:11] <knittl> yofel: will it cause any problems or can i ignore that warning?
[17:11] <yofel> dunno, first time seeing this for me tooo
[17:11] <yofel> *too
[17:14] <knittl> https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/505855 @ yofel
[17:14] <yofel> knittl: thx
[17:14] <knittl> nevertheless, i'm rebooting and then installing the drivers with jockey
[17:14] <knittl> cu
[17:21] <knittl> ubuntuone-syncdaemon is crashing constantly for me, but i couldn't find information on launchpad. any advice?
[17:21] <knittl> constantly: on every reboot
[17:25] <knittl> meh, installation of nvidia driver failed
[17:26] <knittl> 010-01-11 18:23:07,729 WARNING: modinfo for module nvidia failed: ERROR: modinfo: could not find module nvidia
[18:04] <knittl> hm, are there any issues with standby? my screen stays blank after reboot. using nvidia driver i can issue ctrl-alt-backspace to restart X
[18:04] <knittl> but that's not that comforting :D
[18:06] <ssix> hey @all
[18:16] <acicula> Ugh why does mouse integratio never work in Virtual PC :(, can Virtualbox handle amd64 on a x86 with the virtualization extenstions?
[18:35]  * cwillu_web reads the channel topic especially because things are broken
[18:37] <bjsnider> things are broken?
[18:41] <cwillu_web> bjsnider: seem to be;  updated yesterday (about 4 days since the last upgrade), and x seems to hardlock the machine (doesn't even respond to alt-sysrq-b)
[18:42] <cwillu_web> this was still under 2.6.32-9;  -10 doesn't act any differently though
[18:43] <cwillu_web> one notable feature of /var/log/xorg.0.log is something to the effect of "no mode setting driver available", which seems odd on an intel chipset :p
[18:45] <cwillu_web> added edgers at that point for no particularily good reason, and I get a partially working failsafe-x
[18:46] <cwillu_web> question: can somebody tell me the four options that failsafe-x gives you?  I can see the list well enough to click on one, but not well enough to read them
[18:48] <knittl> the first option is failsafe mode
[18:49] <cwillu_web> yep, figured that one out :)
[18:49] <cwillu_web> what are the others, do you know?
[18:49] <knittl> the last one is exit to console
[18:49] <knittl> and the other two are (don't know the order) reconfigure graphics and view logfiles
[18:50] <cwillu_web> okay, that one doesn't work, probably because of kms being broken
[18:50] <cwillu_web> reconfigure is the second one?
[18:51] <knittl> could be, but could also be the third one
[18:52] <cwillu_web> second option gives me a list of three options
[18:52] <cwillu_web> none of which seem to do anything
[18:59]  * cwillu_web tries a different approach
[18:59] <cwillu_web> where does xorg's glx module live?
[19:01] <cwillu_web> can anybody confirm that they've got /usr/lib/xorg/modules/extensions/libglx.so?
[19:02] <knittl> what's wrong with setxkbmap?
[19:02] <bjsnider> that would be a link
[19:02] <cwillu_web> bjsnider:  to what?
[19:03] <bjsnider> the actual file would be /usr/lib/xorg/modules/extensions/standard/libglx.so
[19:03] <cwillu_web> also missing :D
[19:03] <cwillu_web> okay, this narrows things down
[19:03]  * cwillu_web reinstalls xserver-xorg-core
[19:03] <cwillu_web> different crash
[19:04] <cwillu_web> [   18.093211] (EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: Input/output error.
[19:07] <cwillu_web> and aptitude reinstall xserver-xorg xserver-xorg-core xserver-xorg-video-intel, things look normal again
[19:07] <cwillu_web> odd
[19:08] <cwillu_web> I don't think I've had any crashes during upgrades
[19:12] <seren__> has anyone tried kubuntu + plymouth ?
[19:12] <seren__> does it start ? :)
[19:28] <vish> bah , all i get in Ubuntu is "mountall cannot connect to plymouth" argh!
[19:28] <seren__> I have seen people reporting it was working on ubuntu after today's update
[19:28] <seren__> I have no idea what it looks like though
[19:29] <seren__> but it is "different from fedora"
[19:43] <CShadowRun> is nvidia proprietary driver working in lucid atm?
[19:46] <seren__> using plymouth instead of usplash for kubuntu does not really work
[19:47] <seren__> X does not start
[19:47] <seren__> there is probably missing pieces
[19:49] <alkisg> CShadowRun: it works for me...
[19:49] <CShadowRun> alkisg: nice, ty
[20:30] <coz_> hey guys...out of curiosity... are nvidia drivers not working again?
[20:30] <coz_> they arent here  so I just wanted to check with you guys
[20:30] <charlie-tca> AFAIK, they are broken
[20:31] <coz_> charlie-tca,  ok   that's all I needed to know for now :)  thanks
[20:31] <charlie-tca> welcome
[20:34] <yofel> coz_: you did try to install nvidia-current ?
[20:34] <coz_> yoasif,   from hardware drivers?  no I didnt
[20:35] <coz_> yoasif,   trying now
[20:35] <yofel> coz_: I'm yofel, not yoasif :P
[20:35] <coz_> yofel,  sorry...bad tab habits
[20:35] <coz_> yoasif,  apologies  guy
[20:40] <coz_> yofel,   that driver failed to install
[20:40] <coz_> yofel,  I will try again tomorroe
[20:40] <coz_> tomorrow
[20:43] <yofel> odd, works here (amd64)
[20:44] <coz_> yofel,  according to /var/log/jockey.log    ERROR   could not find module nvidia
[20:44] <coz_> yofel,   32 bit here
[20:44] <yofel> oh, now that you mention it...
[20:45] <yofel> it builds a 'nvidia-current.ko' not 'nvidia.ko'
[20:45] <yofel> bjsnider: you here? is that a bug or will that work?
[20:46] <coz_> yofel,  any issues reported with manual install?
[20:46] <yofel> no, 'aptitude reinstall nvidia-current' works without error, but as I said, the module name is different from before
[20:48] <coz_> yofel,  then I will download the nvidia driver and try a manual install
[20:48] <yofel> I can't reboot my pc right now to test it though
[20:50] <coz_> yofel,  rebooting now to test... if this fails  I will go for manual instal
[20:50] <coz_> install
[20:50] <bjsnider> there are some issues being worked out right now that will be fixed in the next couple of days
[20:50] <coz_> bjsnider,  cool.... I want worried :)   I just checked in to see the current issues with the driver :)
[20:59] <coz_> ok  manual install  worked fine ...for now :)
[21:01] <FFForever> I know this isn't regular ubuntu support but i have been asking this a few times and no one has answered me in #ubuntu, I disabled the default messaging app and pidgin just stays in my tray, is there a way i can get the green tray icon back?
[21:03] <coz_> FFForever,  I personally couldnt help with this since I never use pidgin
[21:04] <FFForever> i prefer pidgin over empathy
[21:04] <coz_> FFForever,   try the  #pidgin channel
[21:04] <FFForever> coz_, the issue is ubuntu mods the pidgin source so they wouldn't help me or thats what they told me...
[21:04] <coz_> FFForever,  ah I see... ok  sorry about that then
[21:10] <yofel> FFForever: did you remove the indicator applet maybe?
[21:10] <FFForever> yofel, i disabled it from starting up
[21:11] <FFForever> like 2 months ago
[21:11] <yofel> hm, afaik empathy has a green tray icon, pidgin should have a while sheet of paper with a small green icon on it
[21:12] <yofel> ah, no, while message box with green circle
[21:12] <FFForever> it just sits in my task bar at the bottom with no indications of new messages :(
[21:13] <yofel> well, I'm no expert on this, I use psi in kde
[21:18] <rrva> How can I identify which process is causing heavy disk i/o at the moment+
[21:18] <yofel> rrva: iotop
[21:19] <yofel> you might want to use 'iotop -o'
[21:24] <rrva> how can I identify processes in io wait state?
[21:28] <CShadowRun> hmm, just tried to install the alpha 1 of lucid, i selected "Install", it gave me a login prompt.
[21:28] <CShadowRun> \o/
[21:30]  * charlie-tca thinks you can hit enter on that one and keep going, if it is alpha1. The daily-live won't work.
[21:31] <CShadowRun> haha, i tried ubuntu, and live...didn't think to try null
[21:33] <charlie-tca> heh
[21:33] <CShadowRun> is the partition editor stable?
[21:33] <charlie-tca> one of the images I tested accepted it, when nothing else worked
[21:33] <charlie-tca> Seems to be
[21:34] <CShadowRun> just asking because i want to install it on a separate partition, don't wanna nuke my existing install particularly :P
[21:34] <charlie-tca> I haven't nuked any yet, but my systems I install it on are test machines, and I don't worry about it
[21:34] <CShadowRun> yea, i just wanna stick it on another partition to play with
[21:35] <CShadowRun> Keeping my karmic install :)
[21:35] <CShadowRun> k gonna go play with that, brb :)
[21:35] <charlie-tca> It has worked on the ones I did it too. I had as many as 6 installs on a 40GB drive
[21:47] <CShadowRun> no luck with null as the password :(
[21:47] <CShadowRun> interestingly, it doesn't actually say incorrect password, it just goes black for a second and throws me back at the login prompt. Maybe X is crashing.
[21:51] <charlie-tca> :-(
[21:51] <CShadowRun> i'll try again with alpha2 :P
[21:51] <charlie-tca> try it on user instead
[21:52] <charlie-tca> All I could get was a little grey line for user name; so I hit enter and it went through
[21:52] <CShadowRun> haha
[21:58] <BUGabundo> evening
[21:58] <yofel> hi BUGabundo
[21:58] <BUGabundo> so Nvidia is cool again?
[21:59] <BUGabundo> cause I got a biiigggg error
[21:59] <BUGabundo> trying to install it
[21:59] <BUGabundo> $ pastebinit  /var/log/jockey.log http://paste.ubuntu.com/355196/
[21:59] <yofel> more or less
[21:59]  * BUGabundo heads to #-x
[21:59] <yofel> yeah, coz_ said too that jockey fails
[21:59] <coz_> yofel,  ah ok  :)
[21:59] <yofel> the module name changed from nvidia.ko to nvidia-current.ko
[21:59] <yofel> dunno if that was intentional
[22:00] <coz_> yofel,  well  the manula install works fine at least for now
[22:01] <coz_> manual
[22:01] <BUGabundo> (10:01:04 PM) tseliot: jockey won't work with nvidia
[22:01] <BUGabundo> (10:01:09 PM) tseliot: not yet, at least
[22:02] <BUGabundo> I guess we need to move EVERYONE to #-x
[22:02] <yofel> BUGabundo: just install the driver with aptitude, WFM
[22:02] <BUGabundo> let me see what tseliot says
[22:03] <yofel> hm, I was fine without nvidia-xconfig
[22:04] <BUGabundo> FYI
[22:04] <BUGabundo> (10:04:32 PM) tseliot: BUGabundo: ok, then just use nvidia-xconfig. As I said, it's better if you don't update your system today
[22:32]  * yofel still wonders if someone wants to test the bash-completion in bug 218933
[22:33]  * BUGabundo ducks :S
[22:34] <yofel> I never said you had to test it, and you were busy anyway :P
[22:53] <DrHalan> hows lucid doing? )
[22:53] <yofel> ok, X and KDE are broken
[22:53] <DrHalan> lol kay
[22:54] <DrHalan> isn't there already a freeze for alpha 2?
[22:54] <yofel> well, X works mostly I think, but nvidia drivers are not quite ok, the opengl libs are messed up
[22:55] <yofel> DrHalan: yes, but the mesa packages take longer than expected
[22:55] <yofel> and KDE won't build without right now
[22:55] <yofel> *without mesa
[22:56] <yofel> then again, mesa should be mostly fixed now
[22:57] <yofel> believing the X folks
[22:57] <DrHalan> oh was tehre a new mesa release or are you building from trunk?
[22:58] <BUGabundo> yofel: anyone reported kmail crash on delete?
[22:59] <yofel> BUGabundo: I get kmail crashes when opening a mail
[22:59] <BUGabundo> not here
[22:59] <yofel> but right now we have  a KDE 4.4 beta2 / rc1 mix anyway
[22:59] <BUGabundo> but I haven't upgrade last packages of it
[22:59] <BUGabundo> $ apt-cache policy kmail  Installed: 4:4.3.85-0ubuntu1
[22:59] <yofel> you should wait 1 or 2 days before you do that
[23:00] <bjsnider> nvidia and x at large will be ok after a couple of days
[23:00] <yofel> DrHalan: not sure, afair they changed something in the packageging
[23:00] <yofel> *packaging
[23:03] <yofel> hi DanaG
[23:08] <DrHalan> how is grub-pc doing. on karmic i can't boot from my software raid yet have to use super-grub-cd to boot
[23:45] <Barridus_> fail
[23:47] <yofel> o.O
[23:47] <BUGabundo> HAIL
[23:48] <yofel> ^^