f-spot.exe crashed with SIGSEGV

Bug #130712 reported by pliz
6
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: f-spot

This bug is a duplicate of this one Bug #123764 I do not know how to obtain the output of apport that I got and add it to the bug already reported. I believe it is valuable for the above bug, since it has debugging symbols for f-spot. Please attach the info I am submitting to the bug above. Thank you!

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Aug 6 12:49:29 2007
Disassembly: 0xb6bda490:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/f-spot/f-spot.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: ath_hal nvidia
Package: f-spot 0.3.5-1
PackageArchitecture: i386
ProcCmdline: f-spot /usr/lib/f-spot/f-spot.exe
ProcCwd: /home/pliz
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: f-spot
Stacktrace: #0 0xb6bda490 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: f-spot.exe crashed with SIGSEGV
Uname: Linux okorok 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
pliz (pliz) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The info that you submitted is not really helpful may you try again? Thanks in advance.

Changed in f-spot:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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.