GNOME Bugzilla – Bug 532953
crash in File Browser: 윈도우즈 VISTA 와 파일 공
Last modified: 2008-05-13 16:07:25 UTC
Version: 2.20.0 What were you doing when the application crashed? 윈도우즈 VISTA 와 파일 공 Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 82423808 vsize: 82423808 resident: 24915968 share: 15937536 rss: 24915968 rss_rlim: 4294967295 CPU usage: start_time: 1210770358 rtime: 273 utime: 256 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c1e720 (LWP 4713)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197624
Thread 1 (Thread 0xb6c1e720 (LWP 4713))
----------- .xsession-errors (45 sec old) --------------------- connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! (synaptic:4122): Gtk-CRITICAL **: gtk_text_buffer_set_text: assertion `text != NULL' failed (synaptic:4122): Gtk-CRITICAL **: gtk_text_buffer_set_text: assertion `text != NULL' failed warning: .dynamic section for "/usr/lib/libgdk_pixbuf-2.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libglib-2.0.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations Initializing gnome-mount extension --------------------------------------------------
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 ***