Description of problem: all the devices /dev/ttyS* and /dev/ttyUSB0 belong to user root, and to the group dialout to which ordinary users do not belong by default. Version-Release number of selected component (if applicable): How reproducible: Check the permissions of devices /dev/tty* after a reboot. Steps to Reproduce: 1.ls -l /dev/tty* Solution seems to be to add all users to the dialout group when user is created.
CC: (none) => renaud
CC: (none) => thierry.vignaudAssignee: bugsquad => mageiaSource RPM: (none) => udev
If the user is add only to the dialout group, only root can access the serial ports /dev/ttyS0 and /dev/ttyUSB0. Solution for me is to add all users to the dialout group and uucp group when user is created. With dialout and uucp added, it's working Ok ( MAGEIA 2 / i586) In French: Si l'utilisateur est ajouté pour faire partie du groupe dialout, ce n'est pas suffisant et seul root peut accéder aux ports séries /dev/ttyS0 et /dev/ttyUSB0. La solution pour moi a été d'ajouter l'utilisateur au groupe uucp. Avec l'utilisateur membre de dialout et uucp, le fonctionnement est correct (MAGEIA 2 / i586)
CC: (none) => tc39
With due respect, your Worship, I have adder the user to dialout alone (no uucp) and he can now access /dev/ttyUSB0. (Mageia 1 / I586) Siouplait, msieur, j'ai rajoute l'utilisateur au groupe dialout seulement, et il peut acceder a /dev/ttyUSB0 sans avoir le groupe uucp. (Mageia 1 / I586)
A device can only have one associated group, so it's either dialout or uucp, but not both. Maybe it changed from MGA1 to MGA2.
CC: (none) => ftg
(In reply to comment #3) > A device can only have one associated group, so it's either dialout or uucp, > but not both. Maybe it changed from MGA1 to MGA2. Not technically 100% true when you consider ACLs, but I know what you mean. Theoretically we could configure things with udev rules to mark certain devices as belonging to a "seat" This would then allow ACLs to be applied when a user logs in on a given seat. I'm not sure how it works with USB tho'. I'll ask upstream next time I'm chatting with them.
Is there a confusion here between the user belonging to several groups, and the device ?
(In reply to comment #5) > Is there a confusion here between the user belonging to several groups, and the > device ? Nope. The group based perms on the device will apply if the user is in the group of the device. The user can be in as many other groups as they want.
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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 Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX