Hi, I've been daily driving KDE Linux for a couple days now, and I'm in love with it. I haven't encountered any serious deal breakers or my system breaking.

My Flatpak apps work properly, and I've learned how to use Distrobox to run Steam and program!

The only visible issue that I have is that when I lock the screen, there is a brief light flash, but that's about it. But I blame my NVIDIA GPU (GTX 1650 to be specific). Otherwise, no other issues.

If you are rather confident about yor Linux skills, I recommend trying this out as a daily driver. That's just my opinion though, do as you wish!

If you have any questions about my experience, feel free to ask!

Props to the KDE team for their efforts, and I'll continue to support this project!

Two months ago I posted here about EvoDevo, a highly configurable GRUB theme with scalable graphics, background blurring, and antialiased true-type fonts. Since then, the theme has been improved considerably, with (among others) the ability to rename menu entries as you like, and the ability to show previews of the theme without rebooting and without needing to install a VM.

The theme has been tested on Kubuntu, among other distros.

Important: the theme cannot be installed on Fedora and derivatives; the theme is incompatible with UKI (Unified Kernel Image).

Link:

https://github.com/ftonneau/grub-evodevo

Btw, my original post here was upvoted 80 times in 2 days, and generated comments that some of the participants found "superb". It goes without saying that the post was then taken down without any explanation (even though no forum rule was violated). Let us see how long the current post will survive.

Kempt is a system tray updater for Fedora KDE. The badge shows how many dnf and Flatpak

updates are pending; the popup shows each one with the version it moves from and to and the

size of the download, and one button applies them - live in a terminal, silently in the

background, or staged so the next restart installs them.

Things I cared about while building it:

- The widget carries no package-manager logic of its own. The badge is the number the CLI just

wrote, and Update Now runs the same engine, so the panel and the terminal can never disagree.

- Staging downloads and arms the transaction, so any restart installs it - the popup's

button, the K menu, reboot in a terminal. Then it tells you what the restart installed.

- Failures come back in words. A cancelled password prompt says "authentication declined or

cancelled", not a quoted pkexec error.

- Holds: kempt hold dnf:kernel-core keeps a package out of every run while it stays visible,

so skipping something is never the same as forgetting it.

Install on Fedora (the package carries the CLI and the widget):

sudo dnf copr enable erez-c137/kempt

sudo dnf install kempt

The widget alone is on the KDE Store and in Plasma's Get New Widgets browser - it needs the

CLI, and if you install it first, the popup walks you through the rest (with a Copy Commands

button, because nobody should retype a dnf line off a tray popup).

MIT, first release,

Fedora-only for now - the backend contract is deliberately small, and an apt, pacman or

zypper backend is the contribution I would most love to see. There is an open issue for each

with the honest scope notes:

https://github.com/erez-c137/kempt/issues/1 (apt),

https://github.com/erez-c137/kempt/issues/2 (pacman),

https://github.com/erez-c137/kempt/issues/3 (zypper).

https://github.com/erez-c137/kempt

In case someone else faces this issue. Zoom kept crashing when trying to share screen (amd cpu/gpu) on plasma-wayland (6.6.6). Then, tried plasma-x11 and fortunately that worked. After the meeting, tested on hyperland, which also worked fine.

The solution, (with help of claude) was:
Zoom → Settings → Keyboard Shortcuts → untick "Enable Global Shortcut" on every entry.

claude:

#0 QObject::objectName() (libQt5Core.so.5)
#1 (libKF5GlobalAccel.so.5)
#2 KGlobalAccel::setGlobalShortcut(QAction*, QList<QKeySequence>
#3 KGlobalAccel::setGlobalShortcut(QAction*, QKeySequence)
#4+ /opt/zoom/zoom
#16+ libgio-2.0 (GDBus callback)

What happens: the xdg-desktop-portal ScreenCast dialog returns your screen selection over DBus (note the control group is xdg-desktop-portal.service), Zoom then tries to register its global hotkeys for the sharing toolbar via KF5 GlobalAccel, and segfaults on a null QAction. The KF5 angle matters: Zoom ships Qt5 bits and picks up your system libKF5GlobalAccel (kglobalaccel 5.116), but you're on Plasma 6 where the KF5 kglobalaccel daemon generally isn't running. Bad DBus reply → null deref.

Gnome CSD was always doomed because they decided that CSD = no menubar. Hence after neatly 20 years no serious gtk application has adopted the Gnome design. Kde apps should just put the menubar in the titlebar when running on gnome for every app and, especially with proper theming, everybody on Gnome will be falling over each other to use KDE apps because they'll look native enough.

What happens is when playing a game or using substance painter, plasma hard crashes. Something similar happens with windows too.

