GNOME Bugzilla – Bug 496426
crash in Image Viewer: load an png file into im...
Last modified: 2007-11-15 10:23:37 UTC
Version: 2.18.0.1 What were you doing when the application crashed? load an png file into image viewer 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.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: Glider Icon Theme: gnome Memory status: size: 34729984 vsize: 34729984 resident: 7634944 share: 6344704 rss: 7634944 rss_rlim: 4294967295 CPU usage: start_time: 1194958007 rtime: 6 utime: 4 stime: 2 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 -1208666400 (LWP 5647)] [New Thread -1210946672 (LWP 5648)] (no debugging symbols found) 0x003ff402 in __kernel_vsyscall ()
+ Trace 177405
Thread 2 (Thread -1210946672 (LWP 5648))
----------- .xsession-errors (247691 sec old) --------------------- WARNING: Remote desktop does not support colour depth 24; falling back to 8 X Error of failed request: BadAtom (invalid Atom parameter) Major opcode of failed request: 23 (X_GetSelectionOwner) Atom id in failed request: 0x0 Serial number of failed request: 1991 Current serial number in output stream: 1991 ** (tsclient:3365): WARNING **: Autoselected keyboard map en-gb WARNING: Remote desktop does not support colour depth 24; falling back to 8 X Error of failed request: BadAtom (invalid Atom parameter) Major opcode of failed request: 23 (X_GetSelection ...Too much output, ignoring rest... --------------------------------------------------
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 357405 ***