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 dpkg: package version 1.16.0.3ubuntu3 dbgsym version 1.16.0~ubuntu7.1 outdated debug symbol package for libgpg-error0: package version 1.10-0.3ubuntu1 dbgsym version 1.10-0.2ubuntu1 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 outdated debug symbol package for libltdl7: package version 2.4-2ubuntu1 dbgsym version 2.2.6b-2ubuntu3 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! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/845361/+attachment/2375209/+files/CoreDump.gz ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/845361 Title: eog crashed with SIGSEGV Status in “eog” package in Ubuntu: Invalid Bug description: eog crashed with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: eog 3.1.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic i686 NonfreeKernelModules: wl ApportVersion: 1.22.1-0ubuntu2 Architecture: i386 Date: Fri Sep 9 10:59:57 2011 Disassembly: => 0xaff944: Cannot access memory at address 0xaff944 ExecutablePath: /usr/bin/eog InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: eog /home/username/Desktop/Onam\ latest1.jpg ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xaff944: Cannot access memory at address 0xaff944 PC (0x00aff944) ok SP (0xbfae8c7c) ok Reason could not be automatically determined. Signal: 11 SourcePackage: eog Stacktrace: #0 0x00aff944 in ?? () No symbol table info available. #1 0x00a25ff4 in ?? () No symbol table info available. Backtrace stopped: previous frame inner to this frame (corrupt stack?) StacktraceTop: ?? () ?? () Title: eog crashed with SIGSEGV UpgradeStatus: Upgraded to oneiric on 2011-09-06 (2 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/845361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
