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 474895 - 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
: 475659 476246 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-08 16:51 UTC by sj843
Modified: 2007-09-12 20:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description sj843 2007-09-08 16:51:28 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: 103301120 vsize: 0 resident: 103301120 share: 0 rss: 46505984 rss_rlim: 0
CPU usage: start_time: 1189194830 rtime: 0 utime: 2382611 stime: 0 cutime:2184614 cstime: 0 timeout: 197997 it_real_value: 0 frequency: 11299

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 -1226778960 (LWP 4460)]
[New Thread -1280283744 (LWP 4464)]
[New Thread -1228285024 (LWP 4461)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226778960 (LWP 4460))

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

Comment 1 Felix Riemann 2007-09-12 20:05:36 UTC
*** Bug 475659 has been marked as a duplicate of this bug. ***
Comment 2 Felix Riemann 2007-09-12 20:06:00 UTC
*** Bug 476246 has been marked as a duplicate of this bug. ***
Comment 3 Felix Riemann 2007-09-12 20:07:02 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 ***