Nothing useful from users send this last night, so perhaps someone here can help?
I just did an openSUSE Leap 16 installation on a new used PC with FM2+ AMD. Only IceWM was installed initially, then TDE, then Plasma. TDM is active DM. Plasma and IceWM sessions work normally, but for TDE for the only user, instead a popup:
Call to lnusertemp failed (temporary directories full?). Check your installation.
# df / Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 32073536 6494584 23924168 22% / # ls -lh /*/tmp /tmp lrwxrwxrwx. 1 1050 russfx 3 Mar 31 2010 /nfs/tmp -> Tmp
/tmp: total 8.0K drwx------. 4 root root 140 Apr 13 11:37 1921070663 drwxrwxrwt. 2 root root 40 Apr 13 11:36 .font-unix drwxrwxrwt. 2 root root 60 Apr 13 11:37 .ICE-unix -rw-------. 1 root root 0 Apr 13 11:38 mc.pwd.k6Xx2P drwx------. 2 root root 40 Apr 13 11:38 mc-S9WPN3 drwx------. 3 root root 60 Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-chronyd.service-LWQWx6 drwx------. 3 root root 60 Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-dbus-broker.service-3Mvje9 drwx------. 3 root root 60 Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-irqbalance.service-JzqOxF drwx------. 3 root root 60 Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-polkit.service-VD9khC drwx------. 3 root root 60 Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-systemd-logind.service-n1wbjJ drwx------. 2 root root 60 Apr 13 11:37 tde-root drwxr-xr-x. 3 root root 60 Apr 13 11:37 tdesocket-global drwx------. 2 root root 120 Apr 13 11:37 tdesocket-root -rw-r--r--. 1 root root 135 Apr 13 12:05 tmps.txt -r--r--r--. 1 root root 11 Apr 13 11:37 .X0-lock drwxrwxrwt. 2 root root 60 Apr 13 11:37 .X11-unix drwxrwxrwt. 2 root root 40 Apr 13 11:36 .XIM-unix
/var/tmp: total 28K drwx------. 3 root root 4.0K Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-chronyd.service-5fwrv9 drwx------. 3 root root 4.0K Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-dbus-broker.service-vCN4ts drwx------. 3 root root 4.0K Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-irqbalance.service-VA1jOT drwx------. 3 root root 4.0K Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-polkit.service-yKUPkD drwx------. 3 root root 4.0K Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-systemd-logind.service-szBEoE drwx------. 4 root root 4.0K Apr 12 19:32 tdecache-root drwxr-xr-x 2 root root 4.0K Apr 13 11:53 zypp.tmp #
Root TDE session works fine. This is my first use of SELinux. Could it be related? If not, what would? I see no suspects in dmesg or journal.
On 13/04/2026 21:42, Felix Miata via tde-devels wrote:
Nothing useful from users send this last night, so perhaps someone here can help?
I just did an openSUSE Leap 16 installation on a new used PC with FM2+ AMD. Only IceWM was installed initially, then TDE, then Plasma. TDM is active DM. Plasma and IceWM sessions work normally, but for TDE for the only user, instead a popup:
Call to lnusertemp failed (temporary directories full?). Check your installation.
# df / Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 32073536 6494584 23924168 22% / # ls -lh /*/tmp /tmp lrwxrwxrwx. 1 1050 russfx 3 Mar 31 2010 /nfs/tmp -> Tmp
/tmp: total 8.0K drwx------. 4 root root 140 Apr 13 11:37 1921070663 drwxrwxrwt. 2 root root 40 Apr 13 11:36 .font-unix drwxrwxrwt. 2 root root 60 Apr 13 11:37 .ICE-unix -rw-------. 1 root root 0 Apr 13 11:38 mc.pwd.k6Xx2P drwx------. 2 root root 40 Apr 13 11:38 mc-S9WPN3 drwx------. 3 root root 60 Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-chronyd.service-LWQWx6 drwx------. 3 root root 60 Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-dbus-broker.service-3Mvje9 drwx------. 3 root root 60 Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-irqbalance.service-JzqOxF drwx------. 3 root root 60 Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-polkit.service-VD9khC drwx------. 3 root root 60 Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-systemd-logind.service-n1wbjJ drwx------. 2 root root 60 Apr 13 11:37 tde-root drwxr-xr-x. 3 root root 60 Apr 13 11:37 tdesocket-global drwx------. 2 root root 120 Apr 13 11:37 tdesocket-root -rw-r--r--. 1 root root 135 Apr 13 12:05 tmps.txt -r--r--r--. 1 root root 11 Apr 13 11:37 .X0-lock drwxrwxrwt. 2 root root 60 Apr 13 11:37 .X11-unix drwxrwxrwt. 2 root root 40 Apr 13 11:36 .XIM-unix
/var/tmp: total 28K drwx------. 3 root root 4.0K Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-chronyd.service-5fwrv9 drwx------. 3 root root 4.0K Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-dbus-broker.service-vCN4ts drwx------. 3 root root 4.0K Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-irqbalance.service-VA1jOT drwx------. 3 root root 4.0K Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-polkit.service-yKUPkD drwx------. 3 root root 4.0K Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-systemd-logind.service-szBEoE drwx------. 4 root root 4.0K Apr 12 19:32 tdecache-root drwxr-xr-x 2 root root 4.0K Apr 13 11:53 zypp.tmp #
Root TDE session works fine. This is my first use of SELinux. Could it be related? If not, what would? I see no suspects in dmesg or journal.
If root works and a standard user doesn't, it ineveitably boils down to permissions in my experience.
On 13/04/2026 21:42, Felix Miata via tde-devels wrote:
Nothing useful from users send this last night, so perhaps someone here can help?
I just did an openSUSE Leap 16 installation on a new used PC with FM2+ AMD. Only IceWM was installed initially, then TDE, then Plasma. TDM is active DM. Plasma and IceWM sessions work normally, but for TDE for the only user, instead a popup:
Call to lnusertemp failed (temporary directories full?). Check your installation.
# df / Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 32073536 6494584 23924168 22% / # ls -lh /*/tmp /tmp lrwxrwxrwx. 1 1050 russfx 3 Mar 31 2010 /nfs/tmp -> Tmp
/tmp: total 8.0K drwx------. 4 root root 140 Apr 13 11:37 1921070663 drwxrwxrwt. 2 root root 40 Apr 13 11:36 .font-unix drwxrwxrwt. 2 root root 60 Apr 13 11:37 .ICE-unix -rw-------. 1 root root 0 Apr 13 11:38 mc.pwd.k6Xx2P drwx------. 2 root root 40 Apr 13 11:38 mc-S9WPN3 drwx------. 3 root root 60 Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-chronyd.service-LWQWx6 drwx------. 3 root root 60 Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-dbus-broker.service-3Mvje9 drwx------. 3 root root 60 Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-irqbalance.service-JzqOxF drwx------. 3 root root 60 Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-polkit.service-VD9khC drwx------. 3 root root 60 Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-systemd-logind.service-n1wbjJ drwx------. 2 root root 60 Apr 13 11:37 tde-root drwxr-xr-x. 3 root root 60 Apr 13 11:37 tdesocket-global drwx------. 2 root root 120 Apr 13 11:37 tdesocket-root -rw-r--r--. 1 root root 135 Apr 13 12:05 tmps.txt -r--r--r--. 1 root root 11 Apr 13 11:37 .X0-lock drwxrwxrwt. 2 root root 60 Apr 13 11:37 .X11-unix drwxrwxrwt. 2 root root 40 Apr 13 11:36 .XIM-unix
/var/tmp: total 28K drwx------. 3 root root 4.0K Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-chronyd.service-5fwrv9 drwx------. 3 root root 4.0K Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-dbus-broker.service-vCN4ts drwx------. 3 root root 4.0K Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-irqbalance.service-VA1jOT drwx------. 3 root root 4.0K Apr 13 11:37 systemd-private-74228c98e71245d6b6faba5e257aca1e-polkit.service-yKUPkD drwx------. 3 root root 4.0K Apr 13 11:36 systemd-private-74228c98e71245d6b6faba5e257aca1e-systemd-logind.service-szBEoE drwx------. 4 root root 4.0K Apr 12 19:32 tdecache-root drwxr-xr-x 2 root root 4.0K Apr 13 11:53 zypp.tmp #
Root TDE session works fine. This is my first use of SELinux. Could it be related? If not, what would? I see no suspects in dmesg or journal.
Sorry, forgot to say, give your user 'root' permissions just to test.
Mike Howard composed on 2026-04-14 08:14 (UTC+0100):
Felix Miata wrote:
Nothing useful from users send this last night, so perhaps someone here can help?
I just did an openSUSE Leap 16 installation on a new used PC with FM2+ AMD. Only IceWM was installed initially, then TDE, then Plasma. TDM is active DM. Plasma and IceWM sessions work normally, but for TDE for the only user, instead a popup:
Call to lnusertemp failed (temporary directories full?). Check your installation.
...
Root TDE session works fine. This is my first use of SELinux. Could it be related? If not, what would? I see no suspects in dmesg or journal.
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?
On 14/04/2026 12:27, Felix Miata via tde-devels wrote:
Mike Howard composed on 2026-04-14 08:14 (UTC+0100):
Felix Miata wrote:
Nothing useful from users send this last night, so perhaps someone here can help? I just did an openSUSE Leap 16 installation on a new used PC with FM2+ AMD. Only IceWM was installed initially, then TDE, then Plasma. TDM is active DM. Plasma and IceWM sessions work normally, but for TDE for the only user, instead a popup:
Call to lnusertemp failed (temporary directories full?). Check your installation.
...
Root TDE session works fine. This is my first use of SELinux. Could it be related? If not, what would? I see no suspects in dmesg or journal.
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?
Neither. Change the user ID to 0 (zero) in /etc/passwd. Temporarily of course.
On 14/04/2026 13:09, Mike Howard via tde-devels wrote:
On 14/04/2026 12:27, Felix Miata via tde-devels wrote:
Mike Howard composed on 2026-04-14 08:14 (UTC+0100):
Felix Miata wrote:
Nothing useful from users send this last night, so perhaps someone here can help? I just did an openSUSE Leap 16 installation on a new used PC with FM2+ AMD. Only IceWM was installed initially, then TDE, then Plasma. TDM is active DM. Plasma and IceWM sessions work normally, but for TDE for the only user, instead a popup:
Call to lnusertemp failed (temporary directories full?). Check your installation.
...
Root TDE session works fine. This is my first use of SELinux. Could it be related? If not, what would? I see no suspects in dmesg or journal.
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?
Neither. Change the user ID to 0 (zero) in /etc/passwd. Temporarily of course.
Yeah, I know, essentially becomes 'root' as opposed to being the same user with different permissions. Have you tried, as the problematic user, to create (touch) files in all the directories that TDE uses to set users up? Can you temporarily disable SELinux to rule that out?
Mike Howard composed on 2026-04-14 13:14 (UTC+0100):
Mike Howard wrote:
Felix Miata wrote:
Mike Howard composed on 2026-04-14 08:14 (UTC+0100):
Felix Miata wrote:
Nothing useful from users send this last night, so perhaps someone here can help? I just did an openSUSE Leap 16 installation on a new used PC with FM2+ AMD. Only IceWM was installed initially, then TDE, then Plasma. TDM is active DM. Plasma and IceWM sessions work normally, but for TDE for the only user, instead a popup:
Call to lnusertemp failed (temporary directories full?). Check your installation.
...
Root TDE session works fine. This is my first use of SELinux. Could it be related? If not, what would? I see no suspects in dmesg or journal.
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?
Neither. Change the user ID to 0 (zero) in /etc/passwd. Temporarily of course.
Yeah, I know, essentially becomes 'root' as opposed to being the same user with different permissions. Have you tried, as the problematic user, to create (touch) files in all the directories that TDE uses to set users up? Can you temporarily disable SELinux to rule that out?
Changing userID to 0 allowed TDE session startup, and created /etc/skel directories and more in /, and changed ownership of various files in user's homedir to root. Rebooting with selinux disabled, after fixing those permissions, TDE started up! :/ Rebooting with selinux enabled restored the issue. :(
Mike Howard composed on 2026-04-14 13:14 (UTC+0100):
Mike Howard wrote:
Felix Miata wrote:
Mike Howard composed on 2026-04-14 08:14 (UTC+0100):
Felix Miata wrote:
Nothing useful from users send this last night, so perhaps someone here can help? I just did an openSUSE Leap 16 installation on a new used PC with FM2+ AMD. Only IceWM was installed initially, then TDE, then Plasma. TDM is active DM. Plasma and IceWM sessions work normally, but for TDE for the only user, instead a popup:
Call to lnusertemp failed (temporary directories full?). Check your installation.
...
Root TDE session works fine. This is my first use of SELinux. Could it be related? If not, what would? I see no suspects in dmesg or journal.
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?
Neither. Change the user ID to 0 (zero) in /etc/passwd. Temporarily of course.
Yeah, I know, essentially becomes 'root' as opposed to being the same user with different permissions. Have you tried, as the problematic user, to create (touch) files in all the directories that TDE uses to set users up? Can you temporarily disable SELinux to rule that out?
Changing userID to 0 allowed TDE session startup, and created /etc/skel directories and more in /, and changed ownership of various files in user's homedir to root. Rebooting with selinux disabled, after fixing those permissions, TDE started up! :/ Rebooting with selinux enabled restored the issue. :( After sending this, time had elapsed and another message appeared:
THere was an error setting up inter-process communications for TDE. The message returned by the system was:
Could not read network connection list. /tmp/1278685534/.DCOPserver_ma78m_0 Please check that the 'dcopserver' program is running.
Nothing seems relevant in dmesg or journal. .xsession-errors is big, but susepaste keeps failing, thus it's attached.
On 14/04/2026 16:11, Felix Miata via tde-devels wrote:
<SNIP>
Nothing seems relevant in dmesg or journal. .xsession-errors is big, but susepaste keeps failing, thus it's attached.
Can the problematic user create '/tmp/tde-<username>' manually, without the userid modification?
I don't use SELinux, after trying it initially, many years ago.
Anno domini 2026 Tue, 14 Apr 11:11:04 -0400 Felix Miata via tde-devels scripsit:
Mike Howard composed on 2026-04-14 13:14 (UTC+0100):
Mike Howard wrote:
Felix Miata wrote:
Mike Howard composed on 2026-04-14 08:14 (UTC+0100):
Felix Miata wrote:
Nothing useful from users send this last night, so perhaps someone here can help? I just did an openSUSE Leap 16 installation on a new used PC with FM2+ AMD. Only IceWM was installed initially, then TDE, then Plasma. TDM is active DM. Plasma and IceWM sessions work normally, but for TDE for the only user, instead a popup:
Call to lnusertemp failed (temporary directories full?). Check your installation.
...
Root TDE session works fine. This is my first use of SELinux. Could it be related? If not, what would? I see no suspects in dmesg or journal.
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?
Neither. Change the user ID to 0 (zero) in /etc/passwd. Temporarily of course.
Yeah, I know, essentially becomes 'root' as opposed to being the same user with different permissions. Have you tried, as the problematic user, to create (touch) files in all the directories that TDE uses to set users up? Can you temporarily disable SELinux to rule that out?
Changing userID to 0 allowed TDE session startup, and created /etc/skel directories and more in /, and changed ownership of various files in user's homedir to root. Rebooting with selinux disabled, after fixing those permissions, TDE started up! :/ Rebooting with selinux enabled restored the issue. :( After sending this, time had elapsed and another message appeared:
THere was an error setting up inter-process communications for TDE. The message returned by the system was:
Could not read network connection list. /tmp/1278685534/.DCOPserver_ma78m_0 Please check that the 'dcopserver' program is running.
Nothing seems relevant in dmesg or journal. .xsession-errors is big, but susepaste keeps failing, thus it's attached.
This line looks suspiciouse to me: [KDE-ICE error] ICE default IO error handler doing an exit(), pid = 2195, errno = 11
Nik
On 4/14/26 11:58 AM, Dr. Nikolaus Klepp via tde-devels wrote:
Nothing seems relevant in dmesg or journal. .xsession-errors is big, but susepaste keeps failing, thus it's attached.
This line looks suspiciouse to me: [KDE-ICE error] ICE default IO error handler doing an exit(), pid = 2195, errno = 11
I may be wrong, I'm getting old, but I think that has to do with a mismatch in Xauthority permissions due to setting UID 0. Similar to what occurs if you use sudo or tdesu.
Old bug report about mismatch/permission issue with kdm login: https://bugs.kde.org/show_bug.cgi?id=90978
I still think selinux is your friendly culprit and in some way digging into openSUSE kdebase3-kdm-selinux and the /usr/share/selinux/packages/targeted/kdm3.pp file it provides probably sets the policies to let kdm/tdm work with selinux enabled.
I've run into so many issue with selinux it has been a frustrating mess. The immutable Leap filesystem should limit those, at the expense of being able to tweak the system without selinux complaining.
There are a couple selinux tools, e.g. semodule_unpackage and then dismod to unpackage and disassemble the openSUSE kdm3.pp file, see:
https://serverfault.com/questions/321301/how-do-i-view-the-contents-of-a-sel...
The joys of enterprise security applied to community distros.... I'll ultimately muddle through learning it, but it becomes every more difficult to teach and old dog new tricks :)
On 4/14/26 6:27 AM, Felix Miata via tde-devels 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 can try a global disable adding the kernel parameters:
security=selinux selinux=1 enforcing=0
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 :)
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.
On 4/14/26 6:51 PM, Felix Miata via tde-devels wrote:
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.
Felix,
You may also want to check with Yasuhiko, he has a selinux config for KDE3 that should be exactly what is needed for TDE. You could probably grab it (when I figure out which file and what app - likely kdm/tdm) and just do the old 's/kde/tde/g' swap....
Look at:
kdebase3-kdm-selinux-3.5.10.1-393.1.noarch
which provides:
/usr/share/selinux/packages/targeted/kdm3.pp
Felix Miata composed on 2026-04-14 19:51 (UTC-0400):
David C Rankin composed on 2026-04-14 18:05 (UTC-0500):
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.
It worked. I needed to put .autorelabel on both / and / of home filesystem and reboot.
-
David C Rankin -
Dr. Nikolaus Klepp -
Felix Miata -
Mike Howard