Rhythmbox doesn't start - Segmentation Fault

[bluesky74656]

Binary package hint: rhythmbox

Rhythmbox doesn't start. Attempting to start from the command line shows a segmentation fault. The segfault isn't intermittent as the other Feisty bug claims, nor does it open enough for any display or music to start. This is why I'm creating a new bug report. Here are the results of rhythmbox -d:

rhythmbox -d
(22:51:32) [0x80f4028] [rb_debug_init_match] rb-debug.c:141: Debugging enabled
(22:51:32) [0x80f4028] [main] main.c:206: initializing Rhythmbox 0.10.0
(22:51:32) [0x80f4028] [rb_threads_init] rb-util.c:460: GMutex isn't recursive
(22:51:32) [0x80f4028] [main] main.c:215: going to create DBus object
(22:51:32) [0x80f4028] [main] main.c:299: Going to create a new shell
(22:51:32) [0x80f4028] [rb_dot_dir] rb-file-helpers.c:87: unable to create Rhythmbox's dot dir

(rhythmbox:7335): GLib-GObject-CRITICAL **: g_param_spec_internal: assertion `(name[0] >= 'A' && name[0] <= 'Z') || (name[0] >= 'a' && name[0] <= 'z')' failed
Segmentation fault (core dumped)

Steps to Reproduce:
Attempt to start Rhythmbox.

rhythmbox --version
GNOME rhythmbox 0.10.0

rhythmbox --gst-version
GStreamer Core Library version 0.10.12

Ubuntu 7.04 - Feisty Fawn

[Sebastien Bacher (seb128)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[bluesky74656 (bluesky74656)]

I managed to solve the problem by re-installing rhythmbox. I still have no idea what caused it, but it works now.

Thanks anyway.

[Sebastien Bacher (seb128)]

closing the bug then, feel free to reopen if you get the bug again and can get a stacktrace