GNOME Bugzilla – Bug 460848
crash in Open Folder: Error appeared when tryi...
Last modified: 2007-09-11 13:52:12 UTC
Version: 2.18.3 What were you doing when the application crashed? Error appeared when trying to copy from mounted sshfs to local disk Distribution: Unknown Gnome Release: 2.18.3 2007-07-07 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.22-ARCH #1 SMP PREEMPT Mon Jul 23 21:13:22 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaAquaIsh Icon Theme: nuoveXT.2.2 Memory status: size: 85368832 vsize: 85368832 resident: 30834688 share: 16830464 rss: 30834688 rss_rlim: 4294967295 CPU usage: start_time: 1185524584 rtime: 469 utime: 429 stime: 40 cutime:0 cstime: 0 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227376960 (LWP 5185)] [New Thread -1300079728 (LWP 8683)] (no debugging symbols found) 0xb7f19410 in __kernel_vsyscall ()
+ Trace 150879
Thread 2 (Thread -1300079728 (LWP 8683))
----------- .xsession-errors --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 Xlib: unexpected async reply (sequence 0xcad8)! (nautilus:5185): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
same issue as bug 461765 *** This bug has been marked as a duplicate of 461765 ***