Ubuntu
f-spot package

f-spot.exe crashed with SIGSEGV

Bug #216510 reported by R S Gill on 2008-04-12

This bug report is a duplicate of: Bug #199496: Tomboy.exe crashed with SIGSEGV in exit(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	f-spot (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: f-spot

Imported pictures into f-spot. Exported those same pictures to Picasa web. Once export was complete, tried to exit f-spot which caused it to crash.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Apr 12 17:00:06 2008
Disassembly: 0xb6baf430:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/f-spot/f-spot.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: nvidia
Package: f-spot 0.4.2-1ubuntu2
PackageArchitecture: i386
ProcCmdline: f-spot /usr/lib/f-spot/f-spot.exe
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 0xb6baf430 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: f-spot.exe crashed with SIGSEGV
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

Tags:

Revision history for this message

R S Gill (rsgill) wrote on 2008-04-12:

Dependencies.txt Edit (5.6 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (29.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (674 bytes, text/plain; charset="utf-8")
Registers.txt Edit (461 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2008-04-12: Symbolic stack trace

Stacktrace.txt (retraced) Edit (23 bytes, text/plain)

StacktraceTop:?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2008-04-12: Stack trace with source code

StacktraceSource.txt Edit (24 bytes, text/plain)

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-04-14:

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.