GNOME Bugzilla – Bug 685551
GLib-GObject-CRITICAL **: g_value_get_uint: assertion `G_VALUE_HOLDS_UINT (value)' failed
Last modified: 2012-10-15 09:25:01 UTC
While trying to reproduce bug 685400, the following different error showed up. Starting program: /usr/bin/rhythmbox -D --debug [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1". [New Thread 0xb2ccab70 (LWP 19201)] [New Thread 0xb22ffb70 (LWP 19202)] [New Thread 0xab9c8b70 (LWP 19203)] [Thread 0xab9c8b70 (LWP 19203) exited] [New Thread 0xab9c8b70 (LWP 19204)] [New Thread 0xaaa80b70 (LWP 19205)] [New Thread 0xa8934b70 (LWP 19206)] [Thread 0xab9c8b70 (LWP 19204) exited] [Thread 0xaaa80b70 (LWP 19205) exited] [New Thread 0xaaa80b70 (LWP 19207)] [Thread 0xa8934b70 (LWP 19206) exited] [New Thread 0xa8934b70 (LWP 19221)] [Thread 0xa8934b70 (LWP 19221) exited] (rhythmbox:19186): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files Program received signal SIGINT, Interrupt. 0xb7fe1424 in __kernel_vsyscall () Continuing. [New Thread 0xab9c8b70 (LWP 19234)] [New Thread 0xa2f78b70 (LWP 19235)] [New Thread 0xa2720b70 (LWP 19236)] [New Thread 0xa1f1fb70 (LWP 19237)] [Thread 0xa1f1fb70 (LWP 19237) exited] [Thread 0xaaa80b70 (LWP 19207) exited] [Thread 0xab9c8b70 (LWP 19234) exited] [New Thread 0xab9c8b70 (LWP 19264)] [Thread 0xab9c8b70 (LWP 19264) exited] [Thread 0xa2f78b70 (LWP 19235) exited] [New Thread 0xa2f78b70 (LWP 19277)] [New Thread 0xaaa80b70 (LWP 19278)] [New Thread 0xa171eb70 (LWP 19279)] [New Thread 0xa0f1db70 (LWP 19280)] [New Thread 0xa071cb70 (LWP 19281)] [Thread 0xa0f1db70 (LWP 19280) exited] [Thread 0xaaa80b70 (LWP 19278) exited] [Thread 0xa071cb70 (LWP 19281) exited] [Thread 0xa2f78b70 (LWP 19277) exited] [New Thread 0xa2f78b70 (LWP 19319)] [New Thread 0xa071cb70 (LWP 19325)] [Thread 0xa171eb70 (LWP 19279) exited] [New Thread 0xa171eb70 (LWP 19326)] (rhythmbox:19186): GLib-GObject-CRITICAL **: g_value_get_uint: assertion `G_VALUE_HOLDS_UINT (value)' failed Program received signal SIGINT, Interrupt. 0xb7fe1424 in __kernel_vsyscall () (gdb) t a a bt f
+ Trace 230974
Thread 1 (Thread 0xb2fa1af0 (LWP 19186))
Backtrace stopped: previous frame inner to this frame (corrupt stack?) Continuing. [New Thread 0xaaa80b70 (LWP 19394)] [Thread 0xa2f78b70 (LWP 19319) exited] [New Thread 0x9bf1ab70 (LWP 19395)] [New Thread 0x9b719b70 (LWP 19396)] [New Thread 0x9af18b70 (LWP 19397)] [New Thread 0x9a717b70 (LWP 19398)] [New Thread 0x99f16b70 (LWP 19399)] [New Thread 0x99715b70 (LWP 19400)] [Thread 0x9a717b70 (LWP 19398) exited] [Thread 0x99f16b70 (LWP 19399) exited] [Thread 0x99715b70 (LWP 19400) exited] [Thread 0x9af18b70 (LWP 19397) exited] [Thread 0x9bf1ab70 (LWP 19395) exited] [New Thread 0x9bf1ab70 (LWP 19402)] [Thread 0xa171eb70 (LWP 19326) exited] [Thread 0xa071cb70 (LWP 19325) exited] [Thread 0xaaa80b70 (LWP 19394) exited] [Thread 0x9b719b70 (LWP 19396) exited] [New Thread 0x9b719b70 (LWP 19552)] [New Thread 0xaaa80b70 (LWP 19553)] [New Thread 0xa071cb70 (LWP 19554)] [Thread 0xa071cb70 (LWP 19554) exited] [Thread 0xaaa80b70 (LWP 19553) exited] [New Thread 0xaaa80b70 (LWP 19567)] [Thread 0xaaa80b70 (LWP 19567) exited] [Thread 0xa2720b70 (LWP 19236) exited] [Thread 0x9b719b70 (LWP 19552) exited] [Thread 0x9bf1ab70 (LWP 19402) exited] [Thread 0xb2ccab70 (LWP 19201) exited] [Thread 0xb2fa1af0 (LWP 19186) exited] [Inferior 1 (process 19186) exited normally] quit
I am able to reproduce this bug using debian sid and version 2.97
(In reply to comment #1) > I am able to reproduce this bug using debian sid and version 2.97 Thanks for following up on the report. Searching the Web for this error, I found out this has been reported to the Debian BTS as #660113 [1] already for Rhythmbox 2.95-1. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660113
Here is a backtrace from Rhythmbox 2.97-2.1 and GNOME 3. I was trickered after clicking on the play button.
+ Trace 230981
Thread 1 (Thread 0x7ffff7fac9c0 (LWP 14865))
This is harmless, ignore it until it gets fixed in pygobject.
*** This bug has been marked as a duplicate of bug 684331 ***