Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1076138

Summary: [abrt] nautilus: nautilus_file_updated_deep_count_in_progress(): nautilus killed by SIGABRT
Product: Red Hat Enterprise Linux 7 Reporter: Martin <mholec>
Component: nautilusAssignee: Alexander Larsson <alexl>
Status: CLOSED WORKSFORME QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: mclasen, mholec, tpelka, vbenes
Target Milestone: rcKeywords: Reopened
Target Release: 7.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:bb9acf5a5fd9e98155cba43cb9636a444095e4c1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-06 06:28:39 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: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: sosreport.tar.xz none

Description Martin 2014-03-13 16:02:02 UTC 
Description of problem:
reproducible: randomly

1. Select directory, right click on it and select "Properties"
2. Keep Properties open, create new directory in Nautilus.
3. Open Properties for new directory.

Nautilus crashes with:
Initializing nautilus-open-terminal extension
**
ERROR:nautilus-file.c:7137:nautilus_file_updated_deep_count_in_progress: assertion failed: (nautilus_file_is_directory (file))
Aborted (core dumped)

Version-Release number of selected component:
nautilus-3.8.2-4.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        nautilus
crash_function: nautilus_file_updated_deep_count_in_progress
executable:     /usr/bin/nautilus
kernel:         3.10.0-108.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #4 nautilus_file_updated_deep_count_in_progress at nautilus-file.c:7137
 #6 deep_count_next_dir at nautilus-directory-async.c:2670
 #7 deep_count_more_files_callback at nautilus-directory-async.c:2716
 #8 next_async_callback_wrapper at gfileenumerator.c:311
 #9 g_task_return_now at gtask.c:1105
 #10 complete_in_idle_cb at gtask.c:1114
 #14 g_main_context_iteration at gmain.c:3766
 #15 g_application_run at gapplication.c:1623
Comment 1 Martin 2014-03-13 16:02:06 UTC 
Created attachment 874037 [details]
File: backtrace
Comment 2 Martin 2014-03-13 16:02:13 UTC 
Created attachment 874038 [details]
File: cgroup
Comment 3 Martin 2014-03-13 16:02:22 UTC 
Created attachment 874040 [details]
File: core_backtrace
Comment 4 Martin 2014-03-13 16:02:25 UTC 
Created attachment 874041 [details]
File: dso_list
Comment 5 Martin 2014-03-13 16:02:27 UTC 
Created attachment 874042 [details]
File: environ
Comment 6 Martin 2014-03-13 16:02:29 UTC 
Created attachment 874043 [details]
File: limits
Comment 7 Martin 2014-03-13 16:02:31 UTC 
Created attachment 874044 [details]
File: maps
Comment 8 Martin 2014-03-13 16:02:33 UTC 
Created attachment 874045 [details]
File: open_fds
Comment 9 Martin 2014-03-13 16:02:38 UTC 
Created attachment 874046 [details]
File: proc_pid_status
Comment 10 Martin 2014-03-13 16:02:40 UTC 
Created attachment 874047 [details]
File: var_log_messages
Comment 11 Martin 2014-03-13 16:04:24 UTC 
Created attachment 874048 [details]
File: sosreport.tar.xz
Comment 15 Matthias Clasen 2014-10-03 18:10:26 UTC 
I failed to reproduce this here. Is there any more specific information ? does the folder first opened have to be big, so counting files will take a while ? does the newly created folder have to reside inside the original one ?
Comment 16 Tomas Pelka 2014-10-06 06:28:39 UTC 
(In reply to Matthias Clasen from comment #15)
> I failed to reproduce this here. Is there any more specific information ?
> does the folder first opened have to be big, so counting files will take a
> while ? does the newly created folder have to reside inside the original one
> ?

I don't know, Martin is not with RedHat anymore. I'm going to close as works for me. 

Tom
Comment 17 Red Hat Bugzilla 2023-09-14 02:04:59 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days