Bug 462230 – 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 462230 - crash in Image Viewer:


Summary:	crash in Image Viewer:


Status:	RESOLVED DUPLICATE of bug 348651

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-07-31 17:42 UTC by jmikemoya
Modified:	2007-07-31 20:14 UTC

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

Description jmikemoya 2007-07-31 17:42:57 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: 92213248 vsize: 0 resident: 92213248 share: 0 rss: 33767424 rss_rlim: 0
CPU usage: start_time: 1185903662 rtime: 0 utime: 1667 stime: 0 cutime:1592 cstime: 0 timeout: 75 it_real_value: 0 frequency: 3

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 -1226794816 (LWP 10367)]
[New Thread -1287365728 (LWP 10376)]
[New Thread -1228301408 (LWP 10371)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 151886

Thread 1 (Thread -1226794816 (LWP 10367))

#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 cmsSetLanguage
from /usr/lib/liblcms.so.1
#5 ??
#0 __kernel_vsyscall

Comment 1 Martin Ejdestig 2007-07-31 18:21:11 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 problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.

Comment 2 André Klapper 2007-07-31 19:09:59 UTC

hej martin, for future reference, please mark the bug as a duplicate by just using the dupe+fixed answer, instead of clicking twice, on duplicate and fixed_in_head :)

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

Comment 3 Martin Ejdestig 2007-07-31 20:14:07 UTC

Oups. Don't know what happened here. I guess I looked at the different answers by clicking  on them and didn't notice that it left the earlier one in there. Sorry.