It’s probably uwsm. A faulty update got pushed. Start Hyprland without uwsm or downgrade to the prior version until the fix is rolled out. Ran into that today too.
this post was submitted on 12 Aug 2025
13 points (93.3% liked)
Linux
57255 readers
840 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
Log in on the console Ctrl + Alt + f3 for example, then put in your username and password. This bypasses GDM and hyprland and drops you in on the console.
There you have then access to your whole computer and can check the logs for error messages, you can try to just run pacman again perhaps that fixes something, and you can also move your dotfiles somewhere else to check if they cause the problem.
Everything looks pretty normal to me.
pacman is working, I have no errors. I did what you said. Logged in the console (tty) (Arch Linux 6.15.9-arch1-1) and everything looks pretty normal, no errors or anything else.
sudo systemctl status shows you what services are running, sudo systemctl list-units lists everything, including the services that failed. sudo systemctl status gdm.service shows you the status of one service in particular, and sudo journalctl -u gdm.service shows the output/logs of that service.
There's a decent chance something is not starting due to misconfiguration. I'm guessing GDM based on previous comments. You can also check /var/log/pacman.log (make sure to save a copy, just in case), to see what packages changed/updated.
If you think it's a pacman issue somehow, you can reinstall your entire system (excluding AUR or self-made PKGBUILDs). Note that this is almost never required to fix an issue. In a properly working system this "shouldn't harm anything", but nothing can be guaranteed on a broken system. The command for that is sudo pacman -S $(pacman -Qqn)
Did a quick view into their installer. They use some AUR parts. Upgrading only with pacman seems not useful. Better use yay -Syu (or paru -Syu) it will upgrade both AUR and pacman. Since others recommended, get a tty and run HyDE installscript again.
Ctrl-alt-Fnumber until you get to a tty shell. Login, run journalctl - f. Ctrl-alt-Fnumber until you get back to login screen, and login. Go back to tty and see what errors got logged.
If you have ssh enabled you can also ssh in and run the journalctl cmd. You'll have to try different F number keys, I dont remember which ones get you a tty and which gets you the login. Start at F1 and move across, but wait a bit, sometimes it can take a while to spawn the TTY.