eog crashed with SIGSEGV in eog_job_queue_remove_job()

[Rich]

Binary package hint: eog

I was trying to view images as I downloaded them off of my camera - I switched to one of the as-yet-unthumbnailed images, and eog crashed.

ProblemType: Crash
Architecture: i386
Date: Mon Feb 4 04:10:50 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/eog
NonfreeKernelModules: nvidia
Package: eog 2.21.4-0ubuntu1
PackageArchitecture: i386
ProcCmdline: eog IMG_5450.JPG
ProcCwd: /home/rich/camera
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/bin/zfs/:/home/rich/bin:/usr/local/bin/zfs/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: eog
StacktraceTop:
 eog_job_queue_remove_job ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: eog crashed with SIGSEGV in eog_job_queue_remove_job()
Uname: Linux eris 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse pulse-access pulse-rt scanner src video
SegvAnalysis:
 Segfault happened at: 0x8085996 <eog_job_queue_remove_job+38>: cmp %eax,(%edx)
 PC (0x08085996) ok
 source "%eax" ok
 destination "(%edx)" (0x0000000b) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA

[Apport retracing service (apport)]

StacktraceTop:eog_job_queue_remove_job (job=0x839d568) at eog-job-queue.c:214
eog_list_store_remove_thumbnail_job (store=0x819e720, iter=0xbfbbf04c)
eog_list_store_thumbnail_unset (store=0x819e720, iter=0xbfbbf04c) at eog-list-store.c:786
eog_thumb_view_clear_range (tb=<value optimized out>, start_thumb=1016, end_thumb=1023)
tb_on_visible_range_changed_cb (tb=0x8359008, user_data=0x80e0f10) at eog-thumb-view.c:167

[Pedro Villavicencio (pedro)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=514294

[Martin Olsson (mnemo)]

Rich, if you can attach a copy of the image that causes this crash that would be helpful both for fixing this bug and also for regression testing. Thanks.

[Pedro Villavicencio (pedro)]

are you still able to reproduce this with Maverick?

[Pedro Villavicencio (pedro)]

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!