[05:27] <pwnguin> anyone care to describe what this means?
[05:27] <pwnguin> pushed as d954f9c80348de294602d931d387e5cd1ef4b9a5
[05:27] <pwnguin> from x.org bugzilla
[05:27] <pwnguin> http://bugs.freedesktop.org/show_bug.cgi?id=13961
[05:27] <ubotu> Freedesktop bug 13961 in Server/general "xkbLEDs causes segfault on login" [Critical,Resolved: fixed] 
[07:10] <ubotu> New bug: #187240 in linux-restricted-modules-2.6.24 (restricted) "NVidia driver and kernel module driver mismatch" [Undecided,New] https://launchpad.net/bugs/187240
[07:26] <tjaalton> pwnguin: http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commit;h=d954f9c80348de294602d931d387e5cd1ef4b9a5
[07:35] <tjaalton> it's not on the 1.4-branch though
[09:46] <tjaalton> bryce: the reporter is not subscribed on bug 144068 :)
[09:46] <ubotu> Launchpad bug 144068 in xorg "X graphical interface not loading." [Undecided,Invalid] https://launchpad.net/bugs/144068
[09:47] <tjaalton> so maybe just close it as invalid (it's nvidia blob related anyway)
[15:13] <seb128> hum
[15:14] <seb128> is xorg eating modifiers every now and then a known issue?
[15:30] <tjaalton> seb128: you mean that the special keys don't work?
[15:30] <tjaalton> ctrl,alt,shift..
[15:30] <seb128> yes, that's not called modifiers?
[15:31] <tjaalton> I guess they are :)
[15:31] <seb128> looks like it keeps generating this event when that happens
[15:31] <seb128> KeyRelease event, serial 31, synthetic NO, window 0x2e00001,
[15:31] <seb128>     root 0x69, subw 0x0, time 11773833, (167,-13), root:(174,41),
[15:31] <seb128>     state 0x2000, keycode 101 (keysym 0x0, NoSymbol), same_screen YES,
[15:31] <seb128>     XLookupString gives 0 bytes: 
[15:31] <seb128>     XFilterEvent returns: False
[15:31] <tjaalton> I haven't seen that but I've been using evdev.. gues there's a bug open for that
[15:35] <ubotu> New bug: #44912 in xorg (main) "Default desktop is too cpu hungry when idle." [Medium,Confirmed] https://launchpad.net/bugs/44912
[17:56] <ubotu> New bug: #187365 in xserver-xorg-video-intel (main) "Xorg 7.3 with Intel does not display maximum resolution anymore" [Undecided,New] https://launchpad.net/bugs/187365
[18:31] <bryce> tjaalton: that sounds fine
[18:32] <bryce> tjaalton: fwiw, now that triaged bugs are at 0 New, I've turned attention to Incomplete bugs with a response, and have begun working my way through them
[18:32] <bryce> (starting with some old ones -- so if you notice reports that are invalid or whatever, please feel free to handle accordingly)
[18:33] <tjaalton> bryce: ok, cool
[18:35] <tjaalton> I noticed that there are at least two mesa patches upstream that affect some compiz related crashes, but they are not on the stable branch for some reason
[19:23] <pwnguin> heh
[19:23] <pwnguin> "And it turns out null-pointer dereferences are bad."
[19:26] <tjaalton> yeah, that was one of them :)
[19:26] <ubotu> New bug: #186017 in linux-restricted-modules-2.6.24 (restricted) "kaffeine-xine crashed with ATI Radeon official drivers" [Undecided,New] https://launchpad.net/bugs/186017
[19:33] <pwnguin> tjaalton: so uh, do i need to back/forward port the patch?
[19:35] <tjaalton> pwnguin: the xkbLED patch?
[19:35] <pwnguin> yea
[19:37] <tjaalton> ask if it could be included in the 1.4-branch
[19:39] <tjaalton> that's the best approach imho
[19:51] <bryce> tjaalton: hey btw, colin and I were wondering what further work is needed for input support / hal?
[19:51] <bryce> tjaalton: if there's work still needed, I want to set aside some time to assist with that
[19:51] <tjaalton> bryce: gravity has some patches that would make it use the configuration on xorg.conf
[19:52] <tjaalton> so no need to edit some bizarre fdi file
[19:52] <tjaalton> he hasn't published them yet afaik
[19:52] <tjaalton> but please poke him about it :)
[19:53] <bryce> ok
[19:54] <bryce> aside from that, is the autoconfiguration of input devices all squared away, or is there more feature development work needed?
[19:54] <bryce> or are we back to just bug squishing?
[19:57] <pwnguin> does that mean i wouldnt need an xorg.conf for say, wacom?
[19:57] <bryce> pwnguin: yes that's the intent
[19:57] <tjaalton> actually, that depends on how the wacom driver is doing
[19:58] <tjaalton> bryce: mjg59 said once that synaptics needs some love, and he promised to do something about it but I don't know if he's had the time yet
[20:03] <bryce> ok, maybe we should follow up with him
[20:03] <tjaalton> it was before christmas though :)
[20:04] <bryce> in fact he was at the sprint in london for one day last week
[20:04] <tjaalton> and now at LCA
[20:04] <bryce> ted asked him some questions about reusing the synaptics approach for configuring wacom and other things
[20:05] <bryce> he was talking about needing an X extension similar to xrandr, but for input devices, in order to do all this stuff right
[20:05] <bryce> hrm, which I'd taken notes
[20:06] <bryce> ok, I'll follow up with him at some point.  I suspect this is going to take more time than we have for hardy
[20:06] <tjaalton> yeah
[20:07] <bryce> btw, I've had some emails with glatzor, mpt, and others to get the plans sorted out for the xrandr gui tool
[20:08] <seb128> hey bryce
[20:08] <bryce> heya seb128
[20:08] <tjaalton> bryce: cool, right now it's pretty useless :/
[20:08] <seb128> bryce: didn't you read my comment before?
[20:09] <bryce> seb128: oh I must have missed it
[20:09] <bryce> seb128: btw, I got confirmation regarding your advice on gnome-control-center preferring C - http://mail.gnome.org/archives/gnomecc-list/2007-November/msg00043.html
[20:10] <bryce> seb128: sorry, could you repeat the comment?
[20:11] <seb128> bryce: no, I switched computer since, basically that's modifier not working every now and then, I think that's an xorg issue
[20:12] <tjaalton> yes, I'll dig up the bug
[20:12] <seb128> when that happens the cursor is directly hidden in widget that do that on key events
[20:12] <seb128> and xev confirm that xorg seems to generate continuous events
[20:13] <seb128> I copied the xev event on the chan, I've it on my laptop and can attach it to a bug or copy it again later if required
[20:13] <bryce> seb128: ah ok; sorry technically I'm on holiday today so am trying not to work (it's hard!) but I'll look into it tomorrow after I finish more ubuntu-mobile stuff, if you can send me the bug
[20:13] <seb128> ups, sorry
[20:13] <seb128> technically I've finished my work day ;-)
[20:13] <seb128> right
[20:14] <seb128> let me know when you look at it, there is no hurry
[20:14] <seb128> I'm just hanging around in case of one of the late GNOME 2.21.90 upload is an issue for the CD build
[20:14] <bryce> cool
[20:14] <tjaalton> 17:31 < seb128> looks like it keeps generating this event when that happens
[20:14] <tjaalton> 17:31 < seb128> KeyRelease event, serial 31, synthetic NO, window 0x2e00001,
[20:14] <tjaalton> 17:31 < seb128>     root 0x69, subw 0x0, time 11773833, (167,-13), root:(174,41),
[20:14] <tjaalton> 17:31 < seb128>     state 0x2000, keycode 101 (keysym 0x0, NoSymbol), same_screen YES,
[20:14] <tjaalton> 17:31 < seb128>     XLookupString gives 0 bytes: 
[20:14] <tjaalton> 17:31 < seb128>     XFilterEvent returns: False
[20:14] <bryce> yeah I plan to spend today on getting inkscape further along for the release :-)
[20:14] <seb128> tjaalton: thanks
[20:15] <bryce> ok, got it, I'll investigate more tomorrow
[20:15] <seb128> thanks
[20:15] <seb128> I'm using compiz there in case that's revelant, I'll try without it if that happens
[20:16] <bryce> oh btw, is there a LP# for this?
[20:16] <tjaalton> I bet there is
[20:16] <seb128> not from me, but Hobbsee mentionned she has a such issue for some time and somebody else too
[20:17] <seb128> I doubt that's due to the wm, I tried switching to no desktop effect and activating the option again and that didn't fix it
[20:17] <bryce> ok, I'll search if someone already put in a report.  I may ask for your Xorg.0.log and xorg.conf later
[20:17] <seb128> so that looks like an xorg issue
[20:17] <seb128> sure
[20:17] <seb128> I'll copy those next time I run into the bug
[20:18] <bryce> maybe check ~/.xsession-errors too, just in case
[20:20] <seb128> ok
[20:20] <seb128> will do that tomorrow, I doubt I'll work enough to trigger it again today ;-)
[20:20] <bryce> seb128: btw, I was looking at some dejavu font issues yesterday.  Is that package owned by Arne?  
[20:21] <seb128> nobody owns package in ubuntu ;-)
[20:21] <bryce> it appears some of his patches from Gutsy were not ported forward to Hardy, so there were regressions
[20:21] <bryce> ahh, "Is he the person that normally would keep an eye on that package?"
[20:21] <seb128> I don't think arne did lot of packaging changes yet but he's the fonts contact, so if you have any change to do there might be a good idea to talk to him first
[20:22] <bryce> ok good, I described the solution for the user reporting the problem and asked that he contact arne about it
[20:28] <tjaalton> seb128: so the modifier key is 'stuck' for a while?
[20:29] <seb128> the events seem to be loop generated or something like that
[20:29] <seb128> I've looked to the logs but there was nothing obvious there
[20:34] <tjaalton> I can't find any bugs with that description on LP
[20:45] <tjaalton> hehe, freedesktop bug 13538
[20:45] <ubotu> Freedesktop bug 13538 in Server/general "staggering server memory leak" [Blocker,New] http://bugzilla.freedesktop.org/show_bug.cgi?id=13538
[20:47] <ubotu> New bug: #97107 in gnome-screensaver (main) "Braid screensaver cause desktop to freeze up (dup-of: 101943)" [Medium,Triaged] https://launchpad.net/bugs/97107
[22:36] <ubotu> New bug: #187430 in xkeyboard-config (main) "New Variant/Layout for symbols/ca - shs" [Undecided,New] https://launchpad.net/bugs/187430