Red Hat Bugzilla – Bug 1013272
[abrt] nautilus-3.10.0-1.fc20: nautilus_location_entry_update_current_uri: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Last modified: 2014-12-22 12:36:35 EST
Version-Release number of selected component:
cmdline: nautilus --new-window
Thread no. 1 (10 frames)
#0 nautilus_location_entry_update_current_uri at nautilus-location-entry.c:180
#1 nautilus_location_entry_set_location at nautilus-location-entry.c:203
#2 nautilus_window_sync_location_widgets at nautilus-window.c:1020
#3 real_active at nautilus-window-slot.c:475
#4 g_closure_invoke at /lib64/libgobject-2.0.so.0
#5 signal_emit_unlocked_R at /lib64/libgobject-2.0.so.0
#6 g_signal_emit_valist at /lib64/libgobject-2.0.so.0
#7 g_signal_emit_by_name at /lib64/libgobject-2.0.so.0
#8 nautilus_window_set_active_slot at nautilus-window.c:1776
#9 notebook_switch_page_cb at nautilus-window.c:272
Created attachment 804585 [details]
Created attachment 804586 [details]
Created attachment 804587 [details]
Created attachment 804588 [details]
Created attachment 804589 [details]
Created attachment 804590 [details]
Created attachment 804591 [details]
Created attachment 804592 [details]
Created attachment 804593 [details]
Created attachment 804594 [details]
Created attachment 804595 [details]
it usually happens when I close a Nautilus window after I worked with an external USB device such as pen drives, SD cards and so on, however it apparently happens in a random way
finally I was able to reproduce it in a consistent way, because I found out that it happens when you copy something from an external storage device (I tried a SD card but it should work with any device) to your HD (in my case a SSD) using two tabs of the same Nautilus window
to reproduce it do as follows:
1. open a Nautilus window
2. insert a SD card
3. open the SD card in a new tab of the same Nautilus window
4. copy files and/or folders either by copy&paste or by drag&drop to your HD
5. eject the SD card by clicking on the triangle
6. close the Nautilus window by clicking on the x
hope it can help to fix this annoying issue
(In reply to Fiorenzo De Santis from comment #13)
> finally I was able to reproduce it in a consistent way, because I found out
> that it happens when you copy something from an external storage device (I
> tried a SD card but it should work with any device) to your HD (in my case a
> SSD) using two tabs of the same Nautilus window
> to reproduce it do as follows:
> 1. open a Nautilus window
> 2. insert a SD card
> 3. open the SD card in a new tab of the same Nautilus window
> 4. copy files and/or folders either by copy&paste or by drag&drop to your HD
> 5. eject the SD card by clicking on the triangle
> 6. close the Nautilus window by clicking on the x
> hope it can help to fix this annoying issue
I have a faster steps to reproduce (no need for SD card):
1. open 2 nautilus windows.
2. in one window open 2 tabs (each tab must be different folders).
3. close the nautilus window which has 2 tabs.
Created attachment 850712 [details]
Check for valid location entry widget
After some debugging I observed that nautilus is attempting to update the location entry widget when each tab is closed, but the widget has been mangled by the window being destroyed and is no longer valid.
A simple NULL check and widget test keeps nautilus from crashing for me.
This may not be the best way to fix this, but I didn't see another solution after spending a few minutes looking at it.
@Matthias Clasen: There is a patch and steps to reproduce for this bug. What happens now? Do you also need to file a bug upstream?
It would be good to file a bug with this patch upstream, yes. Thanks for the fix, Michael.
Yes. Could you open bug in GNOME Bugziila ?
Bug opened: https://bugzilla.gnome.org/show_bug.cgi?id=722616
(In reply to Igor Gnatenko from comment #19)
> Yes. Could you open bug in GNOME Bugziila ?
Igor, can you merge the second patch Michael posted at https://bugzilla.gnome.org/show_bug.cgi?id=722616
FYI, the patch has now been committed upstream.
I'm backporting this (plus the other crasher fix that got committed alongside it, just for the hell of it).
nautilus-3.10.1-3.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing nautilus-3.10.1-3.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
nautilus-3.10.1-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
The problem persist after update, similar to comment #15
Copied files total size over 5GB with multiple windows.
(In reply to im_asmodeus from comment #27)
> The problem persist after update, similar to comment #15
Hm, it doesn't seem like it should be possible to get this exact same crash after this update. Also, the problem tracker  indicates zero crashes on the updated version 3.10.1-3.
Just to be sure -- since Nautilus is one of those applications that likes to live in the background even though it appears to be closed -- did you log out (or restart) between applying the update and hitting the crash?
If so, a backtrace would be helpful here as it might be slightly different from the original crash, yet similar enough that ABRT considers it a duplicate to this bug.
Created attachment 864133 [details]
Reply to comment #27
I did logged out, using laptop, logout/lock/poweroff is a frequent occurrence.
I've uploaded the backtrace - see comment #29
(In reply to im_asmodeus from comment #30)
> I've uploaded the backtrace - see comment #29
Not core_backtrace (though that does indeed look like this same crash); there is a file in that folder named coredump. Could you please take that file and generate a stack trace follow the instructions at https://fedoraproject.org/wiki/StackTraces#core
(Note that the last command listed there is the one that you need to type first.)
Created attachment 864571 [details]
Created attachment 864572 [details]
Reply to comment #28 & comment #31
Uploaded the requested files.
#0 0x000000000044711d in nautilus_location_entry_update_current_uri (
uri=0x198b750 "mtp://[usb:003,003]/Phone/Download", entry=0x0)
183 nautilus_entry_set_text (NAUTILUS_ENTRY (entry), uri);
"Hm, it doesn't seem like it should be possible to get this exact same crash after this update"