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 431327 - crash in Image Viewer: przeglądanie zdjęc,obrót...
crash in Image Viewer: przeglądanie zdjęc,obrót...
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-04-19 12:35 UTC by w.sosnowski
Modified: 2007-04-19 14:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description w.sosnowski 2007-04-19 12:35:16 UTC
Version: 2.16.1

What were you doing when the application crashed?
przeglądanie zdjęc,obrót w prawo


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

Memory status: size: 82087936 vsize: 0 resident: 82087936 share: 0 rss: 24440832 rss_rlim: 0
CPU usage: start_time: 1176986010 rtime: 0 utime: 1093 stime: 0 cutime:1029 cstime: 0 timeout: 64 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 -1226422080 (LWP 15226)]
[New Thread -1275327584 (LWP 15228)]
[New Thread -1228272736 (LWP 15227)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226422080 (LWP 15226))

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

Comment 1 Susana 2007-04-19 14:49:03 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 ***