GNOME Bugzilla – Bug 461340
crash in Image Viewer: I was viewing stereogram...
Last modified: 2007-09-10 22:10:07 UTC
Version: 2.18.2 What were you doing when the application crashed? I was viewing stereograms (about 400kB each), and then after cycling through the four in the folder (pressing the right arrow key to advance through them), and arriving back at the first, I clicked ctrl-W to close the window. Thus, it crashed! It did so as I was closing, though, so I do not mind *too* much :) 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.1-27.fc7 #1 SMP Tue Jul 17 17:19:58 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Simple Icon Theme: Bluecurve Memory status: size: 422293504 vsize: 422293504 resident: 42942464 share: 30130176 rss: 42942464 rss_rlim: 18446744073709551615 CPU usage: start_time: 1185663358 rtime: 148 utime: 122 stime: 26 cutime:6 cstime: 22 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/eog' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496387280 (LWP 26665)] [New Thread 1094719824 (LWP 26667)] [New Thread 1084229968 (LWP 26666)] (no debugging symbols found) 0x000000361140d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 151251
Thread 1 (Thread 46912496387280 (LWP 26665))
----------- .xsession-errors (234941 sec old) --------------------- Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/xfs (total watches = 1955) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/fuse (total watches = 1956) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/jbd2 (total watches = 1957) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/hugetlbfs (total watches = 1958) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/proc (total watches = 1959) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/hostfs (total watches = 1960) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/ocfs2 (total watches = 1961) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/ufs (total watches = 1962) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/sysfs (total watches = 1963) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/qnx4 (total watches = 1964) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/minix (total watches = 1965) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/sysv (total watches = 1966) Watching directory /home/richard/rpmbuild/kernel-2.6.21.new/vanilla/fs/nfs_common (total watches = 1967) ...Too much output, ignoring rest... --------------------------------------------------
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!
*** Bug 466525 has been marked as a duplicate of this bug. ***
Reopening because of the duplicate. Bug 466525 don't have a correct stacktrace either, but the xsession-errors is correct : (eog:6685): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `EogFullScreen' (eog:6685): Eog-CRITICAL **: eog_image_list_iter_valid: assertion `EOG_IS_IMAGE_LIST (list)' failed (eog:6685): Eog-CRITICAL **: eog_image_has_data: assertion `EOG_IS_IMAGE (img)' failed (eog:6685): GLib-GObject-CRITICAL **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed
*** Bug 475592 has been marked as a duplicate of this bug. ***
This is most likely the same problem as bug 354327. The development version shouldn't show that behaviour anymore. --- 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 354327 ***