GNOME Bugzilla – Bug 728448
Nautilus will SIGABRT when thumbnails are not allowed to fully generate
Last modified: 2016-08-05 07:17:42 UTC
Nautilus will in some cases get a SIGABRT signal and quit having output following message to standard output or error. ERROR:nautilus-view.c:1810:rename_newly_added_folder: code should not be reached fish: Job 1, “nautilus” terminated by signal SIGABRT (Abort) Reproduction steps are pretty simple: 1. $ mkdir /tmp/make-it-abort; 2. put some – the more the better – thumbnailable data into that directory, preferably without opening nautilus; 3. In quick succession do following: Enter the /tmp/make-it-abort with nautilus → ^A (select all items) → Menu key (open a context menu for selected items) → Enter (New Folder with Selection (x items)). If the thumbnails for images are not yet finished generating by the time one completes the sequence of actions, nautilus should SIGABRT. However, if the thumbnails’ generation is (almost?) finished by the time one clicks Enter, things will work out and nautilus won’t crash. Also reproducible in 3.10 exactly the same way.
Confirmed, that's a frequently reported issue on Ubuntu https://bugs.launchpad.net/nautilus/+bug/1443718 It has also been reported on fedora, https://bugzilla.redhat.com/show_bug.cgi?id=1225493 That seems more difficult to hit with 3.18 though, but the items get unselected when the thumbnails are generated and the new "enter folder name" dialog delays the action, you can see missing files errors on the command line though
(In reply to Sebastien Bacher from comment #1) > Confirmed, that's a frequently reported issue on Ubuntu > https://bugs.launchpad.net/nautilus/+bug/1443718 > > It has also been reported on fedora, > https://bugzilla.redhat.com/show_bug.cgi?id=1225493 > > That seems more difficult to hit with 3.18 though, but the items get > unselected when the thumbnails are generated and the new "enter folder name" > dialog delays the action, you can see missing files errors on the command > line though Sebastian, is it possible for you to test with 3.20.1? Specifically this commit https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-20&id=3fb0240ca0946103d2b585d37da22cb19332a000 This could be backported if necessary.
Let's mark it as fixed as per comment 2
@Carlos the fix seems to work indeed, backporting would be nice though I guess it wouldn't apply as it in < 3.16 versions? We updated current Ubuntu to 3.20 so that's good but I would still like to see that fixed in oldest series if we can
(In reply to Sebastien Bacher from comment #4) > @Carlos the fix seems to work indeed, backporting would be nice though I > guess it wouldn't apply as it in < 3.16 versions? We updated current Ubuntu > to 3.20 so that's good but I would still like to see that fixed in oldest > series if we can Cool. It's not a straightforward backport, so I wouldn't do it for older versions. Feel free to do it though and attach here if you find the time or you think it worth it.