Results 1 to 7 of 7

Thread: kde boot fails after interrupted ZYPPER DUP command

  1. #1

    Default kde boot fails after interrupted ZYPPER DUP command

    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.

    HTML Code:
    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.

    Any help would be gladly appreciated.

    Thanks,
    Chuck Haatvedt (learning linux)

    Opensuse Tumbleweed / Windows 10 dual boot
    Opensuse Tumbleweed in VMWARE Player

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    13,310
    Blog Entries
    3

    Default Re: kde boot fails after interrupted ZYPPER DUP command

    Login to a different desktop environment.

    Create a new user account.

    Test whether plasma works for the new user account.

    If it works for a new user, then the problem is with saved user settings rather than what is installed. The idea is to test that.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  3. #3

    Default Re: kde boot fails after interrupted ZYPPER DUP command

    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 ?
    Chuck Haatvedt (learning linux)

    Opensuse Tumbleweed / Windows 10 dual boot
    Opensuse Tumbleweed in VMWARE Player

  4. #4
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,947
    Blog Entries
    1

    Default Re: kde boot fails after interrupted ZYPPER DUP command

    Something like the following might be sufficient...

    Code:
    mv ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/.config/plasma-org.kde.plasma.desktop-appletsrc-old
    * Do this while logged in as the appropriate user in the working DE, then log out and try starting a KDE session again.

  5. #5
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,424
    Blog Entries
    14

    Default Re: kde boot fails after interrupted ZYPPER DUP command

    Also, if you have been messing around with resolutions:
    Code:
    rm -rf ~/.local/share/kscreen
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  6. #6

    Default Re: kde boot fails after interrupted ZYPPER DUP command

    i logged into a different user and by using Dolphin in superuser mode, I renamed this file in my problematic user spcwh2, to add -old to the name

    ~/.config/plasma-org.kde.plasma.desktop-appletsrc

    renamed to ~/.config/plasma-org.kde.plasma.desktop-appletsrc-old

    I also did the same with this file as well

    ~/.config/plasma-org.kde.plasma.desktop-appletsrc.lock

    renamed to ~/.config/plasma-org.kde.plasma.desktop-appletsrc.lock-old


    I then logged out and attempted to logon with my spcwh2 user with plasma and the result was the same. i could not enter plasma.

    I then repeated the process to rename .local/kscreen to .local/kscreen-old

    i then logged out and attempted logging on with my spcwh2 user and the result was the same.
    I could not enter plasma.
    Chuck Haatvedt (learning linux)

    Opensuse Tumbleweed / Windows 10 dual boot
    Opensuse Tumbleweed in VMWARE Player

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,947
    Blog Entries
    1

    Default Re: kde boot fails after interrupted ZYPPER DUP command

    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.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •