Rhythmbox crashes with SIGSEGV every time after changing the path for the music collection in the settings

Bug #976441 reported by Dejan Milosavljevic
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After changing the directory in the setting (the path where rhytmbox can find my music-collection), rhytmbox crashes. (Ubuntu 12.04 final beta). I can reproduce the crash, it happens every time I change the directory-path in the settings.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.96-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
Uname: Linux 3.2.0-22-generic-pae i686
ApportVersion: 2.0-0ubuntu4
Architecture: i386
Date: Sun Apr 8 10:40:24 2012
Disassembly: => 0xb71de616: Cannot access memory at address 0xb71de616
ExecutablePath: /usr/bin/rhythmbox
ProcCmdline: rhythmbox
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
Title: rhythmbox crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Dejan Milosavljevic (dejanmilo) wrote :
visibility: private → public
summary: - rhythmbox crashed with SIGSEGV
+ Rhythmbox crashed with SIGSEGV after changing the path for the music
+ collection in the settings
summary: - Rhythmbox crashed with SIGSEGV after changing the path for the music
- collection in the settings
+ Rhythmbox crashes with SIGSEGV every time after changing the path for
+ the music collection in the settings
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()

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):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libv4l-0: package version 0.8.6-1ubuntu1 dbgsym version 0.8.5-3ubuntu2
outdated debug symbol package for upstart: package version 1.5-0ubuntu3 dbgsym version 1.3-0ubuntu11

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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.