Bug 203504 - User can no longer unmount hotpluggable storage media
Summary: User can no longer unmount hotpluggable storage media
Status: CLOSED DUPLICATE of bug 203073
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase   
(Show other bugs)
Version: 5
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2006-08-22 05:24 UTC by Stefan Becker
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-22 15:33:44 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Stefan Becker 2006-08-22 05:24:56 UTC
Description of problem:
My FC5 installation just got updated to the KDE 3.5.4 packages released last
week. Now end users can't unmount hotpluggable storage media they mounted

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Plug in USB storage device (I tried ext3 & vfat formatted ones)
2. Press OK on the mount dialog or double-click the storage media icon
3. Use "Safely remove" on the mounted storage media icon
Actual results:
Media stays mounted

Expected results:
Media should be unmounted

Additional info:
hal & selinux packages weren't updated so the changes in KDE 3.5.4 cause or have
unconvered the problem.

Only root can unmount those devices, because /etc/fstab doesn't get updated when
a hotpluggable storage media is connected. That might be the root problem and
therefore a hal problem if it is responsible to update /etc/fstab. I browsed
through the hal storage media scripts and it seems it doesn't update /etc/fstab
anywhere. The old(?) tools updfstab or fstab-sync do no longer exist in FC5.

Comment 1 Ngo Than 2006-08-22 15:33:44 UTC

*** This bug has been marked as a duplicate of 203073 ***

Note You need to log in before you can comment on or make changes to this bug.