- Go to System Settings
- Click Splash Screen
[Stable Update] 2021-07-23 - Kernels, Nvidia, Mesa, Wine, Firefox, Thunderbird, Virtualbox
5 posts were split to a new topic: KDE Logo in splash screen instead of Manjaro after update
3 posts were split to a new topic: KDE Meta key doesn’t open menu after update
I have the same problem here. On Arch this is already reported as a bug.
The update went well at first glance, but my computer froze twice since I installed it. I had to shut it down by force each time.
seems there is a bug at Arch: FS#71541 : [telegram-desktop] telegram-desktop doesn't work after update to 2.8.11-1
I’m using KDE,cannot reproduce,telegram 184.108.40.206 works fine on my machine
Please read this:
Have you tried 5.10 LTS (Long Term Support) already?
telegram-desktop version 2.8.11-2.0 should fix the bug.
Same here in Manjaro XFCE. A temporary workaround it to launch it with
But this updates includes just that version (2.8.11-2), isn’t it? Also in the Arch bug track one comment says that it persists in 2.8.11-2.
I don’t know if you have more information on the issue, but it seems to me that it is not fixed for everybody in this version?
PS: Mine works fine.
Edit: I can confirm from a friend that the problem persists with 2.8.11-2. (XFCE)
For KDE users who wish to re-apply their preferred login splash screen:
- Backup / remove the old ksplashrc file:
mv ~/.config/ksplashrc ~/.config/ksplashrc.bak
- Go to System Settings
- Type in
- Click on Splash Screen
- Select and Apply your desired splash screen
Mostly working but I did have a Bluetooth issue. I could not pair with any of my Bluetooth devices after the upgarde. Deleting the paired devices and pairing again seems to have worked. No idea what that was about.
good morning everyone…thanks for the information…glad it works on kde(years ago my desktop)but i am on xfce…
it doesn’t matter…it works with the version downloaded from telegram website(2.8.10)
Greetings and a hug
Sorry, I don’t understand. That’s my point precisely. This update includes already the updated package, but some people still have problems.
The update initially came with 2.8.11-2, which is buggy.
It was later updated to 2.8.11-2.0, which does not anymore have the bug (I can confirm it).
The patched version has not reached all the mirrors yet.
Ahhh, ok. Now I understand. Thanks! It didn’t occur to me that 2.8.11-2 and 2.8.11-2.0 were different
Not an issue but after
pacman -Syu , it is showing warning:
warning: inxi: local (3.3.06.1-1) is newer than community (3.3.05.1-1)
10 posts were split to a new topic: How to manage a Rolling release from a user perspective