David C Rankin composed on 2026-04-14 18:05 (UTC-0500):
Felix Miata wrote:
If root works and a standard user doesn't, it inevitably boils down to permissions in my experience.
Mine too, but I can't find any that are wrong user:group or obviously wrong permissions but I don't know that I would recognize wrong permissions. Attachment is output of:
# ls -alRhn/home/<username> --group-directories-first
Sorry, forgot to say, give your user 'root' permissions just to test.
What chmod and/or chown would do that?
Felix,
Does leap 16 use selinux like Tumbleweed or still on apparmor. You
Given SElinux seems to be the SUSE future, I selected it instead of Apparmor for this 16.0 installation for a new used x86_64 v2 PC for my brother. I also put Mint Cinnamon on it, as my other brother likes it better, so if Mint becomes the preference, I get less work to expect.
can try a global disable adding the kernel parameters:
security=selinux selinux=1 enforcing=0
security=selinux selinux=0 enforcing=0 is what I think I used on Mike's suggestion that seems to have confirmed SElinux is the problem.
Also on TW, there were changes to systemd loginctl that changed the way the user "seat" is seen. This had a few side-effect and was fixed on TW.
Mike may be correct and this may be a UID/GID permission issue, but given experience with TW over the past year, it seems like it may also be a selinux or loginctl issue as well.
Other than disabling it with the kernel command line params, I don't have any silver bullets for you. selinux and loginctl are both Andrei type issues :)
I guess I need to post where Andrei should see it.