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 422827 - crash in Image Viewer: viewing a slide show fro...
crash in Image Viewer: viewing a slide show fro...
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-03-25 22:58 UTC by bruce.lerner
Modified: 2007-03-27 19:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description bruce.lerner 2007-03-25 22:58:55 UTC 
Version: 2.16.1

What were you doing when the application crashed?
viewing a slide show from Eye of GNOME 2.16.1.


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

Memory status: size: 118398976 vsize: 0 resident: 118398976 share: 0 rss: 46530560 rss_rlim: 0
CPU usage: start_time: 1174863255 rtime: 0 utime: 5428 stime: 0 cutime:5272 cstime: 0 timeout: 156 it_real_value: 0 frequency: 4

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 -1226049344 (LWP 6064)]
[New Thread -1313207392 (LWP 6069)]
[New Thread -1227560032 (LWP 6066)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 122224

Thread 1 (Thread -1226049344 (LWP 6064))

  • #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-03-27 19:48:30 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 ***