The cause is Arch updating the package from Qt 5 to Qt 6: [telegram-desktop 3.4.2-2: Build against Qt6]
This leads to read message ticks, stickers, etc being pixelized. The issue on Telegram Desktop official repo states that it’s not solvable on Qt 6 at the moment: [search for QT6 fractional scaling in new versions results in pixilated images on linux]
Solution: install the official binary package from Telegram, for example, from AUR. That is built against Qt 5, I guess. pamac build telegram-desktop-bin
(Don’t worry, it will pick your user profile and settings, no manual actions were required for me)
The Super-key does not open the “application launcher” anymore.
Workaround 1: Set the keyboard shortcut to “Super+Y” or something else like “Super + -”. Then the “application launcher” can be launched with “Super” or “Super+Y”.
Workaround 2: Use Alt+Space
The keyboard shortcuts of the “Entries” of “Status and Notifications” are resetted after a reboot. I like to enable/disable “Night Colour” with “Super+Strg+K” or open the “Notifications” with “Super+Strg+N”.
EDIT: Seems to be a KDE bug. After I setup the keyboard shortcut for the second entry (e.g. “Night Colour”), the keyboard shortcut for the first entry (e.g. “Notifications”) is deleted. Although the shortcut for “Notification” is removed in the GUI, it still works until I reboot my computer.
How can I debug this issue? I skimmed “journalctl -b” and saw nothing special (except that I have EXT4 errors that I’m fixing now).
I’d heard about kernel 5.16 has some better gaming perfomance. So, I’ve installed and switched my kernel from 5.14 to 5.16 and get issue with my xbox 360 gamepad. It was connected and detected in the system settings(I use KDE edition), plus in Steam the same, BUT there wasn’t any input events from my gamepad. And when I tried to see an error with xboxdrv(I have xboxdrv installed, but don’t use it of most time. Gamepad works natively) by the line:
The only apparent potential problem was that a message flashed past saying something about GRUB might fail to boot and something about secure boot (I think).
However, GRUB did boot, so I’m happy. Though I assume this might be a problem for some users.
after updating i didn’t have DSL ethernet connection even though it showed as connected.
a second reboot fixed it.
I’ll see what happens after a shutdown.
I tried that several times with several versions of systemd installed and updating after the user creation. It just didn’t work with an mdraid RAID1 disk as the storage. I can get the storage mounted by running manually
cryptsetup open /dev/md/home home-username
mount /dev/mapper/home-username /home/username -o subvolid=username
but systemd-homed/systemd-homeworkd which ever portion was responsible for doing that kept failing.
For some reason, my system failed to import all my zfs pools after reboot (I installed Manjaro on zfs). It said “pool was previously in use from another system”. I need to use
zpool import -f POOLNAME
for all my zfs pools and then reboot again in the rootfs prompt. It seems normal now.