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 424891 - crash in Image Viewer: I was looking at some ph...
crash in Image Viewer: I was looking at some ph...
Status: RESOLVED DUPLICATE of bug 354106
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-31 15:09 UTC by stawo.micky
Modified: 2007-04-01 10:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description stawo.micky 2007-03-31 15:09:54 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I was looking at some photos.
FireFox 2 and Skypre were running in the background.


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

Memory status: size: 74125312 vsize: 0 resident: 74125312 share: 0 rss: 36188160 rss_rlim: 0
CPU usage: start_time: 1175353472 rtime: 0 utime: 8215 stime: 0 cutime:7774 cstime: 0 timeout: 441 it_real_value: 0 frequency: 27

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 -1226340160 (LWP 9659)]
[New Thread -1263858784 (LWP 9662)]
[New Thread -1228641376 (LWP 9660)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 123841

Thread 1 (Thread -1226340160 (LWP 9659))

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


Felix Riemann





          2007-04-01 10:00:50 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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