rhythmbox crashed with SIGSEGV

[Piotr Tarsa]

rhythmbox crashes a second or two after opening
i have a ntfs disk mounted and a large number of songs are loaded from that disk (i don't know if that matters here)

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: rhythmbox 2.97-1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-12.12-generic 3.5.2
Uname: Linux 3.5.0-12-generic x86_64
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
Date: Tue Aug 28 19:55:13 2012
Disassembly: => 0x7fe4a07386d5: Cannot access memory at address 0x7fe4a07386d5
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2)
ProcCmdline: rhythmbox
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe4a07386d5: Cannot access memory at address 0x7fe4a07386d5
 PC (0x7fe4a07386d5) ok
 SP (0x7fff286d4740) ok
 Reason could not be automatically determined.
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
XsessionErrors: (indicator-multiload:1953): GLib-GIO-CRITICAL **: GApplication subclass 'Main' failed to chain up on ::startup (from start of override function)

[Apport retracing service (apport)]

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

[Apport retracing service (apport)]

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 libcdparanoia0: package version 3.10.2+debian-11 dbgsym version 3.10.2+debian-10ubuntu1
python3.2-minimal version 3.2.3-3 required, but 3.2.3-4 is available
python2.7 version 2.7.3-0ubuntu4 required, but 2.7.3-4 is available
outdated debug symbol package for libjack-jackd2-0: package version 1.9.8~dfsg.4+20120529git007cdc37-2ubuntu1 dbgsym version 1.9.8~dfsg.1-1ubuntu1
apt version 0.9.7.1ubuntu2 required, but 0.9.7.5ubuntu1 is available
libcups2 version 1.6.1-0ubuntu3 required, but 1.6.1-0ubuntu4 is available
outdated debug symbol package for libcups2: package version 1.6.1-0ubuntu4 dbgsym version 1.6.1-0ubuntu3
outdated debug symbol package for libyelp0: package version 3.5.90-0ubuntu1 dbgsym version 3.4.1-0ubuntu1
gvfs-common version 1.13.7-0ubuntu2 required, but 1.13.7-0ubuntu3 is available
libapt-pkg4.12 version 0.9.7.1ubuntu2 required, but 0.9.7.5ubuntu1 is available
outdated debug symbol package for libcap-ng0: package version 0.6.6-2ubuntu1 dbgsym version 0.6.6-1ubuntu1
apt-utils version 0.9.7.1ubuntu2 required, but 0.9.7.5ubuntu1 is available
libpython2.7 version 2.7.3-0ubuntu4 required, but 2.7.3-4 is available
gvfs-libs version 1.13.7-0ubuntu2 required, but 1.13.7-0ubuntu3 is available
gvfs-daemons version 1.13.7-0ubuntu2 required, but 1.13.7-0ubuntu3 is available
outdated debug symbol package for libfile-fcntllock-perl: package version 0.14-2 dbgsym version 0.14-1build1
libllvm3.1 version 3.1-2 required, but 3.1-2ubuntu1 is available
python3.2 version 3.2.3-3 required, but 3.2.3-4 is available
gvfs version 1.13.7-0ubuntu2 required, but 1.13.7-0ubuntu3 is available
python2.7-minimal version 2.7.3-0ubuntu4 required, but 2.7.3-4 is available
outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu3 dbgsym version 3.16-1ubuntu2
libapt-inst1.5 version 0.9.7.1ubuntu2 required, but 0.9.7.5ubuntu1 is available
libpython3.2 version 3.2.3-3 required, but 3.2.3-4 is available
gvfs-backends version 1.13.7-0ubuntu2 required, but 1.13.7-0ubuntu3 is available
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
outdated debug symbol package for yelp: package version 3.5.90-0ubuntu1 dbgsym version 3.4.1-0ubuntu1

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!