• pastermil@sh.itjust.works
    link
    fedilink
    arrow-up
    7
    ·
    5 months ago

    That might be the problem with DE integration. I’ve been using KDE, and I’ve only had to deal with a single interface for setting wifi connection.

    • swab148@startrek.website
      link
      fedilink
      arrow-up
      4
      arrow-down
      2
      ·
      5 months ago

      NetworkManager is still shite on KDE, I’ve had to change the backend to iwd and download a new DHCP client just this week.

        • swab148@startrek.website
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          5 months ago

          I think it’s just that the defaults for NetworkManager don’t play nice with systemd, wpa_supplicant would take several minutes to connect to my wifi, and dhcpd just dropped my connection after I rebooted the router (for unrelated purposes) and would reconnect for about a minute before it dropped it again.

          I’ve still been having an issue where if I reboot the computer, NetworkManager will hang up the boot process indefinitely, but this doesn’t happen if I shut it down and then turn it back on with the power button. Still haven’t figured that one out, all of my research said that this issue was supposed to have been fixed with the last update, but not for me I guess!

          • pastermil@sh.itjust.works
            link
            fedilink
            arrow-up
            2
            ·
            5 months ago

            Yeah, it’s known to not play nice with dhcpcd. I’ve been using nm’s built-in dhcp client. Otherwise dhclient’s been known to work. Not sure about the wpa_supplicant part as it never cause me any issue by itself.