https://bugs.kde.org/show_bug.cgi?id=481280
--- Comment #4 from Henrique <account+...@hfalmeida.com> --- (In reply to fanzhuyifan from comment #3) > (In reply to Henrique from comment #2) > > (In reply to fanzhuyifan from comment #1) > > > Thank you for your bug report! > > > > > > When your session freezes, would it be possible to switch to a virtual > > > terminal using Ctrl+Alt+F3 and see whether kwin_wayland is still using the > > > CPU? If so, could you attach a gdb instance to it and see where it is > > > stuck > > > at? > > > > > > Alternately, you could try ssh'ing into the machine when you encounter the > > > graphical freezes. > > > > Thank for your response. I couldn't move to another tty nor could i ssh from > > another device. > > > > I looked into the last boot's journalctl output with journalclt -b-1 and > > found an error that i thought could be related: > > > > fev 13 09:05:41 user systemsettings[4005]: Failed to load > > GeolocationProvider: > > "/usr/lib/qt6/plugins/plasma5support/geolocationprovider/plasma-geolocation- > > gps.so" "Could not load plugin from > > /usr/lib/qt6/plugins/plasma5support/geolocationprovider/plasma-geolocation- > > gps.so: Cannot load library > > /usr/lib/qt6/plugins/plasma5support/geolocationprovider/plasma-geolocation- > > gps.so: (libgps.so.30: não é possível abrir arquivo compartilhado: Arquivo > > ou diretório inexistente) > > fev 13 09:05:41 user systemsettings[4005]: "location" > > > > I then installed gpsd and it's now working properly. Seems like gpsd should > > be a dependency for plasma6? I checked /var/log/pacman.log and it doesn't > > seem like that package had been installed or uninstalled before so this must > > be a new thing. > > gpsd is already listed as an optional dependency for arch linux. I cannot > reproduce the freeze after uninstalling gpsd on Arch Linux with plasma > master build. hmm, interesting. Well, that's all the information i got and the issue is solved on my end after installing gpsd. Not sure what could be the difference between your setup and mine to cause. Anyway, as you can't reproduce it and it's solved here, the issue can be marked as resolved. Thank you @fanzhuyifan -- You are receiving this mail because: You are watching all bug changes.
