eog crashed with SIGSEGV

Bug #185316 reported by Mikko Ruohola
12
Affects Status Importance Assigned to Milestone
eog (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: eog

Multiple crashes. eog was on background showing an image. after 15-25min it just crashes. don't know yet why.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Jan 23 12:54:41 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/eog
NonfreeKernelModules: cdrom
Package: eog 2.21.4-0ubuntu1
PackageArchitecture: i386
ProcCmdline: eog file:///home/polarfox/Kuva%203.png
ProcCwd: /home/polarfox
ProcEnviron:
 LANGUAGE=fi_FI:fi:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: eog
Stacktrace: #0 0x0806354b in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: eog crashed with SIGSEGV
Uname: Linux polarfox-laptop 2.6.24-4-generic #1 SMP Mon Jan 14 17:30:39 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Mikko Ruohola (polarfox) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:update_image_pos (window=<value optimized out>) at eog-window.c:656

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in eog:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, is this reproducible everytime? May you tell us a few steps in order to reproduce the crash? Does it happens only with that image or with all you're seeing?

Changed in eog:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in eog:
status: Incomplete → Invalid
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.