swhkd icon indicating copy to clipboard operation
swhkd copied to clipboard

install guide turns off NetworkManager wifi

Open erickthesublime opened this issue 1 year ago • 3 comments

Version Information: $ linux-lts is being used I think

  • Distribution Information ( run uname -a ) Linux archlinux 6.6.46-1-lts #1 SMP PREEMPT_DYNAMIC Wed, 14 Aug 2024 15:21:14 +0000 x86_64 GNU/Linux
  • swhkd version ( swhkd -V ) Simple-Wayland-HotKey-Daemon 1.3.0-dev

Describe the bug: tldr: pkexec swhkd causes "NetworkManager $nmcli general" to show "Wifi: Disabled" and errors

background: During installtion, I ran into a few error after doing make setup, which I ignored, then I did make clean, which cleaned 0 files, then doing make resulted in another error that chat GPT said was due to me missing "pkgconf" which I then proceeded to use pacman to reinput "make" which I think gave me two warnings at the end but overall seemed successful.

main issue: pkexec swhkd errors and turns off my wifi in nmcli aka "NetworkManager"

Expected behavior: to be able to config swhkd and use hotkeys

Actual behavior: the last step of the install procedure results in error and my wifi being turned off

To Reproduce: $ pkexec swhkd

Additional information: [horizon@archlinux ~]$ pkexec swhkd [2024-08-18T17:25:14Z WARN swhkd::environ] XDG_CONFIG_HOME not found, using hardcoded /etc [2024-08-18T17:25:14Z WARN swhkd::environ] XDG_RUNTIME_DIR not found, using hardcoded /run/user [2024-08-18T17:25:14Z WARN swhkd::environ] XDG_RUNTIME_DIR not found, using hardcoded /run/user [2024-08-18T17:25:14Z WARN swhkd] Running swhkd as root! [2024-08-18T17:25:15Z ERROR swhkd] Could not open evdev device at /dev/input/mouse3: Inappropriate ioctl for device (os error 25) :^H^C[2024-08-18T17:25:29Z WARN swhkd] Received SIGINT signal, exiting...

erickthesublime avatar Aug 18 '24 17:08 erickthesublime

+1 happens to me

erickthesublime avatar Aug 31 '24 18:08 erickthesublime

also happens to me

distbit0 avatar Dec 18 '24 08:12 distbit0

Yes, this is a known issue, pr #254 will hopefully fix this soon. till then you can use release 1.21(or some not so old commit) which does not seem have this problem

manthanabc avatar Dec 19 '24 17:12 manthanabc