GNOME Bugzilla – Bug 588548
crash in Open Folder: dragging a folder from a...
Last modified: 2009-10-10 14:00:31 UTC
Version: 2.26.3 What were you doing when the application crashed? dragging a folder from an tarball using File Roller 2.26.3 onto my desktop using nautilus 2.26.3 Distribution: Unknown Gnome Release: 2.26.3 2009-07-03 (Archlinux) BugBuddy Version: 2.26.0 System: Linux 2.6.30-ARCH #1 SMP PREEMPT Sat Jul 4 11:13:08 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10602000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 81125376 vsize: 81125376 resident: 24227840 share: 15708160 rss: 24227840 rss_rlim: 18446744073709551615 CPU usage: start_time: 1247583804 rtime: 392 utime: 337 stime: 55 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 0xb6e8aa60 (LWP 22820)] [New Thread 0xb6a25b70 (LWP 22833)] 0xb7ff7424 in __kernel_vsyscall ()
+ Trace 216434
Thread 1 (Thread 0xb6e8aa60 (LWP 22820))
---- Critical and fatal warnings logged during execution ---- ** Gdk **: The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAtom (invalid Atom parameter)'. (Details: serial 12045 error_code 5 request_code 24 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ----------- .xsession-errors (723 sec old) --------------------- (firefox:21822): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb65cecc0(0xad497bb0) (firefox:21822): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb65cecc0(0xad4a2170) (firefox:21822): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb65cecc0(0xad4a2800) (firefox:21822): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb65cecc0(0xad497d70) (firefox:21822): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb65cecc0(0xad4a3b40) (firefox:21822): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb65cecc0(0xad4a3de0) (firefox:21822): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb65cecc0(0xad497c90) ...Too much output, ignoring rest... --------------------------------------------------
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 bug 589258 ***