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 409157 - crash in Image Viewer: Slideshow had been runni...
crash in Image Viewer: Slideshow had been runni...
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-02-18 04:01 UTC by vanselm
Modified: 2007-02-18 05:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description vanselm 2007-02-18 04:01:48 UTC
Version: 2.16.1

What were you doing when the application crashed?
Slideshow had been running.  No other apps were open.


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

Memory status: size: 110735360 vsize: 0 resident: 110735360 share: 0 rss: 54620160 rss_rlim: 0
CPU usage: start_time: 1171721889 rtime: 0 utime: 756193 stime: 0 cutime:708848 cstime: 0 timeout: 47345 it_real_value: 0 frequency: 2306

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 -1226528576 (LWP 6794)]
[New Thread -1291162720 (LWP 6796)]
[New Thread -1228035168 (LWP 6795)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226528576 (LWP 6794))

  • #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 Claudio Saavedra 2007-02-18 05:01:56 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 348651 ***