GNOME Bugzilla – Bug 537975
crash in Home Folder: open a sharing folder in...
Last modified: 2008-06-12 16:39:50 UTC
What were you doing when the application crashed? open a sharing folder in windows srv 2003 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 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: MacOS-X Icon Theme: eXperience Memory status: size: 77021184 vsize: 77021184 resident: 25067520 share: 15949824 rss: 25067520 rss_rlim: 4294967295 CPU usage: start_time: 1213271232 rtime: 933 utime: 881 stime: 52 cutime:4 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6a95940 (LWP 3849)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200236
Thread 1 (Thread 0xb6a95940 (LWP 3849))
----------- .xsession-errors (20 sec old) --------------------- for menu path "<Toolbox>/Xtns/Languages/_Script-Fu" (number of '/' must be the same) bad translation "<Toolbox>/Xtns/Languages/_Script-Fu/" for menu path "<Toolbox>/Xtns/Languages/_Script-Fu" (number of '/' must be the same) ** (gimp-2.4:4485): WARNING **: Invalid borders specified for theme pixmap: /home/felipe/.themes/MacOS-X/gtk-2.0/entry2.png, borders don't fit within the image Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e00003 (Exportar A) Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. 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 ***