Description of problem: I was trying to open a folder that contained a file I was searching for. Version-Release number of selected component: nautilus-3.10.1-4.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: nautilus --new-window /run/user/1000/gvfs/smb-share:server=peeves.local,share=www crash_function: g_type_check_instance executable: /usr/bin/nautilus kernel: 3.15.10-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance at gtype.c:4082 #1 g_signal_connect_data at gsignal.c:2435 #2 set_pending_icon_to_reveal at nautilus-canvas-container.c:592 #3 end_renaming_mode at nautilus-canvas-container.c:7454 #4 icon_set_position at nautilus-canvas-container.c:304 #6 lay_down_one_line at nautilus-canvas-container.c:1189 #7 lay_down_icons_horizontal at nautilus-canvas-container.c:1261 #8 lay_down_icons at nautilus-canvas-container.c:1853 #9 redo_layout_internal at nautilus-canvas-container.c:1873 #10 _g_closure_invoke_va at gclosure.c:840 Potential duplicate: bug 711663
Created attachment 930284 [details] File: backtrace
Created attachment 930285 [details] File: cgroup
Created attachment 930286 [details] File: core_backtrace
Created attachment 930287 [details] File: dso_list
Created attachment 930288 [details] File: environ
Created attachment 930289 [details] File: exploitable
Created attachment 930290 [details] File: limits
Created attachment 930291 [details] File: maps
Created attachment 930292 [details] File: open_fds
Created attachment 930293 [details] File: proc_pid_status
Created attachment 930294 [details] File: var_log_messages
Another user experienced a similar problem: I was traging to drag and drop a file to Google Drive. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: nautilus --new-window /run/user/1000/gvfs/smb-share:server=peeves.local,share=www crash_function: g_type_check_instance executable: /usr/bin/nautilus kernel: 3.17.2-200.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I was trying to rename a file. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: nautilus --new-window /home/omega13a/.local/share/celestia/extras/mine crash_function: g_type_check_instance executable: /usr/bin/nautilus kernel: 3.19.5-100.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I was trying to paste some files I copied from over my local network. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: nautilus --new-window /home/omega13a/.local/share/celestia/extras/mine crash_function: g_type_check_instance executable: /usr/bin/nautilus kernel: 3.19.5-100.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.
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.