rhythmbox crashed with SIGSEGV in g_closure_invoke()

Bug #632290 reported by Damien Cassou
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

I was closing the application

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: rhythmbox 0.13.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
NonfreeKernelModules: nvidia wl
Architecture: i386
Date: Tue Sep 7 11:40:14 2010
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100831.2)
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x2369f35: mov 0x30(%esi),%eax
 PC (0x02369f35) ok
 source "0x30(%esi)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/libindicate.so.4
 ?? () from /usr/lib/libdbus-glib-1.so.2
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Damien Cassou (cassou) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 dbus_owner_change (proxy=0x9c9c6a8,
 _dbus_g_marshal_VOID__STRING_STRING_STRING (
 marshal_dbus_message_to_g_marshaller (closure=0xa2b61c8,
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
security vulnerability: yes → no
visibility: private → public
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.