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 393308 - 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-01-05 22:39 UTC by cedric
Modified: 2007-01-06 04:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description cedric 2007-01-05 22:39:31 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: 98783232 vsize: 0 resident: 98783232 share: 0 rss: 36339712 rss_rlim: 0
CPU usage: start_time: 1168035543 rtime: 0 utime: 2041 stime: 0 cutime:1975 cstime: 0 timeout: 66 it_real_value: 0 frequency: 5

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 -1225811776 (LWP 16166)]
[New Thread -1292125280 (LWP 16169)]
[New Thread -1227699296 (LWP 16168)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 99715

Thread 1 (Thread -1225811776 (LWP 16166))

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


Susana





          2007-01-06 04:33:39 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 ***