GNOME Bugzilla – Bug 522089
crash in Computer: Using Deluge torrent cli...
Last modified: 2008-03-13 00:21:50 UTC
Version: 2.18.3 What were you doing when the application crashed? Using Deluge torrent client, Pidgin Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 101634048 vsize: 101634048 resident: 26480640 share: 19902464 rss: 26480640 rss_rlim: 4294967295 CPU usage: start_time: 1205350668 rtime: 30 utime: 28 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (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 -1208973600 (LWP 3374)] [New Thread -1255154800 (LWP 3381)] [New Thread -1244664944 (LWP 3380)] [New Thread -1234175088 (LWP 3379)] [New Thread -1222050928 (LWP 3378)] [New Thread -1211561072 (LWP 3375)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 192246
Thread 1 (Thread -1208973600 (LWP 3374))
----------- .xsession-errors (132 sec old) --------------------- localuser:szegedi being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2889 --- Hash table keys for warning below: --> file:///home/szegedi (nautilus:3169): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) The application 'bug-buddy' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. --------------------------------------------------
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 439977 ***