I installed LXDM and LightDM, I couldn’t login from the DM in either cases, so I decided to run LXQt using startx which worked, except I couldn’t sudo from the terminal emulator inside LXQt, while I was able to sudo normally in tty, I’ve tried enabling elogind, nothing changed, my user is in the wheel group and my system is up to date

  • atzanteol@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    4 days ago

    What does “doesn’t allow sudo” mean? Did you get an error that provided a reason? What exactly did you do?

      • atzanteol@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        3 days ago

        But what does. Be specific. Are you prompted on the CLI or is there a pop-up window that you’re entering credentials into?

  • Estebiu@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    2
    ·
    4 days ago

    I dont use neither void and neither x11, but that seems like a common thing that should be mentioned in the docs? i think

        • lonesomeCat@lemmy.mlOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 days ago

          I’ve tried

          exec dbus-run-session -- startlxqt

          Nothing changed

          I also tried

          exec lxqt-session

          It ran a broken session with no panel, I tried to sudo from there but it also said incorrect password

  • Lantern@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    4 days ago

    What shell are you running in your terminal? If I’m remembering correctly, it’s recommended to set the shells during the installation, so that could be the issue here.

    • lonesomeCat@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      Both bash and fish are returning incorrect password upon trying to execute any command with sudo

      • Lantern@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        3 days ago

        Interesting, could also be the tty. If it’s causing you a lot of trouble, you might want to just reinstall.

          • Lantern@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            2 days ago

            I generally find this to be the easiest option if my system is giving me issues. Void took me a few installs before getting the right combination of packages and services running. It’s definitely my favorite distro so far, considering that it provides stability while remaining on a rolling release cycle.

            As to your controller, look into the xpadneo or xone packages. Both are available on Void. Not certain they’ll work with PlayStation controllers, but I wasn’t able to find any packages dedicated to them.

            • lonesomeCat@lemmy.mlOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              19 hours ago

              Nope, xone ain’t doing it, it’s an Xbox series controller, but it could be related to my laptop hardware being extremely outdated idk, I should’ve tried it on a different distros, it works ootb on different machines running Arch and Pop

              • Lantern@lemmy.world
                link
                fedilink
                arrow-up
                1
                ·
                5 minutes ago

                If you haven’t already, try using a wired connection. That should remove the primary difference between xbox one and series controllers. I’d also suggest using a tool like antimicrox to see if you’re receiving input from the controller. You may also want to look into what solutions other distros use for Bluetooth, as the answer could be buried in there.