Bug 1218035

Summary: [abrt] nautilus: directory_count_stop(): nautilus killed by SIGABRT
Product: [Fedora] Fedora Reporter: 汪明衡 <ifoolb>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: al.dunsmuir, ccecchi, chmelarz, christianklomp, ifoolb, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5b4ecd7afbcb98a530a30a603c11bf62c79b973c
Whiteboard: abrt_hash:a02e88a3bf96ee055b3a8fdb9285843feb22353c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 13:58:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description 汪明衡 2015-05-04 05:12:33 UTC 
Description of problem:
I was moving a file through 'move to' in nautilus.

Version-Release number of selected component:
nautilus-3.16.1-1.fc22

Additional info:
reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: directory_count_stop
executable:     /usr/bin/nautilus
global_pid:     27764
kernel:         4.0.1-300.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1002

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 directory_count_stop at nautilus-directory-async.c:2245
 #5 start_or_stop_io at nautilus-directory-async.c:4217
 #6 nautilus_directory_async_state_changed at nautilus-directory-async.c:4297
 #7 call_files_changed_common at nautilus-directory.c:901
 #8 call_files_changed_free_list at nautilus-directory.c:911
 #9 g_hash_table_foreach at ghash.c:1607
 #10 nautilus_directory_notify_files_moved at nautilus-directory.c:1442
 #11 nautilus_file_changes_consume_changes at nautilus-file-changes-queue.c:319
 #12 link_job_done at nautilus-file-operations.c:5490
 #13 mainloop_proxy_func at gioscheduler.c:200

Potential duplicate: bug 727399
Comment 1 汪明衡 2015-05-04 05:12:37 UTC 
Created attachment 1021521 [details]
File: backtrace
Comment 2 汪明衡 2015-05-04 05:12:39 UTC 
Created attachment 1021522 [details]
File: cgroup
Comment 3 汪明衡 2015-05-04 05:12:41 UTC 
Created attachment 1021523 [details]
File: core_backtrace
Comment 4 汪明衡 2015-05-04 05:12:43 UTC 
Created attachment 1021524 [details]
File: dso_list
Comment 5 汪明衡 2015-05-04 05:12:45 UTC 
Created attachment 1021525 [details]
File: environ
Comment 6 汪明衡 2015-05-04 05:12:47 UTC 
Created attachment 1021526 [details]
File: limits
Comment 7 汪明衡 2015-05-04 05:12:51 UTC 
Created attachment 1021527 [details]
File: maps
Comment 8 汪明衡 2015-05-04 05:12:52 UTC 
Created attachment 1021528 [details]
File: mountinfo
Comment 9 汪明衡 2015-05-04 05:12:54 UTC 
Created attachment 1021529 [details]
File: namespaces
Comment 10 汪明衡 2015-05-04 05:12:56 UTC 
Created attachment 1021530 [details]
File: open_fds
Comment 11 汪明衡 2015-05-04 05:12:58 UTC 
Created attachment 1021531 [details]
File: proc_pid_status
Comment 12 汪明衡 2015-05-04 05:13:00 UTC 
Created attachment 1021532 [details]
File: var_log_messages
Comment 13 汪明衡 2015-05-04 05:17:55 UTC 
I was moving a folder, that's more accurate.
Comment 14 汪明衡 2015-05-05 10:33:58 UTC 
I think this is reproduceable. I was encountered this bug again when I was moving a folder. But the move operation itself is completed successfully.
Comment 15 Christian Klomp 2015-06-06 14:31:00 UTC 
Same thing over here, move-to intermittently crashes Nautilus.
This has been happening since the new move-to/copy-to functionality was introduced (for F21 there was a Bugzilla report but it was hidden from public so I'm not sure what happened with that).

It can be very easy to reproduce:
1: Use Nautilus to create a new directory (filesystem or location do not seem to matter, but I tested it with ~/Downloads on BTRFS) enter the folder and create another one inside it.
2: Go back to the start directory and use the move-to function to move the new folders to another location (I chose ~/Documents).
3: Nautilus has a high probability of crashing as soon as the move-to action is confirmed.

The failproof workaround for this is to use the copy-to function and then afterwards manually remove the original directories.
Comment 16 Zdenek Chmelar 2015-06-11 12:08:22 UTC 
Another user experienced a similar problem:

I wanted to move one sub-directory from one directory to another one

reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: directory_count_stop
executable:     /usr/bin/nautilus
global_pid:     31266
kernel:         4.0.4-303.fc22.x86_64
package:        nautilus-3.16.2-1.fc22
reason:         nautilus killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 17 Fedora End Of Life 2016-07-19 13:58:18 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.