Bug 179320

Summary:	Links to devices don't honor user option in /etc/fstab
Product:	[Unmaintained] kdelibs	Reporter:	Nicolas L. <kde>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	AAW, andresbajotierra, asraniel, christophe-gaubert
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Nicolas L. 2009-01-02 00:02:54 UTC

Version:            (using Devel)
Installed from:    Compiled sources

Description of problem:
I created a folderview applet on the desktop then added several links to
devices (partitions on both an external USB drive and an internal SATAII
drive). The drives' entries in /etc/fstab include the user option and the
partitions mount as expected from konsole. Trying to mount them from the links
in the folderview applet gives me a message that only root can mount this
device.

Version-Release number of selected component (if applicable):
kde 4.2 beta 2

How reproducible:
Every time

Steps to Reproduce:
1. Set up entries in fstab that include user and noauto options
2. Add folderview app to desktop
3. Add links to the appropriate devices
4. Try to mount.

Comment 1 Dario Andres 2009-05-17 00:31:45 UTC

If you try to open this links from Dolphin, do you get the same issue? I guess this is a bug on kdelibs more than in folderview itself. (the class that mounts devices)
Thanks

Comment 2 AAW 2009-05-29 20:37:45 UTC

Re: Comment #1

Same behavior under Folderview and Dolphin. Using Mandriva Cooker (kdelibs4-4.2.88-1mdv2010.0) on x86_64.

Comment 3 Christophe Gaubert 2009-10-05 18:19:01 UTC

Isn't it a problem with HAL ? If I'm not wrong, HAL refuse to mount a device when it is present in /etc/fstab.

Comment 4 Christoph Cullmann 2024-09-14 17:07:13 UTC

Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have resolved this bug.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann