I was attempting to do a distribution update on my Tumbleweed system. It is a dual boot sytem with Windows 10 as the other boot option. During the installation portion of the update it hung and would not progress. I tried to kill it with Ctrl-C and after multiple attempts it did stop. I was then able to repeat the zypper dup command but it hung again a bit later. After multiple iterations, it finally completed.
However after that when booting in Plasma, the boot appeared to complete but the mouse would move but any mouse click would do nothing and the only response to the keyboard was when i entered Ctrl-Alt-F1. Then i was able to logon as root and issue a shutdown now command but the system looped thru "a stop job is running for session 2 " . Eventually it got past the stop jobs and fell into an endless displays as follows
systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
The only way out of this was to use the power reset button. After rebooting and logging on with the LXQT desktop, I ran the “journalctl -b -1 -n 8400” command run as root as pasted the output here.
URL: http://susepaste.org/3063090
Interesting is that I can use any of the other Desktop Top environments without issue, but not Plasma. Sometimes when I try to boot into Plasma the graphical interface will not even start.
Is there any option to fix my Plasma DE, or is my best option to reinstall Tumbleweed. I would like to avoid that if possible.
I was able to create a new user using a different DE. Then I rebooted and logged on to Plasma with the new user and it was successful. I could navigate and use Plasma with that user.
So now the question is how can i fix my regular user to allow it to use Plasma ?
Well it might just be easiest to migrate any important user data to a new working account. Delete the old non-working account and rename the new user as required. The alternative is to track down the offending config file(s), but that may be too tedious for you.