[10:06] <hyperair> what's the correct target for issue regarding X and resuming?
[10:06] <hyperair> from hibernate/suspend
[10:12] <bryyce> hyperair, 'linux' is usually a good starting point
[10:13] <hyperair> bryyce: no, i think this is purely X. there are some vt-switching issues, and after that, the wallpaper changes to some hideous black and white weird looking thing
[10:14] <hyperair> bug #510004
[10:14] <hyperair> that
[10:15] <tjaalton> nvidia-graphics-driver-180 then
[10:15] <tjaalton> actually, just n-g-d
[10:16] <bryyce> ah, yeah with -nvidia the kernel team probably couldn't help you any more than we could
[10:16] <hyperair> indeed
[10:16] <hyperair> i figured as much
[10:17] <bryyce> night
[10:18] <hyperair> night
[10:38] <geser> is there a bug about libgl1-mesa-glx being sort of unusable on the buildds?
[10:42] <tseliot> geser: what do you mean?
[10:42] <geser> tseliot: e.g. http://launchpadlibrarian.net/38095009/buildlog_ubuntu-lucid-i386.octave-ad_1.0.6-3_FAILEDTOBUILD.txt.gz
[10:43] <geser> this also happens with -0ubuntu7 (tested in my pbuilder)
[10:43] <geser> although the postinst calls ldconfig, it only triggers it's run at the end (which seems to be to late)
[10:44] <geser> from a look at /sbin/ldconfig this might work: "LDCONFIG_NOTRIGGER=y ldconfig" in postinst
[10:45] <geser> this should force ldconfig being run right now and making libGL.so.1 available for the following packages being configured
[10:45] <tseliot> yes, I was about to say the same about ldconfig. Let me check LDCONFIG_NOTRIGGER
[10:46] <tseliot> yes, that should be our problem
[10:55] <tseliot> geser: I'll try to build the package in my chroot with export LDCONFIG_NOTRIGGER=y
[11:13] <tseliot> bummer, it's building without notrigger here...
[11:13] <tseliot> which I guess is why you mentioned the problem as affecting buildds
[12:25] <tseliot> geser: ok, I've just uploaded 7.7-0ubuntu8. Please test octave3.2 again when mesa is published
[12:59] <geser> tjaalton: in case you didn't notice: libxcb got finally synced today (it triggered a bug in LP which made the previous sync attempts fail)
[14:11] <geser> tseliot: octave-ad build successfully with mesa 7.7-0ubuntu8
[14:12] <tseliot> \o/
[14:12] <tseliot> geser: thanks for testing
[15:53] <tseliot> jbarnes: any ideas as to what can be causing this? http://pastebin.ubuntu.com/359587/
[15:53] <tseliot> when switching users (i.e. when launching an additional X session on a different tty)
[15:54] <tseliot> s/launching/trying to launch/
[17:55] <tjaalton> geser: yep I noticed, nice
[19:04] <Sarvatt> wow, didnt notice we had all these plymouth themes installed as well in lucid, solar looks great but the progress bar is a little messed up
[19:05] <Sarvatt> sudo plymouth-set-default-theme solar --rebuild-initrd  incase anyone else hasn't seen it :D
[19:26] <geser> are there any screenshots available for all themes?
[19:28] <Sarvatt> just found a few here http://www.webupd8.org/2010/01/look-at-ubuntu-lucid-plymouth-themes.html
[19:31] <Sarvatt> tseliot: is it me or does that look like plymouths fault?
[19:32] <superm1> sebner, https://bugs.edge.launchpad.net/ubuntu/+source/plymouth/+bug/506717/comments/6
[19:32] <superm1> so it should be working with non-KMS.  It just Isn't
[19:45] <Sarvatt> its tring to load a second display on vt7 and plymouth only drops drm master on vt switch?
[20:28] <Sarvatt> all this time and it just now hit me to put the intel package on hold and use everything else from edgers :D i've been slacking with the updates lately because I havent been able to use it in months
[20:29] <Sarvatt> was syncing evdev with origin/ubuntu even though we're just syncing debian so I missed alot of fixes there
[20:31] <Sarvatt> anyone here been able to use intel 2.10+ on 945 or under successfully?
[20:31] <jcristau> i haven't even tried since you said it was broken :)
[20:32] <Sarvatt> it's broken here and for at least 15 other people that I know are using edgers but I haven't asked if anyone was actually able to use it so I'd be interested to know :D
[20:32] <Sarvatt> I'll put a note on edgers asking for feedback
[20:33] <jcristau> i was away from my 945 from christmas until yesterday though.  maybe i can try later.
[20:34]  * Duke` checks his driver version
[20:35] <Sarvatt> pretty sure 965+ doesn't have the problem because I know alot of people using edgers with that that arent complaining and never seen any reporters that werent using 915 or 945
[20:36] <Sarvatt> I know you are having the problem as well on 945 with 2.9.99.902+ Duke` :D
[20:36] <Sarvatt> you were the one that tipped me off that libdrm from 11-25 actually works
[20:36] <Duke`> 2.10
[20:36] <Duke`> unfortunately I lost my 11-25 packages, I dunno how :(
[20:36] <Sarvatt> you are using 2.10 now and not getting the errors? or have you been putting up with it for all this time?
[20:37] <Duke`> I have the execbuf error EVERY day
[20:37] <Duke`> I had it some hours ago
[20:37] <Sarvatt> man you have some perserverence
[20:37] <Duke`> every day I pray for the holy new version fixing it :D
[20:38] <Sarvatt> you should just grab the 2.9.1 from lucid and rebuild it for karmic and put a hold on that package
[20:39] <Sarvatt> change the xserver-xorg-dev (>= 2:1.7), line in debian/control to xserver-xorg-dev (>= 2:1.6), first
[20:39] <Duke`> if I would like a stable version, I would just disable edgers for some time and use karmic packages
[20:39] <Duke`> I feel that there is not a lot of activity around this bug at Intel. I hope I'm wrong
[20:40] <Sarvatt> for sure I agree with you :D
[20:43] <Sarvatt> it's incredibly frustrating with how its so random though, cant believe you've put up with it for almost 2 months
[20:45] <Duke`> yeah
[20:45] <Duke`> but someone must do the testing job ;-)
[20:45] <Sarvatt> i wont be updating mesa on karmic anymore probably Duke` :(
[20:45] <Duke`> ah?
[20:46] <Duke`> well, I'll just like an upload when the fix is released
[20:46] <Duke`> at least
[20:46] <Sarvatt> it's changed so much in lucid we cant just use the scripts to update it, and i dont use karmic
[20:46] <Duke`> oh
[20:47] <Duke`> well lucid release is in 3 months, it's not too far ;p
[21:26] <bryyce> btw, I've flagged the exec buf bug to Intel and identified it as a blocker bug that must be fixed before we move to 2.10
[21:26] <bryyce> however, they're blocked by need for additional debugging information
[21:26] <bryyce> there is a debugging patch posted to the bug report, so it sounds like they just need someone to work with them on gathering the right data
[21:27] <bryyce> unfortunately I don't have a 945 that I can do the testing on, and haven't reproduced the issue on !945