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 412739 - crash in Image Viewer: Eye of Gnome 2.16.1 cras...
crash in Image Viewer: Eye of Gnome 2.16.1 cras...
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-27 19:25 UTC by esa.raikkonen
Modified: 2007-02-27 19:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description esa.raikkonen 2007-02-27 19:25:01 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Eye of Gnome 2.16.1 crashes when browsing at the end of the group of photos.  


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

Memory status: size: 152027136 vsize: 0 resident: 152027136 share: 0 rss: 88899584 rss_rlim: 0
CPU usage: start_time: 1172604071 rtime: 0 utime: 1313 stime: 0 cutime:1254 cstime: 0 timeout: 59 it_real_value: 0 frequency: 2

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 -1226332496 (LWP 11815)]
[New Thread -1291936864 (LWP 11817)]
[New Thread -1227838560 (LWP 11816)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 114387

Thread 1 (Thread -1226332496 (LWP 11815))

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


Claudio Saavedra





          2007-02-27 19:31:55 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 ***