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 490181 - crash in Image Viewer: alj
crash in Image Viewer: alj
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-10-25 15:33 UTC by J_I_K_K_E
Modified: 2007-10-27 12:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description J_I_K_K_E 2007-10-25 15:33:16 UTC
Version: 2.18.2

What were you doing when the application crashed?
alj


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 34578432 vsize: 34578432 resident: 6344704 share: 5185536 rss: 6344704 rss_rlim: 4294967295
CPU usage: start_time: 1193326362 rtime: 9 utime: 5 stime: 4 cutime:0 cstime: 0 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 -1208150304 (LWP 3267)]
[New Thread -1210250352 (LWP 3268)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1210250352 (LWP 3268))

  • #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 (9 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600c07 (Dia-ontwer)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600c07 (Dia-ontwer)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600c07 (Dia-ontwer)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600c07 (Dia-ontwer)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600c07 (Dia-ontwer)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** Message: Failed to close thumbnail pixbuf loader for /media/TOS4300_Jikke/Tos4300/REDCAT/MENU.IND: TGA image has invalid dimensions
** Message: Failed to close thumbnail pixbuf loader for /media/TOS4300_Jikke/Tos4300/REDCAT/MENU.IND: TGA image has invalid dimensions
Eog-ERROR **: file eog-image.c: line 777 (eog_image_real_load): assertion failed: (priv->image != NULL)
aborting...
--------------------------------------------------
Comment 1 Felix Riemann 2007-10-27 12:02:42 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 version 2.20. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 354327 ***
Comment 2 Felix Riemann 2007-10-27 12:04:36 UTC
Sorry, wrong duplicate.
Comment 3 Felix Riemann 2007-10-27 12:04:58 UTC

*** This bug has been marked as a duplicate of 357405 ***