Rhythmbox crashes on launch in Ubuntu Breezy

Bug #20490 reported by François Obada
This bug report is a duplicate of:  Bug #20362: Rhythmbox segfaulting on startup. Edit Remove
8
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Critical
Sebastien Bacher

Bug Description

Rhythmbox 0.9.0-0ubuntu-2 crashes on launch, both from the GNOME menu and the
shell. Here is the debug output :

(rhythmbox:7585): Gdk-CRITICAL **: gdk_display_pointer_ungrab: assertion
`GDK_IS_DISPLAY (display)' failed

(rhythmbox:7585): Gdk-CRITICAL **: gdk_display_keyboard_ungrab: assertion
`GDK_IS_DISPLAY (display)' failed

Step to reproduce the bug :
1. Launch the latest Rhythmbox version from Ubuntu Breezy, either from the GNOME
menu or the shell.

Revision history for this message
Øivind Hoel (eruin) wrote :

Created an attachment (id=3433)
Backtrace of rhythmbox crash

Revision history for this message
Øivind Hoel (eruin) wrote :

The above backtrace is off a completely up to date (as of 12:16 CET 29.aug)
breezy installed off the colony 3 cd.
Rhythmbox crashes every time.

Revision history for this message
Uphaar Agrawalla (uphaar) wrote :

Is this the same as
http://bugzilla.gnome.org/show_bug.cgi?id=314677
and
http://bugzilla.gnome.org/show_bug.cgi?id=314452 ?

In that case, it is fixed in GTK CVS.

Revision history for this message
joe (joerg-unglaub) wrote :

this bug treats several other packages mostly gstreamer-based apps
like sound-juicer gnome-volume-control, gnome-sound-recorder, gst-editor,
gst-inspect-gui

Revision history for this message
joe (joerg-unglaub) wrote :

Managed to get the patch frome here:
     http://bugzilla.gnome.org/show_bug.cgi?id=314452
working in ubuntu gtk+2.8.2 source

I think that there is actualle work in getting gtk+2.8.3 in ubuntu
the this bug is fixed there but meanwhile a attach the patch
which gets rhythmbox working.

the patch has to be put in debian/patches as
003-the_patches_name_of_your_choice.patch

Revision history for this message
joe (joerg-unglaub) wrote :

Created an attachment (id=3447)
gtk-screen-init fixes this bug

put in debian/patches/ to activate the patch for next build

Revision history for this message
joe (joerg-unglaub) wrote :

(In reply to comment #6)

that fixed the issue for me
had some trouble making the .debs but just copying
the libgdk-x11......so made it for me.

now some the timebars in rhythmbox and gnome-sound-recorder don't move
but this could be thru my evil copy over replacement of a single gtk part

Revision history for this message
Robert Stoffers (robertstoffers) wrote :
Download full text (10.6 KiB)

I don't know if this will help, but here is my backtrace and other stuff related
to this problem:

Distribution: Ubuntu 5.10 (breezy)
Package: rhythmbox
Severity: critical
Version: GNOME2.11.92 0.9.x
Gnome-Distributor: Ubuntu
Synopsis: it crashes
Bugzilla-Product: rhythmbox
Bugzilla-Component: General
Bugzilla-Version: 0.9.x
BugBuddy-GnomeVersion: 2.0 (2.11.3)

Shell output:

rhythmbox

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): GLib-CRITICAL **: g_key_file_add_group: assertion
`g_key_file_lookup_group_node (key_file, group_name) == NULL' failed

(gnome_segv:13356): Gtk-WARNING **: Theme directory scalable/mimetypes of theme
eXperienceCrystal has no size field

End Shell output

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging ...

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

This bug has been marked as a duplicate of bug 20362.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.