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 445266 - crash in Image Viewer: viewing image
crash in Image Viewer: viewing image
Status: RESOLVED DUPLICATE of bug 357405
Product: eog
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
: 449020 454169 468264 471844 473151 474077 483727 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-07 20:23 UTC by ChaRRAKSUS
Modified: 2007-10-05 14:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ChaRRAKSUS 2007-06-07 20:23:52 UTC
Version: 2.18.0.1

What were you doing when the application crashed?
viewing image


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 141029376 vsize: 141029376 resident: 85655552 share: 10293248 rss: 85655552 rss_rlim: 4294967295
CPU usage: start_time: 1181247605 rtime: 3946 utime: 2336 stime: 1610 cutime:1 cstime: 9 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 -1208875296 (LWP 4899)]
[New Thread -1257825392 (LWP 4901)]
[New Thread -1210975344 (LWP 4900)]
(no debugging symbols found)
0x00ebb402 in __kernel_vsyscall ()

Thread 3 (Thread -1210975344 (LWP 4900))

  • #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 (26 sec old) ---------------------
(eog:4899): Eog-CRITICAL **: eog_image_list_iter_valid: assertion `EOG_IS_IMAGE_LIST (list)' failed
(eog:4899): Eog-CRITICAL **: eog_image_cache_add: assertion `EOG_IS_IMAGE_CACHE (cache)' failed
(eog:4899): Eog-CRITICAL **: eog_image_list_iter_valid: assertion `EOG_IS_IMAGE_LIST (list)' failed
(eog:4899): Eog-CRITICAL **: eog_image_list_iter_valid: assertion `EOG_IS_IMAGE_LIST (list)' failed
(eog:4899): Eog-WARNING **: Image 100_2504.jpg has requested data already loaded.
Eog-ERROR **: file eog-image.c: line 662 (eog_image_real_load): assertion failed: (priv->image == NULL)
aborting...
Xlib: unexpected async reply (sequence 0x6f73)!
--------------------------------------------------
Comment 1 Claudio Saavedra 2007-06-25 17:10:07 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 palfrey 2007-07-06 14:42:48 UTC
*** Bug 454169 has been marked as a duplicate of this bug. ***
Comment 3 Pedro Villavicencio 2007-07-18 21:48:02 UTC
*** Bug 449020 has been marked as a duplicate of this bug. ***
Comment 4 Pedro Villavicencio 2007-07-18 21:48:47 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 5 palfrey 2007-08-20 16:29:32 UTC
*** Bug 468264 has been marked as a duplicate of this bug. ***
Comment 6 palfrey 2007-08-30 16:31:27 UTC
*** Bug 471844 has been marked as a duplicate of this bug. ***
Comment 7 palfrey 2007-09-03 16:49:06 UTC
*** Bug 473151 has been marked as a duplicate of this bug. ***
Comment 8 palfrey 2007-09-06 12:02:54 UTC
*** Bug 474077 has been marked as a duplicate of this bug. ***
Comment 9 Claudio Saavedra 2007-09-08 01:09:42 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 357405 ***
Comment 10 palfrey 2007-10-05 14:03:30 UTC
*** Bug 483727 has been marked as a duplicate of this bug. ***