GNOME Bugzilla – Bug 605200
crash in CD/DVD Creator: I closed the regular Nau...
Last modified: 2010-01-14 02:24:19 UTC
Version: 2.28.2 What were you doing when the application crashed? I closed the regular Nautilus window by pressing the X in the window border... Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-11-21 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30 #1 SMP Mon Jun 29 10:26:36 CEST 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 507244544 vsize: 507244544 resident: 55787520 share: 20533248 rss: 55787520 rss_rlim: 18446744073709551615 CPU usage: start_time: 1261464398 rtime: 1395 utime: 1316 stime: 79 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0x7fff13fff910 (LWP 9872)] 0x00007fff2e84a51d in waitpid () from /lib/libpthread.so.0
+ Trace 219733
Thread 1 (Thread 0x7fff300e8800 (LWP 4512))
Inferior 1 [process 4512] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (13 sec old) --------------------- *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. --------------------------------------------------
I have a Doutb... Is Nautilus o Brasero the problem, because in your description you talk about Nautilus If a product is Nautilus this is Dup of bug 582457.
I miss a word this "could be" dup of bug 582457
Yes it's a dup of that *** This bug has been marked as a duplicate of bug 582457 ***