rhythmbox-metadata crashed with SIGSEGV in connection_closed_cb()

Bug #879042 reported by ducciopiomb
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

The program crashed when I've attached a Creative Zen player on Ubuntu

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: rhythmbox 2.90.1~20110908-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Thu Oct 20 21:11:06 2011
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 LANGUAGE=it_IT:it:en_GB:en
 PATH=(custom, user)
 LANG=it_IT.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x804e538 <connection_closed_cb+56>: cmp %eax,0x4(%ebx)
 PC (0x0804e538) ok
 source "%eax" ok
 destination "0x4(%ebx)" (0x00000005) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 connection_closed_cb (connection=0x92c7800, svc=0x1) at rb-metadata-dbus-service.c:216
 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: rhythmbox-metadata crashed with SIGSEGV in connection_closed_cb()
UpgradeStatus: Upgraded to oneiric on 2011-10-13 (6 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy fuse lp lpadmin plugdev sambashare vboxusers video

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #820601, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
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.