Version-Release number of selected component: nautilus-3.10.1-2.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 _g_log_abort at gmessages.c:255 #5 rename_newly_added_folder at nautilus-view.c:1824 #6 ffi_call_unix64 at ../src/x86/unix64.S:76 #7 ffi_call at ../src/x86/ffi64.c:522 #8 g_cclosure_marshal_generic at gclosure.c:1454 #13 process_old_files at nautilus-view.c:3517 #14 display_pending_files at nautilus-view.c:3559 #15 display_pending_callback at nautilus-view.c:3659 #20 g_main_context_iteration at gmain.c:3774 #21 g_application_run at gapplication.c:1635
Created attachment 846578 [details] File: backtrace
Created attachment 846579 [details] File: cgroup
Created attachment 846580 [details] File: core_backtrace
Created attachment 846581 [details] File: dso_list
Created attachment 846582 [details] File: environ
Created attachment 846583 [details] File: limits
Created attachment 846584 [details] File: maps
Created attachment 846585 [details] File: open_fds
Created attachment 846586 [details] File: proc_pid_status
Created attachment 846587 [details] File: var_log_messages
I am able to reproduce / trigger this by using the "New folder with Selection" option from the context menu on MTP filesystems. (Tested with Nexus 4 and Nexus 7 mounted via MTP, both running Android 4.4.2)
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.