Bug 683315

Summary: [abrt] gvfs-1.4.3-9.el6: g_assertion_message: Process /usr/libexec/gvfs-gdu-volume-monitor was killed by signal 6 (SIGABRT)
Product: Red Hat Enterprise Linux 6 Reporter: prashant ingale <pingale>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: dkochuka, jwest, rdassen, tbzatek, tsmetana, vgaikwad
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-18 13:52:54 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:
Bug Depends On:    
Bug Blocks: 1002711    

Description prashant ingale 2011-03-09 05:43:23 UTC
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:

Comment 3 Tomáš Bžatek 2011-03-09 15:10:48 UTC
(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?

Comment 11 Chris Williams 2015-09-18 13:52:54 UTC
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.

Comment 12 Red Hat Bugzilla 2023-09-14 01:23:18 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days