You can update, there are no issues, anymore and the warning is gone, too.

WOHOOOOO!!!!

You can do your pacman -Syu now @rottenmummy@lemmy.ml ;-)

Oh that makes sense. Thanks a lot for explaining 🙇🙇🙇

It's not in the repos yet, 6.6.5 is currently the latest: https://packages.cachyos.org/package/extra/any/plasma-meta

6.7.0 is currently in extra-testing: https://archlinux.org/packages/?sort=&q=plasma-desktop&maintainer=&flagged=

It shouldn't be in there long before it filters down.
Running an Arch derivative is normally about being at the cutting edge, not the "ow I'm bleeding" edge.

Your system may be reading the default config from /usr/lib/sddm/sddm.conf.d/default.conf, in which case the config file in /etc will probably be empty. You should not edit the contents of a default config.

The recommended location for sddm.conf is within the /etc/sddm.conf.d/ directory, so also check for files there.

is it normal that the sddm.conf is empty? it's supposed to be /etc/sddm.conf right?

thank you!

ah i haven't thought of that
thank you!

I did some quick research and SDDM can do what you want by editing the sddm.conf file. You just have to add the username to HideUsers in the [Users] section.

In that case, it looks like you need to edit sddm.conf and set the HideUsers= field. Source.

on another pc i actually do do that, but i was wondering if there was another way

i'm using kde with sddm i believe

The answer will depend on which desktop environment or login manager you're using.

System users are not the right solution. The use-case for such accounts is when you want certain background services to be linked to a non-human account. Eg: Serving web requests from an http user account that only has access to nginx and the /var/www directory. By default, users created in this way don't even have a home directory.

Depending on which display manager you use you could always just use a theme that requires typing a username rather than selecting from a list. I know there are a few SDDM themes like that.

Not outside of the USA.

Does this make using CachyOS illegal?

Thank god

The translated (by the mozilla translation) article:

CachyOS is based in Germany, with founders in Germany and Russia. Laws on age verification do not exist there.

So the bottom line is: CachyOS does nothing in terms of age verification.

CachyOS uses the SystemD framework. There are no plans to stop using it or use an alternative. CachyOS does not implement anything to do with age verification via SystemD. SystemD does not even have age verification.

So the bottom line is: there is no age verification with SystemD.

— Moderator in the forum of CachyOS

Age verification:

    CachyOS is not located in areas where this is an issue.
    CachyOS is not taking any steps in this regard.

SystemD:

    CachyOS uses SystemD.
    If you do not want to use SystemD, find a different distribution.

STOP asking for these two things.
STOP attacking people for these two things.
STOP being radical on these two issues.

Should anything ever change in these two things, there will be a corresponding announcement.

— Moderator in the forum of CachyOS

Garuda Linux will not introduce age verification measures because the jurisdictions to which Garuda Linux is subject do not have laws requiring an age check.

— Garuda Linux

I would assume it’s different so that different users can configure their lock screens. The login screen shows up before a user has a chance to log in.

Ahh thank you. Was a matter of bad UI. There's a tiny button in the top right corner to modify the appearance instead of loading the options on the massive blank screen. My screen is big and this was maximized so even was less noticable when I was looking before :) Anyway, thanks!

There's a different section under "Screen Locking" in the settings sidebar just below "Login Screen" that controls the lock screen you're talking about. It's different from "Login Screen"

I don't know why they're different, but at least it's not a bug - just two separate settings.

We have thought about this but we opted out, since we do not see all too much benefit from our side. Handheld stuff is not our major focus. Also, we had some concerns that this could get a "burocractic loophole", which seemd to be more or less true so far.

Additionally, to us all this "initiative" locked like an emergency rushed thing, so that Bazzite finds new kernel maintainers and for other technical stuff after kicking the maintainer, which basically made most integration work for them

We neither want to be associated with "Playtron" too. There are more reasons, but Ill keep them out of the public

Well that answered my question quickly lol

On KDE, it looks like to be different, with different bugs, could be gnome being gnome. Seems fixed on KDE Plasma 6.