After fresh install KDE freezes and can't use any sudo commands

siiparch · 2022-08-27 09:43:27

I am facing a strange problem while using Arch.

While using the computer, after a few minutes after powering on, normally when I browse the internet, my browser stops responding, the entire Desktop Environment (KDE) becomes unusable, I cannot start the application launcher, I cannot access the context menu with right click, I can only start the terminal via shortcut, but from the terminal itself I can only execute commands that do not involve the use of "sudo", all other commands, which do involve the use of sudo, give me no output, and the terminal itself appears freezed.

I cannot even close applications that I had previously opened, through the GUI, I can, however, access htop and try to close processes, but they will not close
I also tried to close using the "kill" command, but as mentioned above, I cannot use any command that requires super user privileges.

I would like to point out that:
I use Arch in dual boot with Windows, but the same problem occurs even when I only have Arch installed.

The problem occurs post fresh install, an installation I normally perform with "archinstall".

Rarely, after a few minutes the pc comes back to work, only to run into the same problem again after a while.

Whenever it happens I find myself forced to turn off the PC using the appropriate button on the case.

Normally, I really like to try to fiddle around in order to solve problems, also because I very often end up learning new things, but in this case I just don't know where to start.

seth · 2022-08-27 12:32:29

I use Arch in dual boot with Windows, but the same problem occurs even when I only have Arch installed.

See the 3rd link below and post the outputs of

hostnamectl
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

siiparch · 2022-08-27 12:59:29

Thanks for taking time to answer!

I've disabled secure boot and fastboot before installing arch

This is the Output

dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service | system
dirmngr.socket | sockets.target.wants
display-manager.service | system
fstrim.timer | timers.target.wants
gcr-ssh-agent.socket | sockets.target.wants
getty@tty1.service | getty.target.wants
gpg-agent-browser.socket | sockets.target.wants
gpg-agent-extra.socket | sockets.target.wants
gpg-agent.socket | sockets.target.wants
gpg-agent-ssh.socket | sockets.target.wants
NetworkManager.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
p11-kit-server.socket | sockets.target.wants
pipewire-pulse.socket | sockets.target.wants
pipewire-session-manager.service | user
pipewire.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
systemd-timesyncd.service | sysinit.target.wants
wireplumber.service | pipewire.service.wants
xdg-user-dirs-update.service | default.target.wants

However, I noticed that the sudo command "hang" when internet stopped working. And this happened every 10 minutes after boot, isolating the problem to just the internet not working a few minutes after boot, I found a number of solutions online, one of which recommended removing the "wpa_supplicant" package, due to a problem related to my specific wireless network adapter.

Since I use only and exclusively an ethernet connection, I removed it, and the problem seems to have been solved. Internet is still working after 2 hours.

seth · 2022-08-27 13:14:39

I've disabled secure boot and fastboot before installing arch

Windows fast-start has nothing to do with your BIOS/UEFI settings, pelase read the article.

This is the Output

Please use "code" tags, not "quote" tags.
Also "hostnamectl" is missing.

I found a number of solutions online

Maybe we first figure what the problem actually is before we follow random advise by random dudes on the interwebs…

Internet is still working after 2 hours.

isn't so super-likely to cause the issues you described, but if you want to know what problems may or not exist around your wifi, we'll also need a relevant system journal ("sudo journalctl -b -1" for the previous boot. Don't copy and paste that out of the pager, but see the tip in the 1st link below)

siiparch · 2022-08-27 14:02:34

Thanks again for your answer
And sorry for being dumb and didn't read the article.
I've disabled windows fast startup.

This is the correct command output

Static hostname: archlinux
       Icon name: computer
      Machine ID: db0fca3dd79a44958adc51e940d72b95
         Boot ID: 0627fe2c506445feaeac107ff339d1df
Operating System: Arch Linux                        
          Kernel: Linux 5.19.4-arch1-1
    Architecture: x86-64
 Hardware Vendor: Micro-Star International Co., Ltd.
  Hardware Model: MS-7C75
Firmware Version: 2.E0
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
fstrim.timer                             | timers.target.wants
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

This should be the output of the last command http://0x0.st/o9hN.txt

seth · 2022-08-27 14:30:10

You've a static hostname, so it's not a domain loss.
And there're certainly ath9k issues. The backtraces would match https://bbs.archlinux.org/viewtopic.php … 5#p2039965 so maybe https://bbs.archlinux.org/viewtopic.php … 8#p2038348 (but that's not confirmed)

sudo is NSS sensitive, so that can be due to random network issues, but I'm not sure about the other symptoms, nor about whther that's reflected in the journal because of

Whenever it happens I find myself forced to turn off the PC using the appropriate button on the case.

If this flares up again (despite having the wifi chip disabled, frankly rather blacklist ath9k or disable wifi connections on that device in the NM settings) make sure to use https://wiki.archlinux.org/title/Keyboa … el_(SysRq) instead.

Arch Linux

#1 2022-08-27 09:43:27

After fresh install KDE freezes and can't use any sudo commands

#2 2022-08-27 12:32:29

Re: After fresh install KDE freezes and can't use any sudo commands

#3 2022-08-27 12:59:29

Re: After fresh install KDE freezes and can't use any sudo commands

#4 2022-08-27 13:14:39

Re: After fresh install KDE freezes and can't use any sudo commands

#5 2022-08-27 14:02:34

Re: After fresh install KDE freezes and can't use any sudo commands

#6 2022-08-27 14:30:10

Re: After fresh install KDE freezes and can't use any sudo commands

Board footer