rhythmbox crashed with SIGSEGV in g_atomic_int_exchange_and_add()

Bug #123562 reported by Juan Pablo Salazar Bertín
50
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Rhythmbox
Expired
Critical
rhythmbox (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

I tried to reproduce http://www.rockandpop.cl/player/rockandpop_cl.asx, but I hadn't the codecs. A "couldn't start playback" window was shown. I closed rhythmbox..

ProblemType: Crash
Architecture: i386
Date: Mon Jul 2 10:17:50 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: cdrom
Package: rhythmbox 0.11.1-0ubuntu2
PackageArchitecture: i386
ProcCmdline: rhythmbox
ProcCwd: /home/snifer
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 g_atomic_int_exchange_and_add ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: rhythmbox crashed with SIGSEGV in g_atomic_int_exchange_and_add()
Uname: Linux snifer-laptop 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0xb6f95749 <g_atomic_int_exchange_and_add+9>: lock xadd %eax,(%edx)
 PC (0xb6f95749) ok
 source "%eax" ok
 destination "(%edx)" (0xaaaaaac6) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA

Tags: apport-crash
Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:rhythmdb_event_free (db=0x83f50a0, result=0x895f6f8) at rhythmdb.c:630
rhythmdb_shutdown (db=0x83f50a0) at rhythmdb.c:714
rb_shell_finalize (object=0x81f7000) at rb-shell.c:957
IA__g_object_unref (_object=0x81f7000) at /build/buildd/glib2.0-2.13.5/gobject/gobject.c:1793
IA__g_closure_invoke (closure=0x821b960, return_value=0xbfbc5150, n_param_values=2, param_values=0xbfbc525c, invocation_hint=0xbfbc513c)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Sebastien Bacher (seb128) 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=453125

Changed in rhythmbox:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Confirmed
Changed in rhythmbox:
status: Unknown → New
Changed in rhythmbox:
status: Confirmed → Triaged
Kees Cook (kees)
description: updated
Changed in rhythmbox:
importance: Unknown → Critical
Changed in rhythmbox:
status: New → Incomplete
Revision history for this message
Omer Akram (om26er) wrote :

thanks for the bug report. is it 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
Revision history for this message
Victor Vargas (kamus) wrote :

Since that stream url is not valid and your release is too old I will close this report for now, but if you encounter that this issue is still affecting you using latest release included in Ubuntu Maverick, please reopened again. Thanks in advance

Changed in rhythmbox (Ubuntu):
status: Incomplete → Invalid
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:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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