GNOME Bugzilla – Bug 541061
crash in Open Folder: Opening a remote folder
Last modified: 2008-07-01 18:02:37 UTC
Version: 2.20.0 What were you doing when the application crashed? Opening a remote folder Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 73629696 vsize: 73629696 resident: 21430272 share: 14983168 rss: 21430272 rss_rlim: 4294967295 CPU usage: start_time: 1214909754 rtime: 299 utime: 278 stime: 21 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b3b940 (LWP 3053)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201822
Thread 1 (Thread 0xb6b3b940 (LWP 3053))
----------- .xsession-errors (39 sec old) --------------------- #7 /usr/lib/jvm/java-1.5.0-sun-1.5.0.14/jre/lib/i386/xawt/libmawt.so(Java_sun_awt_X11GraphicsEnvironment_initDisplay+0x26) [0xb1a50106] #8 [0xb22b8bfa] #9 [0xb22b2b3b] #10 [0xb22b2b3b] #11 [0xb22b0219] #12 /usr/lib/jvm/java-1.5.0-sun-1.5.0.14/jre/lib/i386/client/libjvm.so [0xb776a2bc] #13 /usr/lib/jvm/java-1.5.0-sun-1.5.0.14/jre/lib/i386/client/libjvm.so [0xb787ef98] #14 /usr/lib/jvm/java-1.5.0-sun-1.5.0.14/jre/lib/i386/client/libjvm.so [0xb776a0ef] #15 /usr/lib/jvm/java-1.5.0-sun-1.5.0.14/jre/lib/i386/client/libjvm.so(JVM_DoPrivileged+0x32d) [0xb77c7b9d] #16 /usr/lib/jvm/java-1.5.0-sun-1.5.0.14/jre/lib/i386/libjava.so(Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2+0x3d) [0xb756230d] #17 [0xb22b84ab] #18 [0xb22b2a64] #19 [0xb22b0219] connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
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 522534 ***