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 407071 - 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-02-12 14:12 UTC by contact
Modified: 2007-02-12 19:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description contact 2007-02-12 14:12:10 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: 100085760 vsize: 0 resident: 100085760 share: 0 rss: 34402304 rss_rlim: 0
CPU usage: start_time: 1171289464 rtime: 0 utime: 1089 stime: 0 cutime:1049 cstime: 0 timeout: 40 it_real_value: 0 frequency: 3

Backtrace was generated from '/usr/bin/eog'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225987904 (LWP 8943)]
[New Thread -1295082576 (LWP 8945)]
[New Thread -1227953232 (LWP 8944)]
(no debugging symbols found)
0xb7701c21 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 110083

Thread 1 (Thread -1225987904 (LWP 8943))

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 cmsSetLanguage
    from /usr/lib/liblcms.so.1
  • #4 ??
  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0 






Comment 1


Susana





          2007-02-12 19:11:14 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 ***