Banshee.exe crashed with SIGSEGV

Bug #602419 reported by aanno on 2010-07-06
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: banshee

apport report

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: banshee 1.6.1-1~lucid1
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
Architecture: amd64
Date: Thu Jul 1 06:44:26 2010
Disassembly: => 0x7f2fa5674de7: Cannot access memory at address 0x7f2fa5674de7
ExecutablePath: /usr/lib/banshee-1/Banshee.exe
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee-1 /usr/lib/banshee-1/Banshee.exe
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f2fa5674de7: Cannot access memory at address 0x7f2fa5674de7
 PC (0x7f2fa5674de7) ok
 SP (0x7f2f97beb060) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: banshee
Stacktrace:
 #0 0x00007f2fa5674de7 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f2f97beb060
StacktraceTop: ?? ()
Title: Banshee.exe crashed with SIGSEGV
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev pulse pulse-access sambashare users video

aanno (thomas-pasch) wrote :

Stacktrace:
 #0 0x00007f2fa5674de7 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f2f97beb060
StacktraceTop: ?? ()
ThreadStacktrace:

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
visibility: private → public
Pedro Villavicencio (pedro) wrote :

Thanks for the report, could you run banshee as: banshee --debug &> debug.txt ; reproduce the bug and attach that resulting log file to the report? thanks in advance.

Changed in banshee (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Victor Vargas (kamus) wrote :

aanno, any news about this issue?

Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in banshee (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers