I came from Arch to Void just today and after installing KDE and enabling dbus, I enabled SDDM, I type in my password and it says login failed, I tried lightdm, I couldn’t login neither in my user account nor root, I setup plasma to run with xinit, plasma did launch successfully, but sudo NEVER worked inside plasma, it always says “password incorrect, please try again” even though I’m able to sudo inside TTYs

I tried “sudo sddm” and read the logs, it says SDDM: authentication_FAILED for user “” which is weird (it didn’t print any names)

There were also some PAM logs in between, I didn’t change any PAM configuration

I have elogind installed and enabled too

  • Marcos Dione@en.osm.town
    link
    fedilink
    arrow-up
    6
    ·
    6 months ago

    @notTheCat there’s a technique where you boot with a live system, mount your linux system, chroot into it amd change passwords. If you think this is insecure for your system, then you should considering encrypting at least your home diretory/partition.

    • notTheCatOP
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      Yes everything in TTY works as intended, I can login as my user account and sudo works as it should

      • somethingsomethingidk@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        6 months ago

        That’s really weird. I set up a test system and I couldnt reproduce. The only thing I noticed errors flooding dmesg about elogind already running when I enabled it following the docs. I guess sddm is already starting it?

        I dont see how that would cause your issue though. I would probably just reinstall lol

        • notTheCatOP
          link
          fedilink
          arrow-up
          1
          ·
          6 months ago

          I’m starting to suspect my HDD failing at this point, so many weird bugs lately

  • 299792458ms@lemmy.zip
    link
    fedilink
    arrow-up
    3
    ·
    6 months ago

    I do not know how to solve your problem but I suggest posting to c/voidlinux or their subreddit which should have more people capable to help.

      • boredsquirrel@slrpnk.net
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        6 months ago

        Do you have polkit installed?

        Also does startplasma-wayland or how its called in the TTY work?

        Plasma on X11 is practically unmaintained afaik

        • notTheCatOP
          link
          fedilink
          arrow-up
          1
          ·
          6 months ago

          Yes I have polkit installed

          Executing startplasma-wayland returns the following:

          startplasmacompositor: Could not start D-Bus, Can you call qdbus?

          I don’t have an excutable/command named qdbus

          • boredsquirrel@slrpnk.net
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            6 months ago

            I never used Void and think it is meant for people that solve such issues themselves.

            I would recommend a distro where even manually installing KDE plasma packages will result in a “just working” Desktop, like Fedora.

            Otherwise, contact the Void people.

            I did a few minimal installs, currently working on a Qt6-only Wayland-only minimal install to test RAM consumption.

  • lemmyreader
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    Do have the startx command installed ? You can use that from the command line without DisplayManager (Switch to a virtual console with e.g. ctrl-alt-F2). And with XFCE4 you can use the command startxfce4 to start from the command line without DisplayManager. This could help troubleshoot.