Description of problem: /etc/sddm.conf has MinimumUID=500 under Mageia specific configuration. but Mageia switched to MinimumUID=1000 many versions ago.
Hi, thanks report this. I can reproduce it in Mageia 8 Beta 1. Assigning to KDE Team maintainers.
Whiteboard: (none) => MGA7TOOSeverity: normal => majorCC: (none) => ouaurelienAssignee: bugsquad => kdeTarget Milestone: --- => Mageia 8Version: 7 => CauldronSource RPM: sddm-0.18.1-3.mga7 => sddm-0.18.1-4.mga8.src.rpmSummary: /etc/sddm.conf has MinimumUID=500. => /etc/sddm.conf has MinimumUID=500 to list users
We support users upgrading from previous Mageia versions who have a UID still in the 500-999 range. In fact, if a user using such a UID does *not* work, that is a bug and you should file a report. SDDM has been patched to filter out system users so that it does not display them. Hopefully that is still working too.
Resolution: (none) => INVALIDStatus: NEW => RESOLVED
@ David, I recently see my sddm.conf written with MinimumUID=500 with a fresh install of Mageia 8 Beta 1. So I think this is a bug, is not it?
Ie, when sddm is refreshed, sddm.conf is not replaced, but rather a sddm.conf.rpmnew is created. Thus if the user upgrades from Mageia 6, sddm.conf should not be replaced and the old MinimumUID should stay there. If it is a fresh install, then the new sddm.conf with the MinimumUID=1000 would be installed, especially since Mageia fills up the uids<1000 with a whole variety of system uids. Ie, the support for minuid=500 is pretty ratty and difficult already. It is of course true that Mageia will not use a uid (eg for some ancient user with say uid=250) that is already in use. Having sddm MinimumUID=1000 would just be another hurdle that the user would have to put up with to keep his old numbering. But then it was something like Mageia 3 or earlier (more than 5 years ago) that Mageia switched to uid>=1000 for users. I hung on till about 3 years ago with my uid=250 and finally just did find / -uid 250 -exec chown 1000 \{\} + (and similarly for a few other of my users)
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
It doesn't matter when the switch was made. Some users may have low UIDs for a long time. Anyway, unless the login screen is showing system users, there is no bug.
Status: REOPENED => RESOLVEDResolution: (none) => INVALID