eog crashed with SIGSEGV

Bug #869932 reported by Merlin Schumacher
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eog (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Opening a JPG-File caused EOG to crash. On the second try it worked just fine.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: eog 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CheckboxSubmission: 18167c3e7e3fc2fdbde68b6899d0683f
CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
Date: Fri Oct 7 13:59:09 2011
Disassembly: => 0x7f247628b992: Cannot access memory at address 0x7f247628b992
ExecutablePath: /usr/bin/eog
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: eog /home/username/IMG_20110921_000452.jpg
SegvAnalysis:
 Segfault happened at: 0x7f247628b992: Cannot access memory at address 0x7f247628b992
 PC (0x7f247628b992) ok
 SP (0x7fff94d80348) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: eog
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: eog crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-10-02 (5 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare sudo tape vboxusers video

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote :
visibility: private → public
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
Changed in eog (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:

outdated debug symbol package for libavahi-common3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for libtiff4: package version 3.9.5-1ubuntu1 dbgsym version 3.9.4-5ubuntu6
outdated debug symbol package for libk5crypto3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libexif12: package version 0.6.20-1 dbgsym version 0.6.20-0ubuntu1
outdated debug symbol package for libavahi-client3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for libkrb5-3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libdatrie1: package version 0.2.4-3 dbgsym version 0.2.4-1
outdated debug symbol package for libgssapi-krb5-2: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for liblaunchpad-integration-3.0-1: package version 0.1.54 dbgsym version 0.1.51
outdated debug symbol package for libkrb5support0: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libthai0: package version 0.1.15-2 dbgsym version 0.1.14-2ubuntu1

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-amd64-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.