eog crashed with SIGSEGV in visible_range_changed_cb()

Bug #858197 reported by Chris Bainbridge on 2011-09-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eog (Ubuntu)
Low
Unassigned

Bug Description

Happens seemingly randomly with multiple eog windows open.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: eog 3.1.92-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Sat Sep 24 02:48:06 2011
ExecutablePath: /usr/bin/eog
ProcCmdline: eog
ProcCwd: /home/chrb
SegvAnalysis:
 Segfault happened at: 0x44ca49 <visible_range_changed_cb+41>: movl $0x0,0x18(%rax)
 PC (0x0044ca49) ok
 source "$0x0" ok
 destination "0x18(%rax)" (0xaaaaaaaaaaaaaac2) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: eog
StacktraceTop:
 visible_range_changed_cb (thumbview=0x25f0950) at eog-thumb-view.c:244
 g_main_dispatch (context=0x2116460) at /build/buildd/glib2.0-2.29.92/./glib/gmain.c:2441
 g_main_context_dispatch (context=0x2116460) at /build/buildd/glib2.0-2.29.92/./glib/gmain.c:3011
 g_main_context_iterate (context=0x2116460, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.29.92/./glib/gmain.c:3089
 g_main_loop_run (loop=0x21eb9e0) at /build/buildd/glib2.0-2.29.92/./glib/gmain.c:3297
Title: eog crashed with SIGSEGV in visible_range_changed_cb()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip floppy fuse lp lpadmin plugdev sambashare sudo video

Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in eog (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for eog (Ubuntu) because there has been no activity for 60 days.]

Changed in eog (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers