GNOME Bugzilla – Bug 784771
Nautilus Crashes When Cutting File From Outside
Last modified: 2021-05-26 08:17:57 UTC
I'm running XFCE which has a default file manager of Thunar, but I have Nautilus installed and set as my default file manager. However, Thunar still does manage my desktop because I don't think it's possible to remove it completely. So, when I cut a file from my Thunar desktop while an instance of Nautilus is running, that instance will immediately crash. If I have a file copied from my Thunar desktop and open Nautilus, it'll start but crash a second later. These crashes occur regardless of if I run Nautilus with --no-desktop or not. Nautilus Log: ** ERROR:../nautilus/src/nautilus-file.c:582:nautilus_file_new_from_filename: assertion failed: (filename[0] != '\0') Aborted (core dumped) OS: x86_64 Linux 4.11.9-1-ARCH Desktop Environment: XFCE
I should also note that this only happens with cutting, not copying.
Thanks for taking the time to report this. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!
I'm not too sure I did this right (I rebuilt nautilus and gvfs, entering debug and !strip into the PKGBUILDs and then ran gdb with /usr/bin/nautilus.), but here's the stack trace log: Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffe7193700 (LWP 4349)] [New Thread 0x7fffe6992700 (LWP 4350)] [New Thread 0x7fffe4f36700 (LWP 4352)] [New Thread 0x7fffd7fff700 (LWP 4353)] [New Thread 0x7fffd6515700 (LWP 4354)] [New Thread 0x7fffd5d14700 (LWP 4356)] [Thread 0x7fffd5d14700 (LWP 4356) exited] [Thread 0x7fffe4f36700 (LWP 4352) exited] Thread 1 "nautilus" received signal SIGABRT, Aborted. 0x00007ffff3c7c670 in raise () from /usr/lib/libc.so.6 In between the "[Thread 0x7fffe4f36700 (LWP 4352) exited]" and "Thread 1 "nautilus" received signal SIGABRT, Aborted." lines in gdb is where the failed assertion is, but not in the log.
>When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance! The only options I see are NEEDINFO, and RESOLVED, and this bug still isn't resolved, so I'm not sure what to do. Here's a screenshot of what my form looks like: https://i.imgur.com/V8fnp0x.png. (Sorry for sending multiple emails, I thought that after that comment I'd be able to change the status to something else.)
(In reply to thekoopakingdom from comment #3) > Thread 1 "nautilus" received signal SIGABRT, Aborted. > 0x00007ffff3c7c670 in raise () from /usr/lib/libc.so.6 Could you enter "thread apply all bt full" after this, please?
Sure. Here's everything that comes after the "0x00007ffff3c7c670 in raise () from /usr/lib/libc.so.6" line:
+ Trace 237636
Thread 10 (Thread 0x7fffcf7fe700 (LWP 8757))
Thanks. Could you install debug packages for glib2 to have a better stacktrace?
Once this bug is resolved, I can: https://bugzilla.gnome.org/show_bug.cgi?id=782057.
(In reply to thekoopakingdom from comment #8) > Once this bug is resolved, I can: > https://bugzilla.gnome.org/show_bug.cgi?id=782057. Could you please reply to https://bugzilla.gnome.org/show_bug.cgi?id=782057#c5 ?
Alright, I got GLib to build. Here's the stack trace with both of the debug packages: Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffe7e9e700 (LWP 27789)] [New Thread 0x7fffe769d700 (LWP 27790)] [New Thread 0x7fffe5c3c700 (LWP 27792)] [New Thread 0x7fffe522e700 (LWP 27793)] [New Thread 0x7fffd647b700 (LWP 27794)] [New Thread 0x7fffd585a700 (LWP 27796)] [New Thread 0x7fffd5059700 (LWP 27797)] [New Thread 0x7fffcffff700 (LWP 27798)] [Thread 0x7fffcffff700 (LWP 27798) exited] [Thread 0x7fffd647b700 (LWP 27794) exited] [Thread 0x7fffe5c3c700 (LWP 27792) exited] [Thread 0x7fffd5059700 (LWP 27797) exited] Thread 1 "nautilus" received signal SIGABRT, Aborted. 0x00007ffff3e1f8a0 in raise () from /usr/lib/libc.so.6
+ Trace 237991
Thread 1 (Thread 0x7ffff7f92000 (LWP 27785))
The last stacktrace is still missing glib2 and gtk3 debug symbols.
Closing this bug report as no further information has been provided. Please feel free to report this to https://gitlab.gnome.org/GNOME/nautilus/-/issues/ if you can provide the information that was asked for in a previous comment and if this still happens in a recent and supported version. Thanks!