f-spot.exe crashed with SIGSEGV in exit()

Bug #475913 reported by James Michael DuPont
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: f-spot

Do I have to read all 30 of the bug reports?
Was looking a a pic and closed the app. crash.
mike

ProblemType: Crash
Architecture: i386
Date: Thu Nov 5 22:08:46 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/f-spot/f-spot.exe
InterpreterPath: /usr/bin/mono
LiveMediaBuild: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
NonfreeKernelModules: nvidia
Package: f-spot 0.6.1.3-2
ProcCmdline: f-spot /usr/lib/f-spot/f-spot.exe --view /home/username/Downloads/13752_174479347530_611092530_3465749_2901953_n.jpg
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x839ff48: mov (%eax),%esi
 PC (0x0839ff48) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: f-spot
StacktraceTop:
 ?? () from /usr/lib/libGL.so.1
 ?? () from /lib/tls/i686/cmov/libc.so.6
 exit () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
Tags: ubuntu-unr
Title: f-spot.exe crashed with SIGSEGV in exit()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
James Michael DuPont (jamesmikedupont) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? () from /usr/lib/libGL.so.1
__run_exit_handlers (status=158142632, listp=0x305304,
*__GI_exit (status=0) at exit.c:100
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in f-spot (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

python2.6: installed version 2.6.4~rc2-0ubuntu1, latest version: 2.6.4-0ubuntu1
python-minimal: installed version 2.6.4~rc1-0ubuntu1, latest version: 2.6.4-0ubuntu1
python: installed version 2.6.4~rc1-0ubuntu1, latest version: 2.6.4-0ubuntu1
libpython2.6: installed version 2.6.4~rc2-0ubuntu1, latest version: 2.6.4-0ubuntu1
f-spot: installed version 0.6.1.3-2, latest version: 0.6.1.4-0ubuntu1
python2.6-minimal: installed version 2.6.4~rc2-0ubuntu1, latest version: 2.6.4-0ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
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.