[01:00] <ubotu> New bug: #148110 in xserver-xorg-video-intel (main) "compiz opengl rendering artefacts" [Medium,Confirmed] https://launchpad.net/bugs/148110
[03:29] <ubotu> New bug: #145294 in xserver-xorg-video-intel (main) "Copmiz is incompatible with GL screensaver as desktop background (root window)" [Low,New] https://launchpad.net/bugs/145294
[03:31] <ubotu> New bug: #177655 in compiz (main) "compiz not starting after upgrading kernel to 2.6.22-14-generic (dup-of: 192253)" [Medium,Incomplete] https://launchpad.net/bugs/177655
[04:15] <ubotu> New bug: #134446 in linux-restricted-modules-2.6.24 (restricted) "Compiz causing Hard Locks on certain systems" [Undecided,Confirmed] https://launchpad.net/bugs/134446
[05:10] <ubotu> New bug: #67440 in usplash (main) "edgy: usplash (?) blocks console after kdm shutdown (dup-of: 63558)" [Undecided,Confirmed] https://launchpad.net/bugs/67440
[10:27] <ubotu> New bug: #192873 in xserver-xorg-video-intel (main) "[915GM] X freezes after resume" [Undecided,New] https://launchpad.net/bugs/192873
[11:16] <ubotu> New bug: #192881 in linux-restricted-modules-2.6.24 (restricted) "DVB-T with Kernel 2.6.24 do not work" [Undecided,New] https://launchpad.net/bugs/192881
[12:10] <ubotu> New bug: #192883 in displayconfig-gtk (main) "displayconfig-gtk crashed with AttributeError in isXorgConfigChanged() (dup-of: 192253)" [Undecided,New] https://launchpad.net/bugs/192883
[12:37] <soren> tjaalton: What happened to my vmware driver patch?
[14:14] <Q-FUNK> speaking of patches, was bartman's 3rd patch ever merged?
[14:21] <ubotu> New bug: #186186 in xulrunner-1.9 "web page background render errors" [High,Confirmed] https://launchpad.net/bugs/186186
[14:43] <tjaalton> soren: sorry, I pushed it to git but didn't apply on our package. will upload it today
[14:43] <soren> \o/
[14:46] <ubotu> New bug: #191578 in firefox (main) "[hardy] rendering issues (dup-of: 186186)" [Undecided,New] https://launchpad.net/bugs/191578
[15:04] <soren> X has died on my 4 times today already. I'm using the Intel driver (intel 945).. Is it known to be jittery?
[15:05] <tjaalton> i think the drm bits need an update
[15:05] <tjaalton> should be filed already if I'm not mistaken
[15:07] <soren> Cool.
[15:07] <tjaalton> vmware uploaded
[15:07]  * soren hugs tjaalton 
[15:07]  * tjaalton hugs soren back
[15:08]  * tjaalton just saw "300" and feels Spartan
[16:03] <tjaalton> sigh, and the list of typos just keep on growing
[16:04] <tjaalton> another vmware upload on the way..
[16:05] <ubotu> New bug: #192930 in xserver-xorg-input-keyboard (main) "Numeric keypad no longer works in Hardy" [Low,Incomplete] https://launchpad.net/bugs/192930
[17:30] <ubotu> New bug: #192958 in xorg-server (main) "gnome/compiz crashes" [Undecided,New] https://launchpad.net/bugs/192958
[17:50] <seb128> bryce: what do you think that totem is doing wrong to cause bug #130696?
[17:50] <ubotu> Launchpad bug 130696 in totem "xine and totem-xine crashes with the fglrx driver" [Medium,New] https://launchpad.net/bugs/130696
[17:50] <seb128> especially that xine crashes the same way
[17:53] <seb128> I reassigned to xine-lib, let me know if you think I'm wrong
[18:26] <ubotu> New bug: #192638 in compiz (main) "[hardy] compiz can't start after 2008-02-15 updates (dup-of: 192253)" [Undecided,Incomplete] https://launchpad.net/bugs/192638
[19:12] <ubotu> New bug: #145800 in linux-restricted-modules-2.6.24 (restricted) "Compiz Fusion in Gutsy Gibbon Beta -- Momentary Freezes" [Undecided,Confirmed] https://launchpad.net/bugs/145800
[20:11] <ubotu> New bug: #193018 in xorg (main) "SHIFT+ALT != ALT+SHIFT" [Undecided,New] https://launchpad.net/bugs/193018
[20:35] <ubotu> New bug: #184071 in wxmaxima (universe) "wxmaxima fails after xorg update (dup-of: 183969)" [Undecided,New] https://launchpad.net/bugs/184071
[21:18] <ubotu> New bug: #151268 in xserver-xorg-video-ati (main) "compiz with ATI Radeion RV100 QY [7000/VE] corrupts screen after video playback" [Undecided,Incomplete] https://launchpad.net/bugs/151268
[22:18] <bryce> seb128: I get those "...received an X Window System error" messages with my xrandr gui all the time, and it's caused by making an incorrect xlib call
[22:18] <bryce> seb128: the error message indicates a coding error in the client application rather than an error in X
[22:20] <seb128> bryce: I'm not an xorg guy, but those errors often happen when using compiz or special xorg option, or some drivers, etc
[22:20] <bryce> seb128: I wish xlib provided more detailed explanations of the errors - I've not yet figured out what the code numbers indicate or whatever
[22:21] <seb128> why does playing the same video with the same software works when not running compiz in some cases?
[22:21] <bryce> seb128: yeah I know.  It's actually sort of a generic error message though, like "syntax error" or "out of memory"
[22:22] <seb128> on gutsy for example xv video playing doesn't work on some intel cards when using compiz, right?
[22:22] <bryce> so what I suspect is that in each case, the client app is making a different call, but they're all xlib calls (XReply probably), which returns its errors in that generic fashion
[22:22] <bryce> I gather gtk or glib has some sort of catch() routine that is capturing the error and generating the error message... perhaps that routine ought to be made to give better diagnostics (if that's possible)
[22:23] <seb128> how could the application know abou those limitation and don't do standard calls?
[22:23] <seb128> there is a gdk_x_error() right, you can break on it and get a gdb backtrace in such cases
[22:23] <seb128> but still, I'm not sure if that's the application which should know about driver bugs and try to workaround those
[22:24] <seb128> I would tend to say that if xorg doesn't handle standard requests that's something in the xorg stack to blame
[22:25] <bryce> seb128: well, assuming that's the case, at a minimum I would need to know what xlib routine that the client app is trying to access
[22:25] <seb128> alright
[22:25] <bryce> my guess is that it's trying to call some xlib routine which isn't valid with fglrx
[22:26] <seb128> in this case I've reassigned the bug to xine because I think the multimedia framework is likely the one doing the call
[22:26] <bryce> perhaps some sort of visualization thing...  a 3d call, or maybe even xrandr
[22:26] <seb128> and the guy get the issue using xine which seems to confirm that
[22:26] <seb128> right, that's possible
[22:26] <bryce> I notice some apps do xrandr calls to get screen layout info (maybe so they can tell where to pop up windows or whatever), but fglrx (and nvidia, etc.) don't support xrandr
[22:27]  * bryce ponders
[22:27] <seb128> totem doesn't thing like calling xrandr when not using xv and switching to fullscreen video
[22:27] <bryce> I would assume that it would be the client apps' responsibility to check for if a given module is loaded before trying to access its functionality, but not sure
[22:27] <seb128> but is it possible for the application to know that xorg doesn't support xrandr?
[22:28] <seb128> is there an x11 api for that?
[22:28] <bryce> yes
[22:28] <bryce> yep
[22:28] <seb128> ok
[22:28] <seb128> for the xrandr call it likely make sense
[22:28] <bryce> yeah, in fact there is code in Screen Resolution which does exactly this
[22:29] <bryce> and if you don't have the xrandr module it pops up an error dialog
[22:29] <seb128> I don't think those issues are due to xrandr
[22:29] <bryce> it also has code to check that you have a new enough version loaded
[22:29] <seb128> but I'll try to get a backtrace and ping you next time I've a such bug
[22:29] <seb128> maybe I can learn about how to debug those ;-)
[22:29] <bryce> well, iirc, it's a generic api for checking the xorg modules that are loaded, so could be similarly used even if it was say glx or exa or something
[22:30] <bryce> cool
[22:30] <bryce> yeah I really wish X didn't give such cryptic errors
[22:31] <ubotu> New bug: #158453 in xserver-xorg-video-intel (main) "[compiz] System bell causes blur to lose acceleration" [Undecided,Incomplete] https://launchpad.net/bugs/158453