Hi, I’m new, so I will likely make some mistakes. I’ll take into account any feedback that you give me.
My question/issue: Whenever I am done with current KDE session, and want to power-off/restart, it is interrupted with what looks like a script that does not exit. This is in between ‘ending the desktop session’ and ‘returning to the login manager’ (SDDM). A simple keypress of ‘CTRL+C’ is sufficient to resume the action. When this happens, the text-mode screen is entirely empty or displays one or two stray chars, probably a stray keystroke that got picked up in the process.
Do you have any ideas what this could be, or hints of where I should look to find the root of this problem?
UPDATE (I could not find edit button) some info on the desktop installation to help provide context:
Desktop: SDDM, KDE, Wayland
Configuration: I followed the YaST security features to enable “secure file”, disable unnecessary services according to ‘Roaming’ (I mean, the name for the “traveling” profile), enabled SELinux.
Regarding applications: I cleaned up some desktop applications that I do not use, but the install is fresh – few days old – so there aren’t any exotic changes.
The issue did not exist from the start: the fresh install worked, but also started with X11 i.s.o. Wayland. I believe, somehow, the issue emerged after enabling “secure files” or SELinux. I am not sure exactly which setting caused it.
I could revert all kinds of changes, but I would like to troubleshoot if some support/hints are available, and hopefully fix it once and for all.
Quite likely… I obviously don’t know what you individual requirements are, but enabling those is probably way OTT for the “ordinary” user of a desktop / laptop workstation.
If you feel the need for that level of security then a read of the “Security and Hardening Guide”: Security and Hardening Guide | openSUSE Leap 15.5 would be advised first. (That document relates to Leap 15.4, but is equally applicable to TW)
Regarding disabling services, yes there are a few you probably could safely disable, but again exercise caution.
Thanks for the pointers. I do not know yet whether or not I need this. Honestly, I encountered it and activated it partly as a way to understand how OpenSUSE does things, what it provides, how things work, etc. However, the issue seemed sufficiently curious/out-of-place that it seemed better to discuss than to ignore and revert changes. I will definitely check out the hardening-guide. It seems to be quite extensive. I would have started with this had it gotten my attention. For disabling services, I simply followed the offered profile.
Tumbleweed has less documentation owing mainly to it’s evolving nature, but the guides for Leap 15.4 are mostly applicable.
When making changes to configurations, especially if you’re unsure or less familiar, don’t make too many at once, then if there are unintended consequences it’s far easier to back out of the changes. If you have specific questions by all means ask on the forums, you’ll nearly always receive a helpful reply from someone.
Yeah, it is. I guess it also depends on the use case. Given that a lot is new, experimenting is a great way to explore. For depth and when things have to be right, documentation and research is often more consistent and reliable. So, I appreciate the pointers. I don’t want to leave everything to chance.
It’s fine. I already assumed this was the situation.
Oh, reproduction is not the issue. I remember the changes I made and the order. I was hoping, maybe, for a hint to where these scripts could live to see if I can find the issue.
Actually, now I remember something: when I installed SELinux, with ‘selinux-targeted-setup’ last, the ‘.autorelabel’ file got created in ‘/etc/selinux/.autorelabel’. I had to move it to root (‘/’). This locked me out of the freshly installed system. I need to see where I can go to report this, if it is still needed. I corrected it manually, but the experience wasn’t quite optimal rotfl!
I don’t use either selinux or have secure file permissions set on any of my machines, so, if that is the cause, I’m not seeing the problem.
…This is in between ‘ending the desktop session’ and ‘returning to the login manager’ (SDDM). A simple keypress of ‘CTRL+C’ is sufficient to resume the action. …
Don’t know if this would provide anything useful, but if rather than resume with “ctrl-c”, first see if you’re able to switch to a VT (ctrl-alt-F2) and login as your normal user. If you are able, then prior to ending the desktop session switch to a VT and run “journalctl -f”. leave that running and switch back to the graphics terminal (ctrl-alt-f7), logout of the desktop session and switch back to the VT to see if anything interesting shows in the journal.
… I need to see where I can go to report this, if it is still needed. …
If you’re reasonably confident you have found a bug they can be reported at: https://bugzilla.opensuse.org/ (same login credentials as for this forum).
A very simple suggestion, and it works perfectly. Apparently, the desktop session does not have authorization as it checks with polkit. So it fails to issue the “system restart” and then waits.
I will have a look. I saw it in one of the main site’s menus, I think.
