GNOME Bugzilla – Bug 446868
crash in File Browser: Nautilus scp between FC6...
Last modified: 2007-10-23 13:46:30 UTC
Version: 2.18.1 What were you doing when the application crashed? Nautilus scp between FC6 and F7 Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 546082816 vsize: 546082816 resident: 96772096 share: 29958144 rss: 96772096 rss_rlim: 18446744073709551615 CPU usage: start_time: 1181670789 rtime: 5655 utime: 3182 stime: 2473 cutime:21 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496373456 (LWP 5044)] [New Thread 1115699536 (LWP 8996)] (no debugging symbols found) 0x00000032ce6c7956 in poll () from /lib64/libc.so.6
+ Trace 140449
Thread 2 (Thread 1115699536 (LWP 8996))
----------- .xsession-errors (6 sec old) --------------------- --- Hash table keys for warning below: --> file:///home/lbrenta (nautilus:8907): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 1 element at quit time (keys above) --- Hash table keys for warning below: --> file:///home/lbrenta (nautilus:8907): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) reloadBuffers(): 52 nodes checked in 2.92E-4 second(s) reloadBuffers(): 52 nodes checked in 3.93E-4 second(s) ** Message: Hit unexpected error "Operación no permitida" while doing a file operation. ** Message: Hit unexpected error "Operación no permitida" while doing a file operation. Xlib: unexpected async reply (sequence 0x224def)! Xlib: sequence lost (0x2300ed > 0x224fb8) in reply type 0xe3! --------------------------------------------------
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!
*** Bug 447775 has been marked as a duplicate of this bug. ***
*** Bug 448140 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, the 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. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 454836 has been marked as a duplicate of this bug. ***
*** Bug 456657 has been marked as a duplicate of this bug. ***
*** Bug 456709 has been marked as a duplicate of this bug. ***
*** Bug 462726 has been marked as a duplicate of this bug. ***
*** Bug 462091 has been marked as a duplicate of this bug. ***
*** Bug 463675 has been marked as a duplicate of this bug. ***
*** Bug 464008 has been marked as a duplicate of this bug. ***
same issue as bug 461765 *** This bug has been marked as a duplicate of 461765 ***
*** Bug 489248 has been marked as a duplicate of this bug. ***
*** Bug 489214 has been marked as a duplicate of this bug. ***