GNOME Bugzilla – Bug 685565
GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion `object_path != NULL && g_variant_is_object_path (object_path)' failed
Last modified: 2012-10-10 12:18:53 UTC
Starting self-built Rhythmbox 2.98 under Debian Sid/unstable under GNOME 3 and Tracker miners running, the following message is printed to the terminal. GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion `object_path != NULL && g_variant_is_object_path (object_path)' failed Here is the backtrace. If the cdparanoia debugging symbols are needed I am happy to recreate the trace. 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 0xb2badb70 (LWP 27083)] [New Thread 0xada37b70 (LWP 27084)] [New Thread 0xab8d8b70 (LWP 27085)] [Thread 0xab8d8b70 (LWP 27085) exited] [New Thread 0xab8d8b70 (LWP 27086)] [New Thread 0xaa83ab70 (LWP 27087)] [Thread 0xab8d8b70 (LWP 27086) exited] [New Thread 0xaa039b70 (LWP 27088)] [Thread 0xaa039b70 (LWP 27088) exited] [Thread 0xaa83ab70 (LWP 27087) exited] [New Thread 0xaa83ab70 (LWP 27089)] [New Thread 0xaa039b70 (LWP 27093)] [Thread 0xaa039b70 (LWP 27093) exited] [New Thread 0xab8d8b70 (LWP 27104)] [New Thread 0xa2d39b70 (LWP 27105)] (rhythmbox:27068): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion `object_path != NULL && g_variant_is_object_path (object_path)' failed Program received signal SIGINT, Interrupt. 0xb7fe1424 in __kernel_vsyscall () (gdb) t a a bt f
+ Trace 230977
Thread 1 (Thread 0xb2fa1af0 (LWP 27068))
Program received signal SIGINT, Interrupt. 0xb7fe1424 in __kernel_vsyscall () Continuing. [New Thread 0xab8d8b70 (LWP 27284)] [New Thread 0xa24e1b70 (LWP 27285)] [Thread 0xa24e1b70 (LWP 27285) exited] [New Thread 0xa1ce0b70 (LWP 27287)] [New Thread 0xa14dfb70 (LWP 27288)] [New Thread 0xa0cdeb70 (LWP 27289)] [New Thread 0xa04ddb70 (LWP 27290)] [New Thread 0x9fcdcb70 (LWP 27291)] [Thread 0xaa83ab70 (LWP 27089) exited] [Thread 0xa14dfb70 (LWP 27288) exited] [Thread 0xa1ce0b70 (LWP 27287) exited] [Thread 0xa0cdeb70 (LWP 27289) exited] [Thread 0xa04ddb70 (LWP 27290) exited] [Thread 0x9fcdcb70 (LWP 27291) exited] [New Thread 0x9fcdcb70 (LWP 27327)] [Thread 0x9fcdcb70 (LWP 27327) exited] [Thread 0xab8d8b70 (LWP 27284) exited] [Thread 0xa2d39b70 (LWP 27105) exited] [Thread 0xada37b70 (LWP 27084) exited] [Thread 0xb2badb70 (LWP 27083) exited] [Inferior 1 (process 27068) exited normally] quit
fixed in commit c92be6e
(In reply to comment #1) > fixed in commit c92be6e Thanks as always for the quick solution [1]. For the next commits could you please also paste the errors into the commit message. That would be much appreciated for people looking through the commit log and not knowing what extent the fixed error had. I know you paste the Bugzilla bug URL, but it is not made a clickable link in cgit [1] and never will be one for people using plain `git log`. Thanks again! [1] http://git.gnome.org/browse/rhythmbox/commit/?id=c92be6e8ee97be5cb526817645dad50b1857d8c6