rhythmbox crashed with SIGSEGV in g_closure_invoke()

Bug #621408 reported by Edgar Cherkasov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: rhythmbox

bug detected after closing

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: rhythmbox 0.13.0git20100715-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.35-16.22-generic 2.6.35.2
Uname: Linux 2.6.35-16-generic x86_64
Architecture: amd64
Date: Sat Aug 21 01:09:07 2010
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=ru_RU.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1ee4bf3e40: mov 0x58(%rax),%rdi
 PC (0x7f1ee4bf3e40) ok
 source "0x58(%rax)" (0x00000058) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/libindicate.so.4
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
Title: rhythmbox crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Edgar Cherkasov (edgar2705) wrote :
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.