GNOME Bugzilla – Bug 549043
crash in CD/DVD Creator: Open "Network" folder, t...
Last modified: 2008-08-24 18:01:07 UTC
What were you doing when the application crashed? Open "Network" folder, then browse to smb://some_computer/Video - and bug appears here ! Yes. 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: Nuvola Icon Theme: Mac4Lin_Icons_v0.3a Memory status: size: 81403904 vsize: 81403904 resident: 27955200 share: 18620416 rss: 27955200 rss_rlim: 4294967295 CPU usage: start_time: 1219431297 rtime: 9053 utime: 8760 stime: 293 cutime:0 cstime: 1 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 0xb7e8f720 (LWP 5066)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 205547
Thread 1 (Thread 0xb7e8f720 (LWP 5066))
----------- .xsession-errors (6 sec old) --------------------- Предупреждение менеджера окон: Неверный параметр WM_TRANSIENT_FOR окна 0x69 указан для 0x14005d7 (). connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:5066): WARNING **: Hit unhandled case 31 (Действие отменено) in fm_report_error_loading_directory ** (nautilus:5066): WARNING **: Hit unhandled case 2 (Общая ошибка) in fm_report_error_loading_directory --------------------------------------------------
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 ***