GNOME Bugzilla – Bug 540278
crash in File Browser: browising samba share
Last modified: 2008-06-26 09:27:23 UTC
Version: 2.20.0 What were you doing when the application crashed? browising samba share Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Thu Jun 12 16:26:30 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gTango Memory status: size: 98406400 vsize: 98406400 resident: 34607104 share: 21725184 rss: 34607104 rss_rlim: 4294967295 CPU usage: start_time: 1214469580 rtime: 1120 utime: 1052 stime: 68 cutime:0 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 0xb6b9d720 (LWP 3978)] (no debugging symbols found) 0xb7fe1424 in __kernel_vsyscall ()
+ Trace 201425
Thread 1 (Thread 0xb6b9d720 (LWP 3978))
----------- .xsession-errors (18 sec old) --------------------- fixme:shell:DAD_ShowDragImage 0x00000000 stub fixme:shell:DAD_ShowDragImage 0x00000001 stub fixme:shell:UnixFolder_IShellFolder2_GetUIObjectOf Unknown interface {00021500-0000-0000-c000-000000000046} in GetUIObjectOf fixme:shell:UnixFolder_IShellFolder2_GetUIObjectOf Unknown interface {00021500-0000-0000-c000-000000000046} in GetUIObjectOf fixme:shell:DAD_ShowDragImage 0x00000000 stub fixme:shell:DAD_ShowDragImage 0x00000000 stub fixme:shell:DAD_ShowDragImage 0x00000001 stub fixme:shell:DAD_ShowDragImage 0x00000001 stub err:pidl:_ILSimpleGetTextW -- no text fixme:shell:DllGetClassObject failed for CLSID= {53bd6b4e-3780-4693-afc3-7161c2f3ee9c} (MruLongList) ** (nautilus:3978): WARNING **: Hit unhandled case 2 (Errore generico) in fm_report_error_loading_directory QClipboard::setData: Cannot set X11 selection owner for PRIMARY QClipboard::setData: Cannot set X11 selection owner for PRIMARY --------------------------------------------------
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 ***