GNOME Bugzilla – Bug 542114
crash in Open Folder: I was connecting to a wi...
Last modified: 2008-07-08 22:16:15 UTC
Version: 2.20.0 What were you doing when the application crashed? I was connecting to a windows share on my campus network. After opening a new connection, program crashed. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-custom #1 SMP Sun Jul 6 14:54:58 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: black-white_2-Gloss Memory status: size: 87265280 vsize: 87265280 resident: 26812416 share: 15400960 rss: 26812416 rss_rlim: 4294967295 CPU usage: start_time: 1215553441 rtime: 277 utime: 260 stime: 17 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 0xb6bd5720 (LWP 3468)] (no debugging symbols found) 0xb7372f91 in waitpid () from /lib/libpthread.so.0
+ Trace 202356
Thread 1 (Thread 0xb6bd5720 (LWP 3468))
----------- .xsession-errors (40 sec old) --------------------- connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! CalDAV Eplugin starting up ... ** (evolution:3584): DEBUG: mailto URL command: evolution %s ** (evolution:3584): DEBUG: mailto URL program: evolution connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-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 ***