GNOME Bugzilla – Bug 478405
crash in Image Viewer: visualizzando delle imma...
Last modified: 2007-09-20 17:17:59 UTC
Version: 2.18.0.1 What were you doing when the application crashed? visualizzando delle immagini a schermo pieno 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.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 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: 136310784 vsize: 136310784 resident: 86450176 share: 10178560 rss: 86450176 rss_rlim: 4294967295 CPU usage: start_time: 1190232504 rtime: 989 utime: 915 stime: 74 cutime:1 cstime: 3 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 -1209084192 (LWP 4310)] [New Thread -1253962864 (LWP 4312)] [New Thread -1211405424 (LWP 4311)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 164020
Thread 2 (Thread -1253962864 (LWP 4312))
----------- .xsession-errors (806 sec old) --------------------- localuser:ezio being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3814 Loading "installonlyn" plugin ConsoleKit console-kit-daemon (pid 1956) in esecuzione... ConsoleKit console-kit-daemon (pid 1956) in esecuzione... ConsoleKit console-kit-daemon (pid 1956) in esecuzione... sshd sshd (pid 4104) in esecuzione... sshd sshd (pid 4104) in esecuzione... --------------------------------------------------
I was visualizing a folder of images with gThumb direcly from the pen-drive in modality full screen. If I tray to Hard Disk I don't have this problem.
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 current software version (2.20). You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 357405 ***