| Summary: | Wrong umask or mount option in /etc/fstab for ntfs partitions prevents Plasma's App to cut/paste files as user | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Ami age <kourki> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | geiger.david68210, lewyssmith, mageia, ouaurelien, thierry.vignaud |
| Version: | Cauldron | Keywords: | UPSTREAM |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://bugs.kde.org/show_bug.cgi?id=364039 | ||
| Whiteboard: | |||
| Source RPM: | drakxtools-18.33-1.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Ami age
2020-09-26 11:50:57 CEST
Hi, in French first: Je pense que le bug vient du fait que /etc/fstab n'a pas les "bonnes options" pour le volume monté et qui le rendent inaccessibles à l'utilisateur normal. Je voudrais savoir si les disques sont USb (externes) ou SATA (internes)? Back in English: I think bug is in wrong options in /etc/fstab for partitions that must be accessible from users. Question: Are the disks USB external or SATA internal? CC:
(none) =>
ouaurelien in English translated with google: All the disks are connected to the motherboard in SATA. Mageia is simply installed alongside other partitions and nft disks. The fstab is the one created when installing Mageia. en français : Tous les disques sont raccordés sur la carte mère en SATA. Mageia est simplement installé à coté d'autres partitions et disques en nfts. Le fstab est celui crée à l'installation de Mageia. Hi, thanks answering this. I suspect wrong mount options. Can you attach here your /etc/fstab? Sometimes, internal ntfs drives are mounted by systemd-unit and belong to root user. External ntfs drives are mounted by user request and belong to him, not root. I don't know why this appears long time after an install. Where is the bug? Wrong options written by diskdrake (DrakX)? Wrong qt behavior? CC'd David G and Neoclust maintainers of KDE and tv from drakxtools for this. Source RPM:
(none) =>
drakxtools-18.33-1.mga8.src.rpm Thank you Ami for all the pointers, which agree with an earlier bug... I think this bug is a duplicate of Bug 25922 (raised for M7), see especially: https://bugs.mageia.org/show_bug.cgi?id=25922#c1 "Workaround seems to be to add uid and gid to mount options". I have updated that bug to Cauldron, MGA7TOO There is another related bug: https://bugs.mageia.org/show_bug.cgi?id=7985#c22 which notes "The problem doesn't appear in both case when I try to explore the content of these HDD with PCManFM-QT PCManFM or Thunar" Something to try. You can still comment on this bug even though it is closed. --- Voir Bug 25922. Pour éviter, ajouter uid et gid aux options 'mount' (je ne sais pas quels). Vous pourriez aussi essayer d'autres non-KDE gestionnaires de fichiers tels notés dessus. Vous pouvez encore ajouter de commentaires sur ce bug. *** This bug has been marked as a duplicate of bug 25922 *** Keywords:
(none) =>
UPSTREAM @Aurelien Oudelet I did not specify any mounting option. I just installed Mageia 8 cauldron beta1 (and Mageia 7) on ext4 partitions next to nfts partitions without specifying anything for the latter. I know there are workarounds. My bug repository is there so that Mageia is fully operational with the default settings. here is my current FSTAB: # Entry for /dev/sda1 : UUID=f693a385-3b64-4a84-b367-22792d01d365 / ext4 relatime,acl 1 1 # Entry for /dev/sda5 : UUID=5e9c38a2-7cfd-4f68-96b9-6a4a853caceb /home ext4 relatime,acl 1 2 # Entry for /dev/sdb1 : UUID=2AF26C522A012743 /media/win_c ntfs-3g defaults,nofail,umask=000 # Entry for /dev/sdc1 : UUID=215979685F905509 /media/win_c2 ntfs-3g defaults,nofail,umask=000 # Entry for /dev/sdb2 : UUID=18E28D4A5EE679DA /media/win_d ntfs-3g defaults,nofail,umask=000 # Entry for /dev/sdc2 : UUID=9AA894ECA894C7E1 /media/win_d2 ntfs-3g defaults,nofail,umask=000 none /proc proc defaults 0 0 # Entry for /dev/sdb6 : UUID=c630b2ef-35b1-495a-85fd-27cd62302869 swap swap defaults 0 0 -------------------- en français : @Aurelien Oudelet Je n'ai précisé aucune option de montage. J'ai juste installé Mageia 8 cauldron beta1 (et Mageia 7) sur des partitions ext4 à coté de partitions nfts sans rien préciser pour ces dernières. Je sais qu'il y a des solutions de contournement. Mon dépot de bug est là pour que Mageia soit totalement opérationnelle avec les réglages par défaut. voici mon FSTAB actuel : (voir ci dessus) in the ccm disk manager, I checked the nosuid option and that does not solve the bug here is the corresponding fstab # Entry for /dev/sda1 : UUID=f693a385-3b64-4a84-b367-22792d01d365 / ext4 relatime,acl 1 1 # Entry for /dev/sda5 : UUID=5e9c38a2-7cfd-4f68-96b9-6a4a853caceb /home ext4 relatime,acl 1 2 # Entry for /dev/sdb1 : UUID=2AF26C522A012743 /media/win_c ntfs-3g umask=000,nosuid,nofail 0 0 # Entry for /dev/sdc1 : UUID=215979685F905509 /media/win_c2 ntfs-3g umask=000,nosuid,nofail 0 0 # Entry for /dev/sdb2 : UUID=18E28D4A5EE679DA /media/win_d ntfs-3g umask=000,nosuid,nofail 0 0 # Entry for /dev/sdc2 : UUID=9AA894ECA894C7E1 /media/win_d2 ntfs-3g umask=000,nosuid,nofail 0 0 none /proc proc defaults 0 0 # Entry for /dev/sdb6 : UUID=c630b2ef-35b1-495a-85fd-27cd62302869 swap swap defaults 0 0 -------------- en français : dans gestionnaire des disque du ccm, j'ai coché l'option nosuid et celà ne résoud pas le bug voici le fstab correspondant by deleting directly in the umask = 000 fstab file, the bug is solved, cutting and pasting it with an ntfs partition works. here is the corresponding fstab: # Entry for /dev/sda1 : UUID=f693a385-3b64-4a84-b367-22792d01d365 / ext4 relatime,acl 1 1 # Entry for /dev/sda5 : UUID=5e9c38a2-7cfd-4f68-96b9-6a4a853caceb /home ext4 relatime,acl 1 2 # Entry for /dev/sdb1 : UUID=2AF26C522A012743 /media/win_c ntfs-3g ,nofail 0 0 # Entry for /dev/sdc1 : UUID=215979685F905509 /media/win_c2 ntfs-3g ,nofail 0 0 # Entry for /dev/sdb2 : UUID=18E28D4A5EE679DA /media/win_d ntfs-3g ,nofail 0 0 # Entry for /dev/sdc2 : UUID=9AA894ECA894C7E1 /media/win_d2 ntfs-3g ,nofail 0 0 none /proc proc defaults 0 0 # Entry for /dev/sdb6 : UUID=c630b2ef-35b1-495a-85fd-27cd62302869 swap swap defaults 0 0 ------------- en français : en supprimant directement dans le fichier fstab umask=000, le bug est résolu, le couper coller avec une partition ntfs fonctionne. voici le fstab correspondant : Merci pour votre dernier post - très simple et efficace. A noter. Thanks for that post, helpful to others. Simple & effective, even though it should not be necessary. |