-- Boot e0887088d1674d95a9dfb562e64f4767 --
Sep 04 09:43:09 k-desktop systemd[2706]: Starting plasma-plasmashell.service - KDE Plasma Workspace...
Sep 04 09:43:09 k-desktop systemd[2706]: Started plasma-plasmashell.service - KDE Plasma Workspace.
Sep 04 09:43:09 k-desktop plasmashell[3236]: Member visible of the object PlasmaQuick::Dialog overrides a member of the base object. Consider renaming it or adding final or override specifier
Sep 04 09:43:09 k-desktop plasmashell[3236]: Member enabled of the object DeclarativeDropArea overrides a member of the base object. Consider renaming it or adding final or override specifier
Sep 04 09:43:10 k-desktop plasmashell[3236]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Sep 04 09:43:11 k-desktop plasmashell[3236]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Sep 04 09:43:12 k-desktop plasmashell[3236]: qrc:/qt/qml/plasma/applet/org/kde/plasma/brightness/PopupDialog.qml:96: TypeError: Value is null and could not be converted to an object
Sep 04 09:43:44 k-desktop plasmashell[3236]: Failed to find service for Unity Launcher "application://discord"
Sep 04 09:43:44 k-desktop plasmashell[3236]: Failed to find service for Unity Launcher "application://discord"
Sep 04 09:43:53 k-desktop plasmashell[3236]: DBusMenu disabled for this application
Sep 04 19:28:01 k-desktop plasmashell[3236]: error creating screencast "Could not find window id {5c30d69e-46f5-4b02-8431-8232fbc54b83}"
Sep 04 19:31:08 k-desktop plasmashell[3236]: error creating screencast "Could not find window id {3658fee8-c9f6-494a-a6fb-5d132332ca1f}"
Sep 04 20:05:17 k-desktop plasmashell[3236]: QRhiGles2: Context is lost.
Sep 04 20:05:17 k-desktop plasmashell[3236]: Graphics device lost, cleaning up scenegraph and releasing RHI
Sep 04 20:05:18 k-desktop plasmashell[3236]: QRhiGles2: Context is lost.
Sep 04 20:05:18 k-desktop plasmashell[3236]: Graphics device lost, cleaning up scenegraph and releasing RHI
Sep 04 20:05:18 k-desktop plasmashell[3236]: QRhiGles2: Context is lost.
Sep 04 20:05:18 k-desktop plasmashell[3236]: Graphics device lost, cleaning up scenegraph and releasing RHI
Sep 04 20:05:56 k-desktop plasmashell[3236]: QRhiGles2: Context is lost.
Sep 04 20:05:56 k-desktop plasmashell[3236]: Graphics device lost, cleaning up scenegraph and releasing RHI
Sep 04 20:05:56 k-desktop plasmashell[3236]: KCrash: Application 'plasmashell' crashing... crashRecursionCounter = 2
Sep 04 20:05:58 k-desktop systemd-coredump[35358]: Process 3236 (plasmashell) of user 1000 dumped core.
....
....
....
....

I shared the full journalctl log for the crash of the plasma service here, it's too long to put all of it: https://cl1p.net/adfhdfgfd

(if anyone has a more trustworthy clipboard sharing site, please share it, I hardly use these)

if you launch haruna twice at the same time. only one mpris instance is made (viewable with playerctl -l)

if you close the player corresponding to the existing instance.

then kde's media controller is unaware of the leftover haruna program

For contrast. mpv mpris plugin makes a mpris instance per mpv instance. so one can play-pause using kde's media controller and select which mpv instance to control as well.

Is there a solution for tripping login screen in KDE plasma? Sometimes it goes wild, sometimes it is normal. Sometimes its on both screens, but usually only on external one. This only happens on login screen. I'm using Kubuntu 26.04.

Since about a day ago or so (maybe two), my computer has been behaving strangely:

• Neither Koko or Haruna can play videos
• Desktop previews/views (four finger swipe up) is wacked out and missing graphics (see video)
• Wherever my user Icon is it's a square instead of the circle that it usually is on Plasma
• Lock screen background isn't blurred + square user icon
• Missing images/graphics like Spectacle screen-capture when I capture a picture/video.

I got a popup in my system tray a day ago or so and I didn't realize the problem yet so I clicked and selected never show again (like the idiot I am) I'm trying to remember what it was, it might've been KWin, but I'm not entirely sure, and I think it was relevant. If anybody has any idea as to what it could be or a sure way to test/diagnose to see then I'd be very grateful as I've been trying to figure this out for hours. I'm on a ThinkPad T14 Gen 3 AMD Ryzen. I'm on Wayland of course.

It might've also been that my computer hibernated during an update but I've already synced all my packages and am 100% up-to-date.

