GNOME Bugzilla – Bug 461765
crash in Open Folder: I was copying files over...
Last modified: 2018-08-17 13:49:08 UTC
Version: 2.18.3 What were you doing when the application crashed? I was copying files over a smb share to my pc and had not the right permissions. A popup asked me what to do. When I selected "Skip" Nautilius crashed. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 109408256 vsize: 109408256 resident: 57651200 share: 20328448 rss: 57651200 rss_rlim: 4294967295 CPU usage: start_time: 1185794840 rtime: 12333 utime: 10910 stime: 1423 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 -1208531232 (LWP 7558)] [New Thread -1286911088 (LWP 7638)] (no debugging symbols found) 0x00b7f402 in __kernel_vsyscall ()
+ Trace 151570
Thread 2 (Thread -1286911088 (LWP 7638))
----------- .xsession-errors --------------------- CALLBACK: save-authentication!!! Loading "installonlyn" plugin Loading "installonlyn" plugin No packages were given for installation. Loading "installonlyn" plugin Loading "installonlyn" plugin No packages were given for installation. No packages were given for installation. seahorse nautilus module initialized --- Hash table keys for warning below: --> file:///home/noot (nautilus:7568): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Xlib: unexpected async reply (sequence 0x2cc195)! --------------------------------------------------
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. Could you please install some debugging packages [1], start the application as normal, and 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] debugging packages for nautilus, pango, gtk, glib, gnome-vfs, libgnome and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
Done. Some additional information I discovered as well. I copy a directory over a smb share to my pc and in that directory is a file owned by me but with no permission, so ----------, not even read. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 97681408 vsize: 97681408 resident: 31547392 share: 17231872 rss: 31547392 rss_rlim: 4294967295 CPU usage: start_time: 1186453866 rtime: 684 utime: 617 stime: 67 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208224032 (LWP 3486)] [New Thread -1221227632 (LWP 3625)] 0x00c0b402 in __kernel_vsyscall ()
+ Trace 153363
Thread 2 (Thread -1221227632 (LWP 3625))
----------- .xsession-errors --------------------- ** 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 (nautilus:3486): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed Cannot access memory at address 0xf Cannot access memory at address 0xf --------------------------------------------------
Great stack trace Arnaud, thanks! Changing to gnome-vfs and confirming.
*** Bug 465587 has been marked as a duplicate of this bug. ***
*** Bug 470129 has been marked as a duplicate of this bug. ***
*** Bug 475458 has been marked as a duplicate of this bug. ***
*** Bug 442647 has been marked as a duplicate of this bug. ***
*** Bug 434337 has been marked as a duplicate of this bug. ***
*** Bug 446868 has been marked as a duplicate of this bug. ***
*** Bug 460848 has been marked as a duplicate of this bug. ***
*** Bug 477195 has been marked as a duplicate of this bug. ***
*** Bug 477135 has been marked as a duplicate of this bug. ***
*** Bug 489521 has been marked as a duplicate of this bug. ***
*** Bug 485951 has been marked as a duplicate of this bug. ***
*** Bug 490913 has been marked as a duplicate of this bug. ***
*** Bug 490933 has been marked as a duplicate of this bug. ***
*** Bug 491953 has been marked as a duplicate of this bug. ***
*** Bug 493600 has been marked as a duplicate of this bug. ***
*** Bug 500319 has been marked as a duplicate of this bug. ***
*** Bug 502583 has been marked as a duplicate of this bug. ***
Bug #502583 also contains a good stack trace.
*** Bug 503033 has been marked as a duplicate of this bug. ***
*** Bug 504675 has been marked as a duplicate of this bug. ***
*** Bug 510948 has been marked as a duplicate of this bug. ***
*** Bug 518392 has been marked as a duplicate of this bug. ***
gnome-vfs got deprecated in 2008. gnome-vfs is not under active development anymore and had its last code changes in 2011. Its codebase has been archived: https://gitlab.gnome.org/Archive/gnome-vfs/commits/master gio (in glib) and gvfs are its successors. See https://developer.gnome.org/gio/stable/ch33.html and https://people.gnome.org/~gicmo/gio-migration-guide/ for porting info. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of glib/gio/gvfs. Thanks!