I think that is because there are systems in use that have been progressively upgraded since the time when the starting uid on Mageia was 500. 

Existing uid's are preserved during a distro upgrade.

CC: (none) => jim

(In reply to James Kerr from comment #1)
> I think that is because there are systems in use that have been
> progressively upgraded since the time when the starting uid on Mageia was
> 500. 
> 
> Existing uid's are preserved during a distro upgrade.

IINM, there are some cauldron users who have been updating cauldron since Mageia was born, never doing a fresh install.. they'll still have 5xx UIDs on their systems.

Assigning to KDE team for them to decide what to do with this report.

CC: (none) => marja11
Assignee: bugsquad => kde

(In reply to Marja Van Waes from comment #2)

> 
> IINM, there are some cauldron users who have been updating cauldron since
> Mageia was born, never doing a fresh install.. they'll still have 5xx UIDs
> on their systems.
> 
> Assigning to KDE team for them to decide what to do with this report.

I have been UID/GID 501 since Mandrake 7.1 made it so and I preserve this user across multiple machines as they get added to the LAN, fwiw.  IIRC, I have to change the minimum in MCC to see my user in the login screen for, typically, the plasma desktop when installing new, keeping /home.  If it became necessary to change it all for good reason, I imagine I could but would prefer not to.  Thanks.

CC: (none) => rolfpedersen

This is likely INVALID, but another possible approach is what IIRC we did with KDM, which is set it to 1000 but have it patched to also recognize actual (and not system) users in the 500-1000 range.

Actually, default sddm.conf should state 1000 as intended

It's defined as:
%config(noreplace) %{_sysconfdir}/sddm.conf

in spec, so upgrades would keep their old 500, but new installs would get 1000

CC: (none) => tmb

hi ,

closing bug report

Status: NEW => RESOLVED
Resolution: (none) => FIXED