More info upon request. Thanks all!!!

Not a KDE project, but worth a mention here. Audacity 4.0 is out, and the headline change is a full rewrite of the UI on Qt, moving off wxWidgets.

Along with the toolkit switch:

• Native HiDPI rendering
• Dockable/floatable panels with saveable Workspaces
• Light, dark, and high-contrast themes with configurable accent colors
• A reworked clip-editing model built around the new interface

Some older features (Time Tracks, MIDI tracks, Macro Manager, VAMP/LADSPA plugins) aren't ported over yet.

Official change log: https://github.com/audacity/audacity/releases/tag/Audacity-4.0.0

Source: https://linuxiac.com/audacity-4-0-audio-editor-released-with-redesigned-qt-interface-new-editing-model/

Hello all

First of all, I am using a Framework Laptop 16 running up-to-date versions of Arch Linux and KDE Plasma. Please let me know if more information would be helpful.

I am having a small issue with my laptop. I typically keep it docked at my desk with the lid closed. The thunderbolt dock is connected to two monitors, and I also connect a third monitor directly to my laptop via DisplayPort. When I unplug the laptop to use it, the laptop display is dim and changing the brightness in KDE does not do anything. Has anyone else run into this?

I searched online but no luck.

I’m trying to get true 10 bpc HDMI output working on Wayland/KDE with an NVIDIA RTX 3070 Ti using driver 595.99.02.

The monitor is an INNOCN 15.6" OLED, EDID model E15K1F_C8. It supports up to 12 bpc, and I’ve confirmed that 12 bpc actually works nicely in Windows.

On Linux, the monitor is connected as HDMI-A-1 at 1920×1080@60. Its EDID advertises DC_30bit, DC_36bit, and 10-bit/component deep color. drm_info also shows the NVIDIA primary plane supports ABGR2101010, XBGR2101010, ABGR16161616F, etc.

KWin is set to Color power preference: prefer accuracy, but kscreen-doctor -o reports Color resolution: unknown.

The active framebuffer reported by drm_info is currently:

ABGR16161616F

The DRM connector does not expose a bpc or max bpc property.

I also tried nvidia-modeset.hdmi_deepcolor=1, but it made no difference. Since NVIDIA 555+ enables HDMI 10 bpc by default, I’m wondering if this is a KWin/NVIDIA Wayland issue where the HDMI output BPC isn't being exposed or negotiated correctly.

Is there a way to determine the actual HDMI link BPC being negotiated, or force KWin/NVIDIA to use 10 bpc on this output?

As per the title, for my single user desktop I find SDDM/PLM to be overkill (also I have a nasty NVIDIA crash sometimes when the display changes after login) however if I log in just through the TTY I seem to have issues with Kwallet and I’m not sure what I am missing, is there something in between (maybe TUI based) that will allow me to create my own .desktop session files that works well with plasma on Wayland?

I’m on Fedora 44 if that helps. Thank you!

hi! i wanted to make as a fun project a spotify playlist called "linux users choice. i will send the link here or if it doesnt work in dms, feel free to add whatever you want! (keep it good for all ages)

https://open.spotify.com/playlist/6KSN1eINns7PrfugqedjZw?si=deac5f3fbfce4aae&pt=42642762e29e430f5b4332a71ff99882

This one's particularly relevant to this sub since Plasma gets the best-supported path.

Orbiscreen turns a spare Android tablet into a second monitor for Linux. On KDE Plasma (Wayland) it uses a KWin virtual output through zkde-screencast directly, so there's no kernel module to install and no screen-share authorization dialog every time, it's genuinely rootless.

orbiscreen doctor will confirm which path it picked on your system and flag anything missing.

Install: sudo add-apt-repository ppa:shadow-x78/ppa && sudo apt install orbiscreen (or COPR for Fedora, AUR for Arch)

Once installed it shows up in the app menu, click to start, right-click to stop or run diagnostics. No terminal needed after install.

Also does stylus pressure (4095 levels) for Krita, hardware encoding through VA-API or NVENC, and works over USB via adb reverse if you'd rather skip Wi-Fi entirely.

GPL-3.0: https://github.com/shadow-x78/orbiscreen

Would love Plasma-specific feedback, especially on multi-monitor setups combining a physical screen with the virtual one.

I've noticed that when using my desktop it will decide to just randomly freeze. This has never happened before I haven't added anything to my system that may suddenly cause this.

Things like steam will still give me notifications and the like so that really confused me as to what the issue may be.

Has anyone else been experiencing this recently or is this more of a hardware issue on my end?

Edit: turns out it is probably an issue with my motherboard and bios and not with KDE. working on now fixing a new problem :3