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 455528 - crash in Image Viewer: ingenting,högre+venstre ...
crash in Image Viewer: ingenting,högre+venstre ...
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-07-10 12:16 UTC by birgit.hoj
Modified: 2007-07-10 17:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description birgit.hoj 2007-07-10 12:16:14 UTC
Version: 2.16.1

What were you doing when the application crashed?
ingenting,högre+venstre mysklick,funkade inte(,jag hade bildspel)


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

Memory status: size: 103428096 vsize: 0 resident: 103428096 share: 0 rss: 63959040 rss_rlim: 0
CPU usage: start_time: 1184068246 rtime: 0 utime: 20908 stime: 0 cutime:20195 cstime: 0 timeout: 713 it_real_value: 0 frequency: 37

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 -1225996096 (LWP 4837)]
[New Thread -1285375072 (LWP 4840)]
[New Thread -1227981920 (LWP 4838)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225996096 (LWP 4837))

  • #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-07-10 17:18:22 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 ***