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.

Created attachment 483104 [details]
sosreport

Description of problem:

Process /usr/libexec/gvfs-gdu-volume-monitor was killed by signal 6 (SIGABRT)

Version-Release number of selected component (if applicable):
architecture: x86_64
component: gvfs
executable: /usr/libexec/gvfs-gdu-volume-monitor
package: gvfs-1.4.3-9.el6
release: Red Hat Enterprise Linux Server release 6.0 (Santiago)

How reproducible:
randomly

Steps to Reproduce:
1.
2.
3.
  
Actual results:
gvfs crashed.

Expected results:
gvfs should not crash

Additional info:

(In reply to comment #1)
message="assertion failed: (pool != NULL)"

I've seen this before many times, but so far we haven't found the real cause. Not having pool initialized means that connection to system udisks daemon failed.

Could you try doing `udisks --dump` to see if it fails? (no output needed)
Were there any selinux denials?

This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 6 and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days