[00:20] <ubotu> New bug: #199455 in mythtv (restricted) "mythfrontend.real crashed with SIGSEGV in memset()" [Undecided,Invalid] https://launchpad.net/bugs/199455
[14:21] <seb128> bryce: I fixed the gnome-settings-daemon crasher, that was due to conflicting variable names
[14:48] <ubotu> New bug: #197759 in gnome-settings-daemon (main) "Unable to start the settings manager 'gnome-settings-daemon'. (dup-of: 198951)" [Undecided,Incomplete] https://launchpad.net/bugs/197759
[15:30] <ubotu> New bug: #203181 in xorg (main) "Xorg crashed with SIGSEGV in free()" [Undecided,New] https://launchpad.net/bugs/203181
[16:03] <bryce> seb128: excellent
[16:04] <seb128> bryce: that's a 3 line changes ;-)
[16:04] <seb128> bryce: I wrote some explanations on the bug if you are interested
[16:05] <seb128> there is still the gnome-display-properties crasher though
[16:05] <seb128> I think you can reproduce it easily by using Xnest
[16:06] <seb128> I might look at this one too later but I've spent already quite some time on the g-s-d issue and I've other things to do this week
[16:06] <bryce> likely it needs the same fix
[16:06] <bryce> yes I know the feeling
[16:07] <seb128> not likely
[16:07] <seb128> the gsd crasher was due to a variable name conflict
[16:07] <seb128> the other one seems to be an another issue
[16:09] <bryce> do you have the name of the XError in this case?  
[16:09] <seb128> yes
[16:09] <seb128> be back in a minute
[16:09] <seb128> will give you that then
[16:31] <seb128> bryce: bug #199960 is an interesting one
[16:31] <ubotu> Launchpad bug 199960 in gnome-settings-daemon "error starting GNOME Settings Daemon" [High,Confirmed] https://launchpad.net/bugs/199960
[16:31] <seb128> bryce: XRRGetScreenSizeRange() seems to be the crasher for this user
[17:29] <bryce> seb128: what is the proper way for people to get debug symbols for gsd and gnome-desktop?  comment #28 said he installed debug symbols, but his traces only have symbols for Xorg calls
[17:30] <seb128> bryce: add the dbgsym source as indicated on the wiki page about crashes and install libgtk2.0-0-dbgsym libgnome-desktop-2-dbgsym and gnome-settings-daemon-dbgsym
=== asac_ is now known as asac
[19:23] <ubotu> New bug: #197161 in xorg (main) "[Hardy] Macbook trackpad not detected as trackpad" [Undecided,New] https://launchpad.net/bugs/197161
[19:26] <ubotu> New bug: #135023 in xorg-server (main) "wrong resolution autodetected" [Undecided,Incomplete] https://launchpad.net/bugs/135023
[19:27] <ubotu> New bug: #159634 in xorg-server (main) "Display detected as 1680x1050 but is 1680x1040" [Undecided,Incomplete] https://launchpad.net/bugs/159634
[19:43] <ubotu> New bug: #197740 in xorg-server (main) "[Hardy] gnome-display-properties does crazy things" [Undecided,Incomplete] https://launchpad.net/bugs/197740
[20:26] <ubotu> New bug: #203296 in xserver-xorg-input-synaptics "[hardy] Drag fails with keyboard stick and touchpad buttons" [Undecided,New] https://launchpad.net/bugs/203296
[21:09] <bryce> seb128: on 199960, the original reporter's issue has been solved.  But the commenter that provided the backtrace appears to be using a non-xrandr 1.2 driver, which seems to need that gtk.patch from ssp that I forwarded to you earlier.  I also attached it to the bug for you.
[21:15] <seb128> bryce: that is not clear to me, what difference would it make?
[21:15] <seb128> bryce: I'm not comfortable using those gtk changes in hardy and fedora doesn't do that either
[21:15] <bryce> see Soren's comment at the end of http://bugzilla.gnome.org/show_bug.cgi?id=521371
[21:15] <ubotu> Gnome bug 521371 in gdk "XRRGetScreenResources error (libXrandr.so.2)" [Normal,Unconfirmed] 
[21:17] <seb128> bryce: right, what soren wrote that is that the gtk call to XRRGetScreenResources is conditional to the tests before
[21:18] <seb128> bryce: the bug you pointed is a similar gtk crash, not the g-s-d one
[21:18] <seb128> bryce: which means libgnomedesktop should have tests similar to the ones he copied in the comment
[21:18] <seb128> libgnome-desktop doesn't use the gtk xrandr functions, otherwise it would not build without patching gtk
[21:19] <seb128> we need to check whether the libgnome-desktop checks are correct
[21:19] <seb128> and if they are and there is some buggy drivers we need to trap the gdk errors as I told you the other days (which is what sorens mentions on the bug too)
[21:19] <seb128> bryce: does it make sense to you?
[21:24] <seb128> bryce: ok, libgnome-desktop has no such tests
[21:25] <bryce> I am getting so frustrated by this
[21:26] <seb128> why?
[21:26] <seb128> the main crasher is fixed now
[21:27] <seb128> the other issue is that the code dpes xrandr 1.2 only
[21:27] <seb128> does
[21:27] <bryce> well you keep threatening to drop the code unless this is done and that is done, and keep throwing aside patches I send
[21:27] <seb128> hum
[21:27] <seb128> that's not really true
[21:28] <seb128> I said we need to get the crasher at startup fixed, which we mainly did
[21:28] <seb128> you don't argue for shipping hardy crashing out of the box for radeonhd, i855, etc users, do you?
[21:29] <seb128> and I don't reject patches for the fun of it
[21:29] <bryce> no, which is why I put in several days last week putting in a patch to only run on ati and intel which we know work (which was difficult, being sick), but you dropped it
[21:29] <seb128> but I try to minimize the api changes and the distro specific code we have to support
[21:29] <bryce> I'm not saying you're wrong, just that I'm feeling frustrated
[21:30] <seb128> I'm sorry about that
[21:30] <bryce> in any case, I put in a 1.2 check in apply_settings() in gsd-xrandr-manager.  Maybe that just needs to be done throughout.
[21:30] <seb128> but parsing the xorg log to determine if the card used is in a list is just not scalable and ugly
[21:31] <bryce> but it looks to me like this gtk.patch takes care of it globally without having to patch checks into a bunch of different functions
[21:31] <seb128> we would need to make gnome-desktop use those functions then
[21:32] <seb128> and gtk is one of our base libs
[21:32] <seb128> I'm not a big fan of changing behaviour over upstream and carry this patch
[21:32] <seb128> and if the redhat guys are not shipping it but are shipping the capplet they might have a reason
[21:32] <seb128> I would like to try to figure that before running into issues with gtk
[22:41] <ubotu> New bug: #202121 in linux-restricted-modules-2.6.24 (restricted) "Latest linux-restricted-modules-2.6.24-12-generic breaks FGLRX?" [Undecided,New] https://launchpad.net/bugs/202121
[23:16] <ubotu> New bug: #203327 in xorg (main) "Can`t change refresh rate" [Low,Invalid] https://launchpad.net/bugs/203327
[23:46] <ubotu> New bug: #192144 in xorg-server (main) "Xorg crashed with SIGSEGV in _dl_relocate_object()" [Undecided,New] https://launchpad.net/bugs/192144