After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 588548 - crash in Open Folder: dragging a folder from a...
crash in Open Folder: dragging a folder from a...
Status: RESOLVED DUPLICATE of bug 589258
Product: nautilus
Classification: Core
Component: general
2.26.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-07-14 15:05 UTC by Hussam Al-Tayeb
Modified: 2009-10-10 14:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Hussam Al-Tayeb 2009-07-14 15:05:21 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 ()

Thread 1 (Thread 0xb6e8aa60 (LWP 22820))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #4 run_bug_buddy
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 bugbuddy_segv_handle
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 IA__g_logv
    at gmessages.c line 512
  • #8 IA__g_log
    at gmessages.c line 526
  • #9 gdk_x_error
    at gdkmain-x11.c line 466
  • #10 _XError
    from /usr/lib/libX11.so.6
  • #11 process_responses
    from /usr/lib/libX11.so.6
  • #12 _XEventsQueued
    from /usr/lib/libX11.so.6
  • #13 XPending
    from /usr/lib/libX11.so.6
  • #14 gdk_check_xpending
    at gdkevents-x11.c line 154
  • #15 gdk_event_check
    at gdkevents-x11.c line 2354
  • #16 IA__g_main_context_check
    at gmain.c line 2469
  • #17 g_main_context_iterate
    at gmain.c line 2588
  • #18 IA__g_main_loop_run
    at gmain.c line 2799
  • #19 IA__gtk_main
    at gtkmain.c line 1205
  • #20 main
    at nautilus-main.c line 518
  • #0 __kernel_vsyscall

---- 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...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2009-10-10 14:00:31 UTC
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 ***