rhythmbox crashed with SIGSEGV in IA__g_object_unref()

Bug #326869 reported by spinstartshere
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Rhythmbox
Expired
Critical
rhythmbox (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

I closed Rhythmbox accidentally. I use Music Applet in the Panel. The time display changed to --:-- and the playback buttons were still there, so I clicked Play and a notification appeared as though as song was playing. I opened Rhythmbox to play a song, tried to do so and ended up with this crash.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.11.6svn20090108-0ubuntu1
ProcCmdline: /usr/bin/rhythmbox
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 IA__g_object_unref (_object=0xaaaaaaaa)
 find_xoverlay (plugin=0x9e4eaa8)
 bus_sync_message_cb (bus=0xb2f14768, msg=0xb6c9a60,
 marshal_VOID__MINIOBJECT (closure=0x9890f98,
 IA__g_closure_invoke (closure=0x9890f98, return_value=0x0,
Title: rhythmbox crashed with SIGSEGV in IA__g_object_unref()
Uname: Linux 2.6.28-6-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mythtv netdev plugdev powerdev pulse pulse-access pulse-rt sambashare scanner vboxusers video

Tags: apport-crash
Revision history for this message
spinstartshere (spinstartshere) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_object_unref (_object=0xaaaaaaaa)
find_xoverlay (plugin=0x9e4eaa8)
bus_sync_message_cb (bus=0xb2f14768, msg=0xb6c9a60,
marshal_VOID__MINIOBJECT (closure=0x9890f98,
IA__g_closure_invoke (closure=0x9890f98, return_value=0x0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in rhythmbox:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=571175

Changed in rhythmbox:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in rhythmbox:
status: Unknown → New
Changed in rhythmbox:
importance: Unknown → Critical
Changed in rhythmbox:
status: New → Incomplete
Revision history for this message
Omer Akram (om26er) wrote :

could anyone confirm if the issue is still happening with rhythmbox 0.12.8 or 0.13.2

Changed in rhythmbox (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: Triaged → Incomplete
Changed in rhythmbox:
status: Incomplete → Expired
Revision history for this message
Omer Akram (om26er) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in rhythmbox (Ubuntu):
status: Incomplete → Invalid
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.