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 496296 - crash in Image Viewer: visualizing hi-res jpg p...
crash in Image Viewer: visualizing hi-res jpg p...
Status: RESOLVED DUPLICATE of bug 357405
Product: eog
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-12 22:53 UTC by rodrey
Modified: 2007-11-20 11:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description rodrey 2007-11-12 22:53:47 UTC 
Version: 2.18.2

What were you doing when the application crashed?
visualizing hi-res jpg pictures on fullscreen (F11)


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 96940032 vsize: 96940032 resident: 50987008 share: 18006016 rss: 50987008 rss_rlim: 4294967295
CPU usage: start_time: 1194907817 rtime: 1702 utime: 1539 stime: 163 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/eog'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208781088 (LWP 9125)]
[New Thread -1245496432 (LWP 9127)]
[New Thread -1211315312 (LWP 9126)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 177310

Thread 3 (Thread -1211315312 (LWP 9126))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 eog_image_load
  • #11 ??
  • #12 eog_job_call_action
  • #13 ??
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 start_thread
    from /lib/libpthread.so.0
  • #16 clone
    from /lib/libc.so.6 


----------- .xsession-errors (25 sec old) ---------------------
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Max failures exceeded, exiting now
(eog:9125): Eog-WARNING **: Image img_8581.jpg has requested data already loaded.
Eog-ERROR **: file eog-image.c: line 666 (eog_image_real_load): assertion failed: (priv->image == NULL)
aborting...
Xlib: unexpected async reply (sequence 0xdef)!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2007-11-20 11:30:12 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 357405 ***