After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 677464 - rhythmbox crashes on startup
rhythmbox crashes on startup
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: general
unspecified
Other Linux
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-06-05 12:10 UTC by murf
Modified: 2012-09-04 23:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
What I get when I run with -d by hand from command line. (95.55 KB, text/plain)
2012-06-05 12:10 UTC, murf
Details
Rhythmbox Terminal Output (40.95 KB, text/plain)
2012-09-04 22:49 UTC, OzzyFrank
Details
Rhythmbox Debug (from rhythmbox -d) (89.24 KB, text/plain)
2012-09-04 22:54 UTC, OzzyFrank
Details

Description murf 2012-06-05 12:10:40 UTC
Created attachment 215637 [details]
What I get when I run with -d by hand from command line.

This might have something to do with last.fm, but at this point I can't prove it. Signed up and was playing music from last.fm. I think I had the player on hold overnight, but when I came back in, the player had crashed. It no longer starts up.

I've attached the debug output when I start rhythmbox from the command line. Hope it helps.

You know, rhythmbox really needs to implement the --version option! This version of rhythmbox is that currently available on Ubuntu 12.04 LTS, regularly updated.
Comment 1 Jonathan Matthew 2012-06-05 12:16:14 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 murf 2012-06-05 13:25:18 UTC
Followed instructions up to the bug buddy, which did not start up automatically, btw, so I just got into gdb and ran it by hand; thought
you might be interested in the various messages output to the console:


(gdb) run
Starting program: /usr/bin/rhythmbox 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe2c55700 (LWP 23198)]
[New Thread 0x7fffe15f4700 (LWP 23199)]
[New Thread 0x7fffda14a700 (LWP 23200)]
[New Thread 0x7fffd92f6700 (LWP 23201)]
[Thread 0x7fffd92f6700 (LWP 23201) exited]

(rhythmbox:23197): Gtk-WARNING **: A floating object was finalized. This means that someone
called g_object_unref() on an object that had only a floating
reference; the initial floating reference is not owned by anyone
and must be removed with g_object_ref_sink().

(rhythmbox:23197): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkWidget'

(rhythmbox:23197): Gtk-CRITICAL **: gtk_grid_attach: assertion `GTK_IS_WIDGET (child)' failed

(rhythmbox:23197): Gtk-CRITICAL **: gtk_ui_manager_get_widget: assertion `GTK_IS_UI_MANAGER (manager)' failed
[New Thread 0x7fffd92f6700 (LWP 23203)]
[Thread 0x7fffd92f6700 (LWP 23203) exited]
[New Thread 0x7fffd92f6700 (LWP 23215)]
[New Thread 0x7fffc4d3f700 (LWP 23216)]

(rhythmbox:23197): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed

(rhythmbox:23197): Gtk-CRITICAL **: gtk_ui_manager_get_widget: assertion `GTK_IS_UI_MANAGER (manager)' failed

Program received signal SIGSEGV, Segmentation fault.
__GI___libc_free (mem=0x7fff00000002) at malloc.c:2968
2968    malloc.c: No such file or directory.
(gdb) thread apply all bt

Thread 1 (Thread 0x7ffff7fa59c0 (LWP 22335))

  • #0 __GI___libc_free
    at malloc.c line 2968
  • #1 toolbar_add_widget_cb
    at rb-source-toolbar.c line 262
  • #2 g_closure_invoke
    at /build/buildd/glib2.0-2.32.1/./gobject/gclosure.c line 777
  • #3 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.32.1/./gobject/gsignal.c line 3547
  • #4 g_signal_emit_valist
    at /build/buildd/glib2.0-2.32.1/./gobject/gsignal.c line 3296
  • #5 g_signal_emit
    at /build/buildd/glib2.0-2.32.1/./gobject/gsignal.c line 3352
  • #6 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #7 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #8 gtk_ui_manager_ensure_update
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #9 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #10 rb_shell_sync_toolbar_state
    at rb-shell.c line 3194
  • #11 rb_shell_sync_smalldisplay
    at rb-shell.c line 3319
  • #12 rb_shell_startup
    at rb-shell.c line 1169
  • #13 _g_closure_invoke_va
    at /build/buildd/glib2.0-2.32.1/./gobject/gclosure.c line 840
  • #14 g_signal_emit_valist
    at /build/buildd/glib2.0-2.32.1/./gobject/gsignal.c line 3207
  • #15 g_signal_emit
    at /build/buildd/glib2.0-2.32.1/./gobject/gsignal.c line 3352
  • #16 g_application_register
    at /build/buildd/glib2.0-2.32.1/./gio/gapplication.c line 1198
  • #17 g_application_register
    at /build/buildd/glib2.0-2.32.1/./gio/gapplication.c line 1173
  • #18 rb_shell_local_command_line
    at rb-shell.c line 1244
  • #19 g_application_run
    at /build/buildd/glib2.0-2.32.1/./gio/gapplication.c line 1446
  • #20 main
    at main.c line 99

Comment 3 murf 2012-06-05 13:27:28 UTC
now, that was interesting! it removed the bt for threads that were in wait state at the time of the crash. How nice!
Comment 4 Jonathan Matthew 2012-06-17 03:28:53 UTC
Looks like things are pretty messed up by that point.. try running with '-D something' in gdb, which will make it stop at the first critical/warning message, then get a stack trace from there.
Comment 5 OzzyFrank 2012-09-04 22:11:44 UTC
I've had exactly the same problem (more or less - the error numbers vary) since not long after upgrading to Ubuntu 12.04. It still worked fine after the upgrade, but after some updates not long after, I could not get it to run anymore. Sometimes, in my Gnome 3 Classic taskbar, a button appears saying "Starting Rhythmbox", but it never does. I've been hoping an update would fix it - and was happy to see a major update to rhythmbox and dependent packages a few weeks later - but it's still failing to load. I even tried deleting its data folders, in case it was a setting or plugin, but that made no difference at all. I'm on a 64-bit system, in case that matters. I came here to file a bug report, but this is pretty similar - main thing being, nothing will get Rhythmbox to load anymore.
Comment 6 Jonathan Matthew 2012-09-04 22:36:28 UTC
If you could provide the information I requested in comment 4, that would probably help. What 'error numbers' are you talking about?
Comment 7 OzzyFrank 2012-09-04 22:49:38 UTC
Created attachment 223480 [details]
Rhythmbox Terminal Output
Comment 8 OzzyFrank 2012-09-04 22:50:19 UTC
Okay... I just looked up Rhythmbox's options, and thought I'd try to open it
with --disable-plugins - even though I had previously removed any data folders,
like the plugins folder to no avail - and it has loaded. While this isn't a
fix, and clearly something is amiss with Rhythmbox, at least I can get it to
load with "rhythmbox --disable-plugins" until it's fixed.

As for numbers, I'm referring to lines like:

(rhythmbox:30536): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:69:14: Not using units is deprecated. Assuming 'px'.

... and the numbers (after rhythmbox:) always vary. I've attached the terminal output from simply running "rhythmbox". Also, in case it helps, here is the single line of output for running "rhythmbox &" (the "&" was a little trick I found that could get some trouble programs to run):

[1] 31749
Comment 9 OzzyFrank 2012-09-04 22:54:42 UTC
Created attachment 223481 [details]
Rhythmbox Debug (from rhythmbox -d)
Comment 10 Jonathan Matthew 2012-09-04 23:28:09 UTC
The CSS errors you're seeing are probably a mismatch between the versions of gtk and the theme you're using, and they're not at all interesting here.

commit c2239ae should fix this, but I've never seen the crash myself so I can't be sure.