Telegram desktop works without a hitch here on Plasma 6 and this thread here has no solution, so sorry to ask, but have you tried:
If yes, post a new issue here as the Telegram guys will be able to help you better than us…
No issues here. Smooth update.
Which telegram package do you have installed? telegram-desktop from the repos is the one I’m using, with no issues. The AUR packages have issues sometimes.
qBittorrent from Official Repositories Extra stopped working after update.
I uninstalled it and installed the one from Flatpak. But I have to configure everything again, 
How do I remove widgets? I can no longer find a way to do it after this update.
The icons for Notification, Clipboard Contents, and Screen Brightness are also missing. These widgets shows up as a rectangular icon with a question mark in the middle.
I also used to use Latte dock and now it is unresponsive.
Well I went ahead and took the plunge
I followed the instructions in the wiki post to avoid problems, doing timeshift + resetting plasma to defaults. A mild inconvenience, but I didn’t have a lot of customizations anyway… so no big deal
Everything went smoothly. Thank you manjaro team, and whoever contributed to that community post!
EDIT: just updated my laptop as well, which is using wayland, all good!
If your issue is qBittorrent no longer starting and you have hidden startup configured take a look at this:
Changing StartUpWindowState=Hidden to StartUpWindowState=Minimized lets qBt start again and will result in the same behaviour - if you also have minimize to tray configured.
Assuming you are talking of the Plasma desktop environment, right-click the panel and choose “Edit Mode”. You can then hover the mouse over the widgets on the panel and choose “Remove” from the popups.
Choose a different icon theme. The one you’re currently using is no longer compatible.
latte-dock and its various widgets are not compatible with Plasma 6 and qt6. You should remove them.
I always install telegram from the official website
Unpack and open the console in the Downloads folder
sudo mv Telegram /opt/telegram
sudo ln -sf /opt/telegram/Telegram /usr/bin/telegram
There are never any problems))
Hi, the last major update to Qt6 on 2024-05-13 and the minor update on 2024-05-18 went smoothly for me. However, I noticed a small issue with the power saving settings under KDE on several PCs. Maybe someone can confirm this or there is already a solution?
The language of the settings is currently a bit mixed (English and German), although according to the settings manager, all necessary DE language packages are installed (including qt6-translations).
My problem concerns the new power saving settings, specifically the “When locked, turn off screen” setting. This time is entered in seconds. Previously, I had it set so that the screen lock activated after 20 minutes with a slideshow, and the screen turned off after another 240 minutes. With the new setting, this no longer works because the screen turns off after 60 seconds. Entering 14400 seconds is not possible.
Either I don’t understand the connection between “Bildschirm ausschalten” (turn off screen) and “When locked, turn off screen,” or it’s a small bug.
Here is my KDE wayland system:
$ neofetch
██████████████████ ████████ jo@jo-z690
██████████████████ ████████ ----------
██████████████████ ████████ OS: Manjaro Linux x86_64
██████████████████ ████████ Host: Z690 Phantom Gaming-ITX/TB4
████████ ████████ Kernel: 6.6.30-2-MANJARO
████████ ████████ ████████ Uptime: 34 mins
████████ ████████ ████████ Packages: 1684 (pacman), 11 (flatpak)
████████ ████████ ████████ Shell: bash 5.2.26
████████ ████████ ████████ Resolution: 3840x2160
████████ ████████ ████████ DE: Plasma 6.0.4
████████ ████████ ████████ WM: kwin
████████ ████████ ████████ Theme: Default [GTK2/3]
████████ ████████ ████████ Icons: breeze [GTK2/3]
████████ ████████ ████████ Terminal: konsole
CPU: 13th Gen Intel i7-13700T (24) @ 1.400GHz
GPU: Intel Raptor Lake-S GT1 [UHD Graphics 770]
Memory: 3407MiB / 64063MiB
$ lsb_release -a
LSB Version: n/a
Distributor ID: ManjaroLinux
Description: Manjaro Linux
Release: 24.0.0
Codename: Wynsdey
Has anyone had similar experiences or knows a solution?
Thanks in advance!
/usr/bin is for executables that are part of your system and handled by your package manager. If you’re going to install any third-party software in binary form, then it should stay confined to /opt, and then you should add the pertinent directory to your user’s $PATH. And if you want to use a symlink instead, then put it in /usr/local/bin.
It had me confused as well at first, but it’s actually quite logical.
The first setting is for powering down the monitor after a period of inactivity. For instance, I have my screen locker come on automatically after 90 minutes, and then if I don’t unlock it again within 10 minutes, the monitor will switch off at the 100-minute mark.
The second setting — in seconds — is how much time must elapse after the screen gets locked before it powers down the monitor, but — and here’s the clue — this also applies if you manually lock the screen. So if you lock the screen and walk away from the computer, then after that timeout it’ll switch off the monitor, as opposed to waiting for the first timeout if you didn’t manually lock the screen.
@Aragorn Thank you for your feedback!
My goal is to automatically lock the screen and start the slideshow after 20 minutes, similar to a screensaver as was common with CRT monitors in the past. Due to the setting “When locked, turn off screen”, the screen will automatically turn off after the set time elapses, consequently ending the slideshow as well. I was able to enter 14400 seconds now and hope that this meets my requirements.
OK.
So as usual I delayed the previous updates to see if anything pops up in the Forum thread. So this one came as quite a surprise. So it madee me realize that it’s probably TimeTM.
So with the recommendation to update from a TTY in mind, and having made a Timeshift snapshot and having it ready. I deecided to do a little experiment: Update from the Terminal emulator in KDE itself. While doing things as normal. So I went ahead and ran:
pamac upgrade --no-aur
It downloaded ±4GB and installed successfully. So then I decided to just delete the cache directory for giggles’ sake:
rm -rf ~/.cache
And I couldn’t think of anything else to do, so I restarted.
Upon eventually restarting, my SDDM login theme didn’t work, spelling Trouble for me. Long story short, I changed it back to Breeze after remembering I had it hard-coded in a drop-in config file for some reason or the other, and rebooted again.
It worked! So now to check out everything. Well, my launcher was no long er working, sadly. Not a train smash as I simply reverted from Excalibur Launcher to the default Application launcher.
Apart from a couple of, if not all (I haven’t tested yet) Window rules not applying, everything seems to be working. (In X11, will test with Wayland later.) Even the window rules, it’s not as if they’re not working at all, for some reason that I don’t get yet the rules themselves work, they’re just not applying to the windows. I just had to re-select the windows.
So I’m seriously, extremely, very impressed. And a bit disappointed. I think. I mean, I set out the day for this…but either way. kudos to both the team at Manjaro as well as the KDE developers
I’ll now rebuild my AUR packages, but I don’t expect any issues since it has been smooth sailing so far.
OH! I found out my Event calendar extensio0n is no longer working. But already replaced that, so it’s all good!
This is it. Thanks, I wasn’t aware of that problem
Pycharm multi-process debugging is broken with python-312 [1]
Rolled pycharm back to 2023.3.5-2 and everything seems to be fine…
[1] https://youtrack.jetbrains.com/issue/PY-72009
Edit: You still need to disable the low-impact debugging or else watch functionality will take forever. [2]
[2] https://youtrack.jetbrains.com/issue/PY-72345/Pycharm-2024.1-Broken-debug-on-Python-3.12.3#focus=Comments-27-9782099.0-0
Hello, my wife has an old laptop that I upgraded to a Manjaro with plasma 5 so the last 23. I would like to switch to the 24 but keeping plasma 5 and not plasma 6, does anyone have a solution to stay on kde plasma 5.
Thanks in advance
Not possible … not the answer you hoped for - but that is how it is 
ok thanks for the quick response.
for all folks using nvidia/x11 after this update.
i encountered a heavy workload and cpu-usage and stuttering video after the update. the reason is that this update installs the package for hardware acceleration of the gpu that isn’t helpfull
libva-vdpau-driver-wayland 0.7.4-1
installing the package
libva-vdpau-driver
solves the problem due to it was missing. cpu-workload decreases dramatically and stuttering of video-streams is gone plus thermals reduce significant.
I followed the instructions in the wiki post
Can you please post the link to the wiki you are mentioning there?
He means the second post in this and the topic from 13.5. (Known Issues) i guess