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 412103 - crash in Image Viewer:
crash in Image Viewer:
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-02-26 01:28 UTC by sergiobasil
Modified: 2007-02-26 10:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description sergiobasil 2007-02-26 01:28:05 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: 62431232 vsize: 0 resident: 62431232 share: 0 rss: 27074560 rss_rlim: 0
CPU usage: start_time: 1172452620 rtime: 0 utime: 2542 stime: 0 cutime:2320 cstime: 0 timeout: 222 it_real_value: 0 frequency: 58

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 -1225914704 (LWP 7329)]
[New Thread -1249944672 (LWP 7334)]
[New Thread -1228239968 (LWP 7333)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 113921

Thread 1 (Thread -1225914704 (LWP 7329))

  • #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 ??
  • #5 ??
  • #6 cmsCloseProfile
    from /usr/lib/liblcms.so.1
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 eog_image_free_mem_private
  • #0 __kernel_vsyscall 






Comment 1


Felix Riemann





          2007-02-26 10:40:47 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 ***