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 467941 - crash in Image Viewer:
crash in Image Viewer:
Status: RESOLVED DUPLICATE of bug 348651
Product: eog
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-18 12:40 UTC by andrern
Modified: 2007-08-19 12:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description andrern 2007-08-18 12:40:32 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: 110084096 vsize: 0 resident: 110084096 share: 0 rss: 74784768 rss_rlim: 0
CPU usage: start_time: 1187440768 rtime: 0 utime: 717 stime: 0 cutime:669 cstime: 0 timeout: 48 it_real_value: 0 frequency: 0

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 -1226246480 (LWP 12748)]
[New Thread -1266275424 (LWP 12750)]
[New Thread -1228420192 (LWP 12749)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 156127

Thread 1 (Thread -1226246480 (LWP 12748))

  • #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


Felix Riemann





          2007-08-19 12:49:38 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 348651 ***