GNOME Bugzilla – Bug 493630
crash in Image Viewer: OPEN favicon.ico VIA Nau...
Last modified: 2007-11-05 08:20:15 UTC
Version: 2.18.2 What were you doing when the application crashed? OPEN favicon.ico VIA Nautilus 2.18.3 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 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 340283392 vsize: 340283392 resident: 6909952 share: 5324800 rss: 6909952 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194245999 rtime: 2 utime: 2 stime: 0 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496358608 (LWP 26730)] [New Thread 1084229968 (LWP 26731)] (no debugging symbols found) 0x0000003bb88c82e6 in poll () from /lib64/libc.so.6
+ Trace 175319
Thread 2 (Thread 1084229968 (LWP 26731))
----------- .xsession-errors (736309 sec old) --------------------- ** Message: NameOwnerChanged old-owner '' new-owner ':1.41' ** Message: Viewer now connected to the bus ** Message: ViewerSetup ** Message: Calling SetWindow Viewer: SetWindow XID 62711252 size 876:801 ** Message: Viewer state: STOPPED ** Message: SetWindow reply ** Message: ViewerReady ** Message: IsSchemeSupported scheme 'http': yes ** Message: totem_embedded_open_internal 'fd://0' is-browser-stream 1 ** Message: BEFORE _open ** Message: AFTER _open (ret: 1) ** Message: Viewer state: PLAYING ...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 the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 357405 ***