Bug 1017055

Summary: [abrt] nautilus-3.10.0-1.fc20: nautilus_location_entry_set_special_text: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ccecchi, mclasen, sgraf, turquino
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c06dc1f5b93d1eb1675506f2f8a406321209e167
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:35:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Kamil Páral 2013-10-09 08:23:54 UTC 
Description of problem:
I closed Nautilus during copying in progress (from a NFS mounted using autofs). Nautilus crashed and some files were not copied. I can easily reproduce.

Version-Release number of selected component:
nautilus-3.10.0-1.fc20

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        nautilus --new-window
crash_function: nautilus_location_entry_set_special_text
executable:     /usr/bin/nautilus
kernel:         3.11.2-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 nautilus_location_entry_set_special_text at nautilus-location-entry.c:767
 #1 nautilus_location_entry_set_location at nautilus-location-entry.c:201
 #2 nautilus_window_sync_location_widgets at nautilus-window.c:1020
 #3 real_active at nautilus-window-slot.c:475
 #7 g_signal_emit_by_name at gsignal.c:3426
 #8 nautilus_window_set_active_slot at nautilus-window.c:1776
 #9 notebook_switch_page_cb at nautilus-window.c:272
 #14 gtk_notebook_switch_page at gtknotebook.c:6597
 #15 gtk_notebook_real_remove at gtknotebook.c:4939
 #16 gtk_notebook_remove at gtknotebook.c:4109
Comment 1 Kamil Páral 2013-10-09 08:23:58 UTC 
Created attachment 809746 [details]
File: backtrace
Comment 2 Kamil Páral 2013-10-09 08:24:01 UTC 
Created attachment 809747 [details]
File: cgroup
Comment 3 Kamil Páral 2013-10-09 08:24:05 UTC 
Created attachment 809748 [details]
File: core_backtrace
Comment 4 Kamil Páral 2013-10-09 08:24:10 UTC 
Created attachment 809749 [details]
File: dso_list
Comment 5 Kamil Páral 2013-10-09 08:24:14 UTC 
Created attachment 809750 [details]
File: environ
Comment 6 Kamil Páral 2013-10-09 08:24:17 UTC 
Created attachment 809751 [details]
File: exploitable
Comment 7 Kamil Páral 2013-10-09 08:24:21 UTC 
Created attachment 809752 [details]
File: limits
Comment 8 Kamil Páral 2013-10-09 08:24:25 UTC 
Created attachment 809754 [details]
File: maps
Comment 9 Kamil Páral 2013-10-09 08:24:28 UTC 
Created attachment 809755 [details]
File: open_fds
Comment 10 Kamil Páral 2013-10-09 08:24:31 UTC 
Created attachment 809756 [details]
File: proc_pid_status
Comment 11 Kamil Páral 2013-10-09 08:24:34 UTC 
Created attachment 809757 [details]
File: var_log_messages
Comment 12 Stanislav Graf 2014-01-12 21:54:14 UTC 
Another user experienced a similar problem:

Unmount android device

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        nautilus --new-window
crash_function: nautilus_location_entry_set_special_text
executable:     /usr/bin/nautilus
kernel:         3.12.6-300.fc20.x86_64
package:        nautilus-3.10.1-2.fc20
reason:         nautilus killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Fedora End Of Life 2015-05-29 09:32:34 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Fedora End Of Life 2015-06-29 12:35:52 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.