Red Hat Bugzilla – Bug 1026561
Nautilus crashes on folder removal in browser mode
Last modified: 2016-05-10 21:11:37 EDT
Created attachment 819428 [details]
Fix based on current nautilus code, see description
Description of problem:
Nautilus can crash in browser mode if a folder that was previously visited and is thus still visible in the location bar gets deleted.
This is caused by a corrupt button entry in the location bar that points to invalid/unmapped memory after a directory present in the location bar got removed. As soon as nautilus traverses the list for whatever reason(there are multiple examples of that in the code), it crashes.
After a bit of investigation, I think that's caused by nautilus-2.31.5-cleanup-pathbar.patch, which tries to fix bug #690147(location bar not updated on folder removal) but fails at doing it properly. I've attached a fixed patch that is based on the current nautilus code, nautilus-cleanup-pathbar2.patch. It obseletes nautilus-2.31.5-cleanup-pathbar.patch.
 https://git.gnome.org/browse/nautilus/tree/src/nautilus-pathbar.c?id=481cf689488668012ca9d7a9c6b15b1dcd0cb465, line 1539+.
Version-Release number of selected component (if applicable):
2.28.4 / 2.28.4-19-el6 (i686)
Steps to Reproduce:
1. Enable browser mode and make sure the button location bar is active
2. mkdir ~/a/b/c
3. Open ~/a/b/c in nautilus
4. Change back to your home directory by clicking it in the location bar or using Alt+Up
5. Move a to trash by right click->Move to trash
Nautilus crashes most of the time. Sometimes it doesn't, but instead shows a corrupted location bar:
[Username] -> [Empty] -> b -> c
and gets highly unstable after that.
a, b and c removed from location bar, no crash of course.
I'm unable to test this issue on an actual RHEL installation. I'm not a Red Hat customer, and apparently I don't qualify for evaluation due to my e-mail address. So this was tested on a popular RHEL6 rebuild.
However, I highly suspect that this issue also affects RHEL, as the Red Hat specific patch that adds this is also be present there.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.