[18:48] <bryce> NOUVEAU(0): [drm] failed to set drm interface version.
[18:49] <bryce> mlankhorst, ^^ ideas on that one?
[18:49] <bryce> nouveau drm driver appears to have loaded ok according to dmesg but X quits with that error
[18:51] <mlankhorst> forgot, google is your friend probably, EOD for me
[18:52] <mlankhorst> race condition with plymouth iirc?
[18:53] <bryce> ah
[18:53] <bryce> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/966871
[19:41] <bjsnider> what's the deal with this: http://www.phoronix.com/scan.php?page=news_item&px=MTI5MjI
[19:41] <bjsnider> first time i've heard of software being rejected because there's "too much functionality"
[21:53] <bryce> tjaalton, 1103345 is duped to 1099054 but the stack traces look different, so I'm thinking they're not dupes?
[21:55] <tjaalton> bryce: it's the same user, so thought it's dupe anyway
[21:57] <tjaalton> and 1115177 is probably a lightdm bug
[21:58] <tjaalton> those started during quantal
[21:58] <tjaalton> it's not behaving well with current plymouth
[21:58] <tjaalton> I booted my ivb today after moving it under the new desk, and it took a few tries to actually get X running after boot
[21:58] <tjaalton> stock quantal..
[21:59] <tjaalton> the error message in xserver log can vary
[22:00] <tjaalton> lightdm is doing tricks with plymouth, so that it can start the xserver before plymouth has exited or such
[22:01] <bryce> uff
[22:01] <tjaalton> so 1.4.0 made some racy changes that you can hit with a fast machine + ssd
[22:01] <bryce> tjaalton, happen to know if there's a master bug about that?
[22:01] <tjaalton> the one you found with google, bug 982889 :)
[22:02] <bryce> heh
[22:02] <tjaalton> the description is actually misleading, since that's what lightdm does..
[22:02] <bryce> well, guess what I'm asking is does someone else already know about this?  e.g. robert?
[22:02] <tjaalton> he's never around :)
[22:02] <tjaalton> wrong tz for me
[22:03] <tjaalton> not sure if he knows
[22:03] <bryce> ok, then I'll follow up with him when I see him
[22:03] <bryce> we appear to have several of these bugs reported
[22:04] <tjaalton> oh yes
[22:04] <tjaalton> good thing that it doesn't affect 12.04.2
[22:04]  * bryce nods
[22:06] <bryce> think bug 1065288 is the same thing?
[22:07] <bryce> tjaalton, also am I correct in assuming that the DRM needs to hit Initialized *before* the xserver starts?  Versus just before DRI2 is initialized?
[22:07] <bryce> one of the bugs showed DRM after DRI2, the other showed it before DRI2 but after xserver started
[22:08] <tjaalton> yeah that's probably a dupe
[22:09] <tjaalton> haven't really dug into these.. tried once but then my head said no after trying to make some sense of how it's supposed to run
[22:09] <bryce> hmm, maybe not with 1065288, it doesn't follow the pattern; X is starting after DRM
[22:09] <bryce> tjaalton, yeah andy and I tried back a few releases ago and tossed our hands up.
[22:09] <tjaalton> heh
[22:10] <bryce> but if it's true that DRM must hit init before X is started, that's something we can mechanically check for in bugs
[22:11] <tjaalton> it's lightdm starting it..
[22:17] <tjaalton> bryce: btw, can you see why #1041790 isn't shown on the list of raring intel bugs?
[22:19] <bryce> ok
[22:20] <bryce> tjaalton, it does not show up on http://www.bryceharrington.org/Arsenal/ubuntu-x-swat/Reports/totals-raring-workqueue.svg because that excludes bugs that have been forwarded upstream and are still open upstream
[22:23] <tjaalton> oh
[22:23] <tjaalton> guess i need to make my own searches :)
[22:25] <bryce> yeah I'm working on adding more searches for types of queues we want, but that's medium priority work I only get to now and then... 
[22:25] <tjaalton> no worries
[22:26] <bryce> tjaalton, the one at the top of the list is "Bugs against X packages that the X team members are assigned to", so if that sounds suitable, I'll try to have it up by the end of this cycle
[22:33] <tjaalton> bryce: yeah it could be useful
[22:34]  * bryce bumps it up the todo list
[22:49] <bryce> tjaalton, hmm robert says he just starts X when udev tells him to