Banshee 2.0 crashes about 5 seconds after launch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
banshee (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: banshee
Errors from command line launch:
[Info 01:34:43.432] Running Banshee 2.0.0: [Ubuntu Natty (development branch) (linux-gnu, x86_64) @ 2011-04-09 07:44:31 UTC]
[Info 01:34:45.286] Updating web proxy from GConf
[Info 01:34:45.352] All services are started 1.584815
** (Banshee:2251): DEBUG: SyncDaemon already running, initializing SyncdaemonDaemon object
(Banshee:2251): libsoup-WARNING **: No feature manager for feature of type 'U1RequestChrome'
** (Banshee:2251): WARNING **: Error rescanning Purchased Music: No such file or directory
** (Banshee:2251): DEBUG: Loading the real store page
[Info 01:34:47.259] nereid Client Started
[Info 01:34:47.373] GStreamer version 0.10.32.0, gapless: True, replaygain: False
[Info 01:34:47.649] AppleDeviceSource is ignoring unmounted volume Ubuntu
[Info 01:34:47.759] AppleDeviceSource is ignoring unmounted volume 32 GB Filesystem
[Info 01:34:47.785] AppleDeviceSource is ignoring unmounted volume OS
Native stacktrace:
banshee() [0x489171]
banshee() [0x41ad3f]
/lib/x86_
/lib/libnss_
/lib/x86_
/lib/x86_
/lib/x86_
/usr/lib/
/usr/lib/
/lib/x86_
/lib/x86_
/lib/x86_
/lib/x86_
Debug info from gdb:
Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/
again as the root user. For more details, see /etc/sysctl.
ptrace: Operation not permitted.
=======
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=======
Aborted (core dumped)
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 529714, so it 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.