[04:41] <Sarvatt> sorry for the build failure mail spam, obviously only test building on i386 before uploading to the backports ppa's isn't enough
[05:59] <bryceh> Sarvatt, hey do you know why that xrecord crash bug came to be?  did chase's earlier xrecord fix expose the bug or something?
[05:59] <bryceh> I'm going through all the recent X crash reports and it appears like 80% of them at least are dupes of this one
[08:30] <bryceh> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/774978/comments/38
[08:30] <ubot4> Launchpad bug 774978 in xserver-xorg-input-synaptics (Ubuntu Natty) (and 1 other project) "xserver crashes in RecordAReply when XRecord is enabled in syndaemon (affects: 188) (dups: 34) (heat: 640)" [Undecided,Fix committed]
[08:42] <bryceh> cnd, Sarvatt, ^^ please review, you might have more to add to the story
[10:15] <braintorch> Hello. Will there be 270.41.19 nvidia driver for lucid in ubuntu-x repo? Somewhat nasty bug affecting flash video playing was fixed in this version.
[10:19] <bryceh> braintorch, probably in xorg-edgers, maybe in x-updates.  probably not in natty-updates tho.
[10:28] <braintorch> I see it was packaged for oneric and for natty in x-updates but not for maveric or lucid. That's why I interested.
[10:35] <jussi> tjaalton: bah, the original bug I mentioned (about the screen not coming back from sleep) is still there. I guess I didnt wait long enough last time :/
[10:36] <jussi> also, saving the default settings in kubuntu doesnt actually save it, it always reboots with the same settings.
[12:00] <tjaalton> jussi: ok, try with .39-rc3 to see if it's fixed there
[15:45] <cnd> bryceh, wow, that XRecord stuff looks like a festering wound
[15:45] <cnd> good analysis in the bug comment :)
[15:45] <cnd> so are we going to patch up g-s-d to not use -R?
[15:46] <jcristau> do we enable record by default?
[15:47] <jcristau> maybe that's not such a great idea...
[15:47] <cnd> jcristau, apparently g-s-d now tells syndaemon to use XRecord instead of polling the keyboard state
[15:48] <jcristau> record sounds like it makes keyloggers kind of trivial
[15:50] <cnd> heh
[15:52] <Sarvatt> syndaemon itself uses record by default if its built with support for it
[15:52] <Sarvatt> -R doesn't have any affect in that case :(
[15:56] <Sarvatt> bryceh: http://kernel.ubuntu.com/~sarvatt/sandybridge-10.04-live/ \o/
[16:00] <tjaalton> yeah, I tested that and it worked here too
[16:01] <tjaalton> glxgears acted funny though
[16:01] <tjaalton> when trying to move the window
[16:03] <Sarvatt> stutters?
[16:04] <Sarvatt> you should see it with current git if you think thats bad, at least the gears dont flash teal and yellow while it happens
[16:05] <tjaalton> heh ok
[16:05] <Sarvatt> tjaalton: oh you're on a GT1, i've got to try it out on that
[16:05] <Sarvatt> wouldn't be surprised if mesa 7.10.2 is messed up there
[16:08] <Sarvatt> tjaalton: btw you probably want to use i915.semaphores=1 on that thing..
[16:09] <Sarvatt> it'll fix the stuttering if thats the problem you had
[16:09] <tjaalton> seems to be on natty too
[16:10] <tjaalton> which is hardly surprising
[16:13] <Sarvatt> http://dl.dropbox.com/u/1117258/VID_20110608_111152.m4v
[16:15] <Sarvatt> tjaalton: try vblank_mode=0 glxgears if you want some real fun
[16:21] <tjaalton> riight, ~1000 fps, though it looks like ~2
[16:22] <Sarvatt> check dmesg
[16:23] <tjaalton> heh
[16:26] <Sarvatt> ricotz: i dont think the 3.0 kernel is going to work without a module-init-tools update too so probably not a good idea to copy that to edgers right away
[16:36] <ricotz> Sarvatt, ok, so the updated module-init-tools package from oneiric isnt working yet? havent tried to building 3.0 myself yet
[16:38] <ricotz> Sarvatt, looks like the m-i-t update works - ppa:apw/red
[16:38] <Sarvatt> cool, looks like it went into oneiric directly this morning too
[16:39] <Sarvatt> https://lists.ubuntu.com/archives/oneiric-changes/2011-June/002607.html
[16:39] <ricotz> ;)
[16:39] <apw> Sarvatt, we are still sorting out the numbering... the last bits are being fixed now
[16:40] <apw> be careful about uploading the meta to the xorg-edgers without it being fixed
[16:40]  * Sarvatt nods
[16:40] <ricotz> there will be no meta in edgers anyway
[16:40] <Sarvatt> haven't been putting meta's in edgers as of yet
[16:40] <apw> we are hedging our bets right now as to whether to use 3.0 or 3.0.0 for sanity
[16:40] <apw> and so uploading 3.0 kernel with a 3,0,0 meta as unexpectedly we can switch either way that way going forward
[16:41] <Sarvatt> i'm probably a little too cautious about keeping things in there stable :P
[16:41] <ricotz> apw, you are doing an abi bump for stable releases anyway, so perhaps using the stable release version as base?
[16:42] <apw> ricotz, yeah we simply hedging.  i think we'd like to call it 3.0 but module-init-tools is just the tip of the iceberg on whats fooked by the number change
[16:42] <ricotz> this would mean using 3.0.0, 3.0.1, ...
[16:42] <apw> ps all gets angry too
[16:42] <apw> ricotz, yet a third option indeed
[16:43] <ricotz> so 3.0.0-0.1, {stable version}-{ubuntu-revision}
[16:44] <ricotz> just an idea ;)
[16:44] <apw> that does force us to bump abi whenever we take stable which we don't currently always do
[16:44] <Sarvatt> ugh
[16:44] <ricotz> apw, ok, i though it is needed quite everytime
[16:44] <apw> i know, which is why we are hedging :)
[16:45] <apw> ricotz, there have been a number of .7 is huge, .8 is one patch to unbreak .7 which is not a bumper
[16:45] <ricotz> alright
[16:47] <Sarvatt> it would be nice to have the version number reflect reality even though thats a pain in the butt. i constantly get asked by upstreams what 2.6.38-7 maps to for example :P
[16:56] <ricotz> Sarvatt, +1, right, using the actual full upstream version in some kind would be nice
[16:58] <jcristau> Sarvatt: it's never going to map exactly to an upstream version anyway
[16:58] <jcristau> each distro kernel is patch in its own spethial way
[16:58] <jcristau> *patched
[17:09] <Sarvatt> sheesh, mesa tarball is bigger than it was with demos in it now
[17:17] <ricotz> Sarvatt, switching to 3.0 and using bz2 might be nice ;)
[20:43] <cnd> bryceh, Sarvatt: I'm trying out oneiric, but every time I log in I get "Oh no! something wrong has happened." message
[20:43] <cnd> do you know how to get around that?
[20:48] <Sarvatt> cnd: i've never even heard of that dialog
[20:48] <Sarvatt> hmm
[20:49] <cnd> it's this really terrible window that comes up
[20:49] <Sarvatt> apparently its a gnome 3 one
[20:49] <cnd> there's no information
[20:49] <cnd> I have no clue what to do to debug it
[20:49] <cnd> 0 info
[20:49] <cnd> I understand the point, but really it's more aggravating than anything
[20:50] <Sarvatt> looks like it's a gnome-menus problem when it happened in fedora
[20:51] <cnd> I think it manifests from many different error paths...
[20:51] <cnd> I just want to get behind it
[20:51] <cnd> I can relaunch services and stuff if I need
[20:51] <cnd> and it shouldn't be happening when I try a non-gnome 3 session
[20:54] <bryceh> I haven't ever seen that either
[21:00] <Sarvatt> i think this is the longest i've ever gone without updating to the devel release on all any of my systems, not looking forward to gnome 3 pain..
[21:00] <Sarvatt> but i guess its time, starting an upgrade
[21:01] <Sarvatt> cnd: 
[21:01] <Sarvatt> Jun 02 06:24:07 <chrisccoulson>	i did try gnome-shell from our archive last night
[21:01] <Sarvatt> Jun 03 03:37:15 <chrisccoulson>	so, this silly window that takes up my entire screen when i dock my laptop,and shows a sad face telling me i need to log out is actually from gnome-session
[21:01] <Sarvatt> Jun 03 04:00:27 <seb128>	chrisccoulson, by reading gnome-session code that screen is displayed when the session fails to respawn something that quited
[21:01] <Sarvatt> Jun 03 04:03:35 <seb128>	run gnome-session --debug maybe and dock your laptop and look at the session log
[21:01] <chrisccoulson> we really need to kill that error, it's totally ridiculous
[21:03] <cnd> yeah
[21:03] <cnd> Sarvatt, thanks for digging that up!
[21:04] <cnd> oh wait
[21:04] <cnd> I get that error at login
[21:04] <cnd> how do I enable debug for gnome-session like that?
[21:07] <Sarvatt> is there nothing that stands out in ~/.xsession-errors?
[21:08] <cnd> Sarvatt, http://paste.ubuntu.com/622020/
[21:08] <cnd> doesn't look like it :(
[21:13] <Sarvatt> i'm seriously going to regret this upgrade tomorrow no doubt :)
[21:17] <cnd> heh
[21:18] <cnd> I wonder if it's possible to use the natty gnome-session
[21:23] <cnd> I was able to downgrade
[21:24] <cnd> lets see if it helps
[21:25] <cnd> alright, progress
[21:25] <cnd> but I don't have a window decorator...
[22:49] <pentarex> hey guys I'm having some issue with HP G62 with two videocards, INTEL and ATI RADEON 5470, I've installed kubuntu 11.04 and now I cant log in - I see the log in sign, then the screen goes black(blank) and the fan goes off
[22:49] <pentarex> can anyone help me please
[23:23] <Sarvatt> bryceh, RAOF: they snuck up like ninjas when we were drinking :P http://photos.pixoulphotography.com/Events/UDS-Oneiric/17103699_kzzLF6/1/1296062040_6SsNNkg#1296215224_r26Dfnz
[23:51] <RAOF> Sarvatt: Yeah, I know.  I look plenty stupid in the UDS photo's I've found of myself :)