Bug 411688 – crash in Image Viewer:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 411688 - crash in Image Viewer:


Summary:	crash in Image Viewer:


Status:	RESOLVED DUPLICATE of bug 354106

Product:	eog
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	EOG Maintainers
QA Contact:	EOG Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-24 21:17 UTC by ppat
Modified:	2007-02-24 21:37 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description ppat 2007-02-24 21:17:30 UTC

Version: 2.16.1

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 99184640 vsize: 0 resident: 99184640 share: 0 rss: 41033728 rss_rlim: 0
CPU usage: start_time: 1172351488 rtime: 0 utime: 10835 stime: 0 cutime:9985 cstime: 0 timeout: 850 it_real_value: 0 frequency: 21

Backtrace was generated from '/usr/bin/eog'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225996096 (LWP 6148)]
[New Thread -1289630816 (LWP 6153)]
[New Thread -1228018784 (LWP 6149)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 113605

Thread 1 (Thread -1225996096 (LWP 6148))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 cmsCloseProfile
from /usr/lib/liblcms.so.1
#6 ??
#7 ??
#8 ??
#9 eog_image_free_mem_private
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2007-02-24 21:37:57 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 354106 ***