Announcement

Collapse
No announcement yet.

After plasma 7 update, impossible to get graphic display -- sddm or plasmaahell?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    After plasma 7 update, impossible to get graphic display -- sddm or plasmaahell?

    I updated this morning and plasma 7 was installed. But when I boot, I just get a tty login invite. I can login, but can't do anything afterwards. I can't launch plasmashell and it knows no command kwin.

    During the update, it asked if I wanted plasmashell or sddm. Not having any idea what that means, I selected the default, which was sddm. What is sddm? Could that be my pb

    Thanks in advance for any help.
    'I must have a prodigious quantity of mind; it takes me as much as a week sometimes to make it up.' Mark Twain

    #2
    Originally posted by joneall View Post
    it asked if I wanted plasmashell or sddm
    That was to select the desired login manager, SDDM or Plasmalogin, as Plasmalogin is now installed by default.

    SDDM is the login manager favored by KDE for some years now

    Plasmalogin is its replacement. It is actully based on SDDM, so it will have the same sort of look at the moment.

    It is fine to use SDDM, but if you do any package cleanup, it will be removed, so you will end op on Plasmalogin anyway.

    As to the upgrade to Plasma 6.7 , I do not know what might be causing your problem. Mine was fine, other than a notification for 2 phantom, non-existant updates that showed in Discover, that went away after a while. (Nope, they are still there)

    The command to start Plasma from a tty login will be startplasma-wayland, or startplasma-x11 if you use that.

    You might check for updates if you can, maybe you did not get all of them?
    Self-built: Asus PRIME B550M-K/Ryzen 5600GT/32Gb/Intel ARC B580 12Gb/KDE neon
    HP Elitedesk 800 G3 Mini: i5-7500T(35w)/32Gb/Kubuntu LTS
    HP Chromebook 14: i5-1135G7/8Gb/512Gb SSD/KDE Linux

    Comment


      #3
      I had the same issue with my machine. I was able to get it running again. After a login I could start plasma with:
      Code:
      exec /usr/bin/dbus-launch --exit-with-session startplasma-wayland
      After I had that running I reeinstalled plasmalogin:
      Code:
      sudo apt install --reinstall plasmalogin
      and reloaded the service:
      Code:
      sudo systemctl daemon-reload

      Comment

      Users Viewing This Topic

      Collapse

      There are 0 users viewing this topic.

      Working...
      X