Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 337045 - >=gnome-base/gnome-settings-daemon-2.30.2-r1 dies with BadMatch when opening quodlibet
Summary: >=gnome-base/gnome-settings-daemon-2.30.2-r1 dies with BadMatch when opening ...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-13 09:04 UTC by Dan Callaghan
Modified: 2011-04-03 11:45 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
stack trace and X error details from gdb (gsd-badmatch-debug.txt,17.48 KB, text/plain)
2010-09-13 09:05 UTC, Dan Callaghan
Details
emerge --info --verbose (emerge-info.txt,12.52 KB, text/plain)
2010-09-13 09:06 UTC, Dan Callaghan
Details
stack trace and X error details from gdb (from 2.32.1) (gsd-stack-trace.txt,17.16 KB, text/plain)
2011-03-11 00:56 UTC, Dan Callaghan
Details
emerge --info --verbose (emerge-info.txt,12.65 KB, text/plain)
2011-03-11 00:57 UTC, Dan Callaghan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Callaghan 2010-09-13 09:04:29 UTC
After a recent upgrade, whenever I start quodlibet, gnome-settings-daemon dies with a BadMatch error. I'm running quodlibet-2.2.1, xmonad-0.9.1 from haskell overlay, and stable GNOME (gnome-settings-daemon-2.30.2-r1).

Reproducible: Always

Steps to Reproduce:
1. Start quod libet
Actual Results:  
gnome-settings-daemon dies with BadMatch X error


Stack trace and emerge --info to come.
Comment 1 Dan Callaghan 2010-09-13 09:05:48 UTC
Created attachment 247105 [details]
stack trace and X error details from gdb
Comment 2 Dan Callaghan 2010-09-13 09:06:59 UTC
Created attachment 247106 [details]
emerge --info --verbose
Comment 3 Gilles Dartiguelongue (RETIRED) gentoo-dev 2010-09-13 09:28:32 UTC
what version of libxklavier and gtk+ are you running 
Comment 4 Dan Callaghan 2010-09-13 09:35:11 UTC
gtk+-2.20.1-r1
libxklavier-5.0
Comment 5 Pacho Ramos gentoo-dev 2010-09-13 10:23:56 UTC
Did you update properly libxklavier? I mean, running "revdep-rebuild --library libxklavier.so.15" and, after that, removing libxklavier.so.15?

I cannot reproduce this crash, but looks a bit similar to https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/447431

There are others badmatch related reports, but I am not sure if they are related with this:
https://bugzilla.gnome.org/show_bug.cgi?id=628926
Comment 6 Dan Callaghan 2010-09-13 10:36:49 UTC
(In reply to comment #5)
> Did you update properly libxklavier? I mean, running "revdep-rebuild --library
> libxklavier.so.15" and, after that, removing libxklavier.so.15?

I don't have libxklavier.so.15 on my system, and everything is linked correctly, so I must have updated it properly (although I don't remember doing it).
Comment 7 Pacho Ramos gentoo-dev 2010-09-13 10:54:11 UTC
What USEs do you have for media-sound/quodlibet? Try enabling/disabling "gstreamer" USE for it.
Comment 8 Pacho Ramos gentoo-dev 2010-10-12 19:01:55 UTC
(In reply to comment #7)
> What USEs do you have for media-sound/quodlibet? Try enabling/disabling
> "gstreamer" USE for it.
> 

Please get back to us
Comment 9 Dan Callaghan 2010-10-15 00:59:37 UTC
(In reply to comment #7)
> What USEs do you have for media-sound/quodlibet? Try enabling/disabling
> "gstreamer" USE for it.

Sorry for my unresponsiveness. USE for quodlibet is: dbus gstreamer. Will try disabling gstreamer (will it be able to play anything without gstreamer though?)

I also noticed something else. I can work around this bug by starting quodlibet with some windows on my current workspace (I'm using xmonad). The bug only occurs if quodlibet maps its window onto an empty, visible workspace.
Comment 10 Dan Callaghan 2010-10-15 01:06:46 UTC
The bug still occurs with USE -gstreamer for quodlibet.
Comment 11 Pacho Ramos gentoo-dev 2011-01-27 19:43:39 UTC
Could anybody try the status of this with Gnome 2.32?
Comment 12 Pacho Ramos gentoo-dev 2011-02-24 17:48:40 UTC
(In reply to comment #11)
> Could anybody try the status of this with Gnome 2.32?
> 

Please retry with Gnome 2.32 as it's being stabilized
Comment 13 Dan Callaghan 2011-02-24 22:20:37 UTC
Sorry for the delayed response. I can no longer reproduce this crash with gnome-settings-daemon-2.30.2-r1. My guess is that it was fixed by updating libX11 or a related library.
Comment 14 Dan Callaghan 2011-03-11 00:55:48 UTC
I started seeing this crash again today, with gnome-settings-daemon-2.32.1. I can reliably reproduce it, even though I am sure yesterday it wasn't happening. The strangest thing is that I haven't changed anything of importance on my system lately...

Fresh stack trace to be attached.
Comment 15 Dan Callaghan 2011-03-11 00:56:39 UTC
Created attachment 265519 [details]
stack trace and X error details from gdb (from 2.32.1)
Comment 16 Dan Callaghan 2011-03-11 00:57:24 UTC
Created attachment 265521 [details]
emerge --info --verbose
Comment 17 Dan Callaghan 2011-03-11 01:00:38 UTC
Not sure if this is relevant, but I also see these errors in ~/.xsession-errors from quodlibet when it is started. I get these errors each time, irrespective of whether gnome-settings-daemon crashes.

Error grabbing key 173, 0x2784000
Error grabbing key 171, 0x2784000
Error grabbing key 172, 0x2784000
Error grabbing key 174, 0x2784000
Comment 18 Pacho Ramos gentoo-dev 2011-03-11 08:04:06 UTC
Please attach ~/.xsession-errors just after reproducing the crash. Also try on a new created user account if it's reproducible also there.
Comment 19 Pacho Ramos gentoo-dev 2011-03-17 21:30:17 UTC
ping
Comment 20 Dan Callaghan 2011-03-23 22:17:12 UTC
I can't reproduce this on a fresh user account, even when I use the same xmonad config, update the keyboard settings to match my current user account, and copy in my old ~/.quodlibet directory. So I guess that means there is some setting deep in the bowels of my gconf which is triggering this bug?
Comment 21 Pacho Ramos gentoo-dev 2011-03-24 10:12:26 UTC
Yes, you should now start to copy every config file and directory from your non-working home to the new one until it starts to fail again and, then, remember what directory was just copied to try to find the culprit.
Comment 22 Pacho Ramos gentoo-dev 2011-04-03 11:45:03 UTC
This bug is invalid then as is related with some user configuration, if you need help on trying to find exact file or directory causing this, try to ask for help in forums.gentoo.org