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 407474 - crash in Image Viewer:
crash in Image Viewer:
Status: RESOLVED DUPLICATE of bug 354106
Product: eog
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-13 14:07 UTC by Nigel Burman
Modified: 2007-02-13 20:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Nigel Burman 2007-02-13 14:07:17 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: 68259840 vsize: 0 resident: 68259840 share: 0 rss: 28823552 rss_rlim: 0
CPU usage: start_time: 1171375470 rtime: 0 utime: 1660 stime: 0 cutime:1562 cstime: 0 timeout: 98 it_real_value: 0 frequency: 5

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 -1226111312 (LWP 12380)]
[New Thread -1261945952 (LWP 12383)]
[New Thread -1227617376 (LWP 12381)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 110386

Thread 1 (Thread -1226111312 (LWP 12380))

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


Susana





          2007-02-13 20:12:54 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

This issue is already fixed. Thanks.

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