Bug 1385222

Summary: removable media applet mounts as root, effectively making the media read-only for the user
Product: [Fedora] Fedora Reporter: Karel Volný <kvolny>
Component: plasma-workspaceAssignee: KDE SIG <kde-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: jgrulich, kde-sig, me, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:26:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Karel Volný 2016-10-15 11:11:24 UTC
Description of problem:
For convenience, I have setup a mount point to mount some media as user. However, trying to mount a device that matches the entry using the removable media applet in panel, it gets mounted as root, so
a) the user cannot write the media
b) the user cannot unmount the media manually (but it can be done using the applet)
c) in addition, I'm getting "invalid url" error when trying to open the media in Dolphin via the applet

Version-Release number of selected component (if applicable):
plasma-workspace-5.7.5-2.fc24.x86_64

How reproducible:
always

Steps to Reproduce:
1. # mkdir /mnt/sdb1
2. # echo "/dev/sdb1       /mnt/sdb1       auto    noauto,user,utf8        0       0" >> /etc/fstab
3. connect something that gets /dev/sdb assigned and has an usable partition so /dev/sdb1 can be mounted
4. wait for removable media popup, choose that you want to open the media in Dolphin
5. ls -l /mnt/sdb1/
6. umount ("eject") the device using the removable media applet
7. try to mount it again

Actual results:
4. you get an error dialogue instead of Dolphin window
5.
celkem 32
drwxr-xr-x. 4 root root 16384 10. říj  2011 DCIM
drwxr-xr-x. 2 root root 16384 10. říj  2011 MISC
7. impossible, the device no longer appears in the list

Expected results:
4. no error, you get the directory /mnt/sdb1 opened in Dolphin
5.
celkem 32
drwxrwxr-x. 4 kvolny kvolny 16384 10. říj  2011 DCIM
drwxrwxr-x. 2 kvolny kvolny 16384 10. říj  2011 MISC
7. you can mount/umount the media how many times you wish, the device doesn't disappear

Additional info:

Comment 1 Fedora End Of Life 2017-07-25 23:29:14 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-08-08 19:26:10 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.