Bug 233411

Summary:	GNOME umounts volumes while exited from GNOME by root
Product:	Red Hat Enterprise Linux 4	Reporter:	masanari iida <masanari_iida>
Component:	gnome-volume-manager	Assignee:	David Zeuthen <davidz>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.3	CC:	mclasen
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 16:14: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:

Description masanari iida 2007-03-22 09:43:49 UTC

Description of problem:
GNOME umount some Fixed disk partitions while logout from the GNOME session.

Version-Release number of selected component (if applicable):
RHEL4.3
GNOME 2.8.0-5
hal-0.4.2-3.EL4
hal-gnome-0.4.2-3.EL4

How reproducible:
Always 

Steps to Reproduce:
0. Make sure hal daemon is running.
1. Login to GNOME (root user)
2. Mount Fixed scsi disk partition by mount command.
3. Logout from GNOME. (Click logout from menu)
4. Login again into the GNOME, and do "mount".

Actual results:
The Fixed scsi disk partition mounted on (2) umounted by someone.

Expected results:
The Fixed scsi disk partition should be keep be mounted 
by the system even after root user logout from GNOME. 


Additional info:
Reproduced with GNOME.  But not reproduced with twm.
If I stop hal daemon, the symptom does not occur.
With network login (ssh) and mount, it work as expected.
It seemed similar bug is reported as Red Hat Bugzilla #192079, 
but no progress so far.

If this is a bug, please fix it.
If this is expected behavior, it should be documented.

Comment 1 Jiri Pallich 2012-06-20 16:14:39 UTC

Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.