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 421061 - crash in Image Viewer:
crash in Image Viewer:
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-03-21 15:02 UTC by dl7auq
Modified: 2007-03-21 17:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description dl7auq 2007-03-21 15:02:42 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: 87871488 vsize: 0 resident: 87871488 share: 0 rss: 30306304 rss_rlim: 0
CPU usage: start_time: 1174489296 rtime: 0 utime: 519 stime: 0 cutime:489 cstime: 0 timeout: 30 it_real_value: 0 frequency: 0

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 -1225881408 (LWP 10904)]
[New Thread -1277920352 (LWP 10928)]
[New Thread -1259136096 (LWP 10925)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 120787

Thread 1 (Thread -1225881408 (LWP 10904))

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


Timm F. Gloger





          2007-03-21 17:09:47 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 seems to be a duplicate of Bug 348651.






Comment 2


Jens Granseuer





          2007-03-21 17:12:52 UTC
        




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