During a fresh install, if you use Advanced to specify a UID/GID under 1000, you get prompted once exiting the Advanced dialog, and then again when exiting the root password/first user dialog. Reproducible: Steps to Reproduce:
I don't have a strong opinion about this one. Should we remember the answer and not ask again? Or should we warn again & again as we know it might not work well with other programs expecting UIDs > 1000 (eg: gdm and the like)?
Keywords: (none) => USABILITYCC: (none) => mageia, thierry.vignaud
Would probably be nice to only warn once I guess. Note that gdm itself doesn't care, but it uses accountsdaemon which does care although also has heuristics so that users >=500 and <1000 do still show up if they look like real users.
I'd vote for once and once only. People who do this (through Advanced) are likely to know what they are doing. One warning is enough for anyone who wanders in there by mistake.
well iiuc we could avoid asking and asking, we could set a state variable to get the first answer, but that would mean -in the case we later answer no- that adding a new user and changing its id to a low value would not prompt anything but neither allow to go on until the value is set correctly. Another solution could be to add a flag (don't show it again) on that dialog, not saved so valid only for the install session, but i don't know if ask_yesorno has that managed though...
CC: (none) => anaselli
and always iiuc that subroutine is called either for GID or for UID so it should be considered that when is going to be hidden
I think it's really a single issue, and a single composite message covering both UID and GID (as opposed to separate messages for UID and GID) with a "don't show this again" is a good approach.
Thierry could it be used ask_from_ with two type=button (yes and no) and one bool (don't ask again) to implement such a dialog instead of ask_yesorno?
Whiteboard: (none) => MGA5TOO FOR_ERRATA
Whiteboard: MGA5TOO FOR_ERRATA => FOR_ERRATA
Minor issue, I don't think we need to add it to Errata. Removing FOR_ERRATA.
Whiteboard: FOR_ERRATA => (none)
Target Milestone: --- => Mageia 6
Would this really be that hard to fix ?
Assignee: bugsquad => mageiatoolsTarget Milestone: Mageia 6 => ---
Problem still exists in Mageia 6: just ran into the same problem there on multiple machines (where I had to take over old uid/gid that are used on lots of file systems and can't therefore just change the ids), and for each user, there are 4 (four!) warning popups, which is quite annoying: first after editing the uid and gid: 1. warning popup about uid 2. separate (why?) warning popup about gid then the same two popups again after accepting the user. At a rate of 4 popups per user… when you have systems with several users, that makes for a lot of annoying popups.
CC: (none) => c934w-xavm493b
Ping ?
Ping again ?