Banshee.exe crashed with SIGSEGV

Bug #759136 reported by npavlica
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: banshee

Banshee crashed when playing back music. I was switching between a preview track on the Ubuntu One music service to a local music file stored on the computer.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: banshee 2.0.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CheckboxSubmission: 14791328bb0c4d8a3ed677255d18caf2
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Tue Apr 12 13:52:52 2011
Disassembly: => 0x7f763c3f26f2: Cannot access memory at address 0x7f763c3f26f2
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
SegvAnalysis:
 Segfault happened at: 0x7f763c3f26f2: Cannot access memory at address 0x7f763c3f26f2
 PC (0x7f763c3f26f2) ok
 Stack memory exhausted (SP below stack segment)
 SP (0x7f763c5d7bf8) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: banshee
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: Banshee.exe crashed with SIGSEGV
UpgradeStatus: Upgraded to natty on 2011-04-11 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
npavlica (linicks) wrote :
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
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Victor Vargas (kamus) wrote :

Please could you run in a terminal 'banshee --debug' and attach all the output information (while you are trying to reproduce this issue)?, also attach your '~/.config/banshee-1/log' file as a separated attach, Thanks.

visibility: private → public
Changed in banshee (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
npavlica (linicks) wrote : Re: [Bug 759136] Re: Banshee.exe crashed with SIGSEGV
  • log Edit (1.8 KiB, application/octet-stream; name=log)
Download full text (13.5 KiB)

Kamus,

I hope this will help!

On Thu, Apr 14, 2011 at 1:57 PM, Kamus <email address hidden> wrote:

> Please could you run in a terminal 'banshee --debug' and attach all the
> output information (while you are trying to reproduce this issue)?

#################################################### START
#########################################################
$ banshee --debug
** Running Mono with --debug **
[1 Info 17:42:21.481] Running Banshee 2.0.0: [Ubuntu Natty (development
branch) (linux-gnu, x86_64) @ 2011-04-09 07:44:31 UTC]
[1 Debug 17:42:21.495] Initializing GTK
[1 Debug 17:42:22.593] Post-Initializing GTK
[1 Debug 17:42:22.601] Configuration client extension loaded
(Banshee.GnomeBackend.GConfConfigurationClient)
[1 Debug 17:42:22.609] Using default gconf-base-key
[1 Debug 17:42:22.636] Bus.Session.RequestName
('org.bansheeproject.Banshee') replied with PrimaryOwner
[1 Debug 17:42:22.695] Core service started (DBusServiceManager, 0.000989)
[1 Debug 17:42:22.697] Registering remote object
/org/bansheeproject/Banshee/DBusCommandService
(Banshee.ServiceStack.DBusCommandService) on org.bansheeproject.Banshee
[1 Debug 17:42:22.705] Core service started (DBusCommandService, 0.009255)
[1 Debug 17:42:22.732] Opened SQLite (version 3.7.4) connection to
/home/npavlica/.config/banshee-1/banshee.db
[1 Debug 17:42:22.732] Core service started (DbConnection, 0.027121)
[1 Debug 17:42:22.738] Database version 43 is up to date
[1 Debug 17:42:22.761] Core service started (PreferenceService, 0.00885)
[1 Debug 17:42:22.765] Core service started (Network, 0.00472)
[1 Debug 17:42:22.766] Registering remote object
/org/bansheeproject/Banshee/SourceManager (Banshee.Sources.SourceManager) on
org.bansheeproject.Banshee
[1 Debug 17:42:22.766] Core service started (SourceManager, 0.000484)
[1 Debug 17:42:22.773] Core service started (MediaProfileManager, 0.000209)
[1 Debug 17:42:22.775] Registering remote object
/org/bansheeproject/Banshee/PlayerEngine
(Banshee.MediaEngine.PlayerEngineService) on org.bansheeproject.Banshee
[1 Debug 17:42:22.777] Core service started (PlayerEngine, 0.003515)
[1 Debug 17:42:22.789] Registering remote object
/org/bansheeproject/Banshee/PlaybackController
(Banshee.PlaybackController.PlaybackControllerService) on
org.bansheeproject.Banshee
[1 Debug 17:42:22.790] Core service started (PlaybackController, 0.002584)
[1 Debug 17:42:22.796] Starting - Startup Job
[1 Debug 17:42:22.797] Core service started (JobScheduler, 0.007062)
[1 Debug 17:42:22.808] IO provider extension loaded
(Banshee.IO.Gio.Provider)
[1 Debug 17:42:22.835] Loaded HardwareManager backend: Banshee.Hardware.Gio
[1 Debug 17:42:22.836] Core service started (HardwareManager, 0.039257)
[1 Debug 17:42:22.837] Bus.Session.RequestName
('org.bansheeproject.CollectionIndexer') replied with PrimaryOwner
[1 Debug 17:42:22.839] Registering remote object
/org/bansheeproject/Banshee/CollectionIndexerService
(Banshee.Collection.Indexer.CollectionIndexerService) on
org.bansheeproject.CollectionIndexer
[1 Debug 17:42:22.840] Core service started (CollectionIndexerService,
0.003902)
[1 Debug 17:42:22.841] Core service started (SaveTrackMetadataService,
0.001205)
[1 Debug 17:42:22.8...

Revision history for this message
Victor Vargas (kamus) wrote :

Please can you try to disabled LibraryWatcher and Gapless and then check if banshee works fine for you again? Thank you

Revision history for this message
Victor Vargas (kamus) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for banshee (Ubuntu) because there has been no activity for 60 days.]

Changed in banshee (Ubuntu):
status: Incomplete → Expired
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.