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 376747 - crash in Image Viewer: Viewing a slideshow on f...
crash in Image Viewer: Viewing a slideshow on f...
Status: RESOLVED DUPLICATE of bug 364331
Product: eog
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-18 18:45 UTC by Karolina Szablewska
Modified: 2006-11-18 18:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Karolina Szablewska 2006-11-18 18:45:39 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Viewing a slideshow on fullscreen, then pressing ESC to exit it.


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

Memory status: size: 75239424 vsize: 0 resident: 75239424 share: 0 rss: 37281792 rss_rlim: 0
CPU usage: start_time: 1163874617 rtime: 0 utime: 12066 stime: 0 cutime:11359 cstime: 0 timeout: 707 it_real_value: 0 frequency: 43

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 -1225836880 (LWP 7813)]
[New Thread -1266332768 (LWP 7818)]
[New Thread -1227342944 (LWP 7814)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 87514

Thread 1 (Thread -1225836880 (LWP 7813))

  • #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 free
    from /lib/tls/i686/cmov/libc.so.6
  • #5 cmsCloseProfile
    from /usr/lib/liblcms.so.1
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2006-11-18 18:51:01 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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