GNOME Bugzilla – Bug 318766
fatal rhythmbox crash when launching for first time from rhythmbox-applet
Last modified: 2006-11-12 21:36:09 UTC
This bug has been opened here: https://bugzilla.ubuntu.com/show_bug.cgi?id=17318 "Running the most up to date breezy, I added rhythmbox-applet to my top panel. When I hit the play button to launch rhythmbox, it loaded the first time wizard and then said "Application rhythmbox has quit unexpectedly, do you want to restart? After I opened up rhythmbox from the Applications menu, ran the wizard, and tried opening it from the applet after closing it again, it "just worked"."
backtrace of the crash with the current CVS: Backtrace was generated from '/usr/bin/rhythmbox' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1225562432 (LWP 18148)] [New Thread -1236718672 (LWP 18150)] [New Thread -1228325968 (LWP 18149)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 63516
Thread 3 (Thread -1228325968 (LWP 18149))
Can you report the error message that it will print out on a terminal right before the crash?
trace of Bug 110228 looks similar.
there is no message on the terminal/log file for the applet (which starts rhythmbox)
Created attachment 56852 [details] [review] awful hack To fix this properly, we'd need to rearrange the RBShell constructor so we could register it with bonobo before calling rhythmdb_load.
The patch on bug 323348 causes the db to be loaded in another thread, which would also fix this problem.
No, it wouldn't. The druid thing is displayed using gtk_dialog_run, which does not return until the dialog is dismissed. Unless the user manages to click through the druid in less than a second, bonobo-activation will abort the process because the service will not be registered.
One option would be to make RBDruid be the window itself (i.e. derive from GnomeDruid). Then the could use gtk_widget_show rather than rb_druid_show, and respond to the "response" signal by showind the main window.
Created attachment 59550 [details] [review] make drui display non-clocking This patch makes RBDruid derive from GtkWindow instead of having one. This lets us make showing the druid non-clocking, which should fix this bug.
Patch committed to cvs. This fixes it for me.
*** Bug 374273 has been marked as a duplicate of this bug. ***