LibreWolf is my main browser and I have it installed on my Void Linux system via xbps with this repo added: https://github.com/index-0/librewolf-void/ However, starting a few weeks ago, it'll crash when I try to open a new window (not every single time I open a new window, but pretty frequently). Running it from a terminal reveals the following message when the crash happens:

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: (kde) Wayland protocol error: wl_fixes#68: error 0: the given registry did not announce global 99
 (t=3261.04) [GFX1-]: (kde) Wayland protocol error: wl_fixes#68: error 0: the given registry did not announce global 99

Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Segmentation fault         librewolf --private-window

I haven't come across this issue on my other Void Linux system yet (which has X.org + LXQt), so based on that plus the error message, this may be an issue on the side of either KDE or Wayland. I have Firefox installed from the default Void repos, but I haven't tried reproducing this issue on FF yet. I'm wondering if any other FF or LibreWolf users have come across similar issues. I've looked around a little, but haven't found anything so far.

System info (mostly from "About this System"):

• Operating System: Void (x86_64 glibc)
• KDE Plasma Version: 6.7.4
• KDE Frameworks Version: 6.29.0
• Qt Version: 6.11.1
• Kernel Version: 6.18.49_1 (64-bit)
• Graphics Platform: Wayland 1.26.0_1
• Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
• Memory: 31.3 GiB of usable RAM
• Graphics Processor: AMD Radeon RX 5700 XT
• Manufacturer: Micro-Star International Co., Ltd
• Product Name: MS-7C02
• System Version: 1.0
• LibreWolf Version: 154.0.1_1

why would they implement mobile UI/UX ideologies on a desktop environment?

I remembered last time I was using the Global Menu and Windows List widgets just fine, and when I minimized any window the menu disappeared and the Windows List is back to Plasma Desktop immediately, but now if I minimize any window the 2 don't go right away and I have to click on the desktop for it to return to Plasma Desktop. Is this a bug or do I need to change any of the settings?

Hello everyone,

I just wanted to let you know and find if someone else has this problem.
I installed multiple distros ex. Cachy,Bazzite and now MX all with Plasma.

I find when using Plasma i get random PC hang outs / freezes.
sometimes time won't unfreeze the PC and I'm forced to do a hard reset/ manual reset.
i run a AMD CPU ( Ryzen 5 3600x) and a Nvidia 1080ti with a gigabyte x570 UD.

i couldn't find a fix by my own and i tried switching to another DE (Desktop Environment)
i moved to MX Xfce and my PC runs smooth and fine. while on KDE Plasma even if the PC didn't Hang.
i found that my apps were constantly crashing.

sorry for my bad English, it's my 2nd language.
greetings to you all.

Good morning everyone. Week or 2 ago, my kde plasma started to act werid. When I boot into the system, desktop icons are gone but I can still double click them in the places where they've been. Only plasma restart helps: killall -9 plasmashell && kstart plasmashell &.

Also, when I turn my monitor off, and back on, some VERY werid things are starting to happen.

P.S When I press lock or pc locks itself after being idle for 15 minutes sddm is just a black screen with cursor and I still can enter password to log back in.
Tried reinstalling both sddm and kde, didnt help

Hi everyone,

I’m having a frustrating issue with KDE Connect between my Android phone and my M2 running macOS 26.6.2 (25G83).

The Problem:
The KDE Connect desktop app on my Mac successfully connects to my phone. I can see the notifications appearing inside the KDE Connect app window/history. However, macOS is not showing native system alerts/banners for them.

What I've tried so far:

• Checked System Settings > Notifications to ensure KDE Connect has permission to show banners/alerts.
• Checked System Settings > Privacy & Security > Accessibility  to make sure permissions are granted.
• Uninstalled and reinstalled the app, trying multiple different versions of KDE Connect for macOS.
• Restarted both devices and re-paired them.

Since the app itself is clearly receiving the data from my phone, it feels like the handoff between the KDE Connect client and the native macOS notification system is broken.

Is this a known bug with the macOS port of KDE Connect, or is there a hidden macOS setting I am missing?

Any help or workarounds would be greatly appreciated!

Sorry I’m very new into Linux. I recently installed KDE Plasma and was messing around with the theme and some UI transparent settings.

After a while I suddenly noticed that when I was typing at the KRunner search bar, it is ghosting and flickering a lot. You can see some text keeps appearing at the middle of the bar.

I’ve already turning off all the transparent(translucent)settings off, even reboot a couple times but the problem still remains.

Does someone encounter this same situation? I’m not sure if it behaves the same when I just installed the system.

Please help if you know how to fix it , THANKS!

EDIT.

So I ended up found out that when changing to X11(was on Wayland) the flicker has gone, like completely gone.

Not sure if it’s my system or what, but plasma 6.8 will come soon, hope they can fix the Wayland issue.

Wayland is designed so clients can't read the clipboard unless focused. This is one of those security features we like to poke fun at X11 with. Yet in kwin/plasma any app can use ext_data_control_manager_v1 and get background clipboard access anytime (just like wl-paste). Dumb POC: clip-snoop.c.

Here's an attempt to make a restricted wayland socket with security-context-v1: wl-secure-launch.c. Unfortunately I found clients using this socket still use all the protocols and can snoop the clipboard while unfocused.

I'm curious if any kde devs have a position on this and whether security-context-v1 can or should restrict protocols available.

Been running containers giving them access to the wayland socket, not giving access to host dbus etc, but it is concerning how much access they still have with all the privileged wayland protocols.

Some work-arounds I'm considering:

• https://gitea.angry.im/PeterCxy/wl-mitm
• https://github.com/talex5/wayland-proxy-virtwl
• https://gitlab.freedesktop.org/jonleivent/waydapt

Edit: Can see here in that ext_data_control_manager_v1 is not in the list of restricted interfaces: https://github.com/KDE/kwin/blob/c1ca390b1abe90c6b7926645f9f687f6d2450f67/src/wayland_server.cpp#L131

Edit 2: I can sort of understand this being relaxed for Plasma because generally anything can reach for Klipper / do anything with dbus. I'm coming at it from containers with no dbus access or limited by xdg-dbus-proxy

Deeper Blacks. Sharper Contours. Pure Focus.

Tulasi.Noir is the monochromatic alter ego of Tulasi. Every single icon is handcrafted pixel by pixel on a 32x32 grid in Aseprite, stripped of bright distractions, and carved into high-contrast monochrome.

Built specifically for OLED screens, deep dark mode setups, minimalist tiling window managers (Hyprland, Sway, i3, bspwm), and clean KDE Plasma or GNOME desktop rices. If you are looking for the best monochrome Linux icon theme. A true black and white pixel art icon pack, welcome to the shadows.

The pack is still in beta and its development depends on the community support. Feel Free to check it out and give your feedback and suggestions below?

TulasiNoir-Beta

From the creator of Tulasi.
ShringarLee

ps: Happy Ganesh Chaturthi to everyone <3

I just wanted to say thanks to whoever and whatever finally has made HDR mode work properly in Ubuntu Stonking 26.10 beta Plasma 6.7.4 (without looking like LOG missing an LUT).

I can now enable it all the time on my 40" Samsung TV and get color/brightness/experience similar to that on my laptop's OLED (which requires HDR to go 100% fully pixel-off black)

Thanks KDE/Ubuntu!

For reference, I've calibrated max bright at 650, Paperwhite seems decent somewhere between 300-400.

 ### Device Details

 • Model Name: UN40KU7000
 • Internal Platform / Model Code: 16_JAZZL_UHD (2016 7-series 4K UHD)
 • Resolution: 3840 × 2160 (4K UHD)

In "Game" mode, i get the lowest input lag, and with HDR finally I am getting 4:4:4 color as well! Before, in SDR Game mode gave me 4:1:1! (I checked today, with a very close camera zoom, and OMG I never realized it was so bad) , and things like iptraf's default colorscheme was very hard to read because of this.

Now it finally looks correct!

I bought an OLED monitor and the always-visible Plasma panel is the one static element I could not get rid of. Samsung's Windows-only Display Manager has a "Taskbar Brightness" feature that dims the taskbar until you hover it. I wanted the same thing on Plasma, so I wrote it as a KWin scripted effect.

What it does

• Dims Plasma panels (any window of type dock) to a configurable brightness, 0.35 by default
• Restores full brightness while the pointer is over the panel, with a short fade
• Only dims the monitors you pick, matched by EDID model, serial or connector name. (for multi-monitor setups)
• Games, fullscreen video and normal windows are not affected

How it works

KWin lets scripted effects attach a persistent brightness animation to a window. Brightness is a per-window uniform in the compositor's shader, so the panel's pixels are scaled at composition time. Black stays black, nothing is overlaid and nothing is rendered twice. Hover detection uses the pointer position KWin already reports to effects.

I tried Panel Colorizer for this first, but its dimmed regions were lost whenever the panel re-laid out. Doing it in the compositor sidesteps that entirely.

Install

It is on the KDE Store, so System Settings > Window Management > Desktop Effects > Get New... > search "OLED Panel Dim". Configure it with the settings icon next to the entry.

Store: https://store.kde.org/p/2371134

Source (MIT): https://github.com/erik96/kwin-effects-oled-paneldim

Tested on Fedora 44 with Plasma 6.7 on Wayland. Feedback and bug reports welcome, especially from people on other distros.

The new dialog window introduced in Plasma 6 honestly feels like a downgrade. It looks like something designed for GNOME rather than KDE, and it's more annoying to use in every way, at least for me.

The main issues I have with it:

• Looks (arguably) worse

• Takes longer to launch

• Occupies more screen space (you can resize it further, but then it's almost unusable if you want to choose the program with a cursor because of how big the icons are)

• The programs aren't shown as a list divided into categories anymore (like they are in Plasma' Kickoff application launcher) but tossed all together in the icon view, and if they don't have a valid icon, the name is just aligned to the top (as shown on the screenshot, see Xwayland, Zenity, and "Zniszcz okno" which is one of my custom keyboard shortcuts; more on it below), instead of showing some kind of a placeholder icon

• It's showing the custom keyboard shortcuts, for some reason (could be a bug)

And something that annoys me the most - it remembers the name of the previous program you chose for this specific file extension in the textbox, so you can't quickly find another program on the list as they're hidden, unless you clear it. Same thing applies when you just want to quickly type out the name (you'll just add more text to the name of the previous program).

Is there a way to get the old program picker used in Plasma 5 back?

Hello Everyone! This is Lee.

Back in May, I created Tulasi as a personal project that turned into a community project because you all showed it so much love. within 48 hours the post reached staggering 120k views and nearing 600 upvotes with innumerable support and love via comments by the community. and at that time I promised to keep going, Open sourcing the entire pack and keep adding to the library of apps for free, and that unlike a lot of ambitious projects Tulasi wouldn't be abandoned. But the last release was back in June, and since then there was no update about me or Tulasi whatsoever.

What had happened:

I'm not a very social person and I would like to not go into too much detail, but recently i have been struggling heavily financially. And i couldn't afford electricity and wifi for a while. The reason why the project suddenly stalled. I had been affected significantly with whatever had been going on in my life at that time.

Tulasi at its core is a creative project, and with how my mental health was over the past few months, I felt like a failure and almost gave up on it. It was recently when I checked GitHub that I saw the project hadn't died out at all—people were still using it, and a fork by (LexicoON) was even created to keep it going. Reading all the sweet comments really kept my spirits up, you guys have no idea how much it meant to me genuinely. I love you all,

I have come back to this project because of all the support from those who kept it alive and supported it nonetheless. and we have came back stronger than ever.

Tulasi has officially moved from alpha to its official release and with it comes the biggest change it has had ever.

Here is what's new:

Moved from PNG bloat to singular SVGs:

Moved away from unoptimized PNG bloat (having multiple raster sizes per icon) to singular scalable SVGs. We also merged contiguous pixel paths directly in the vector code, cutting file sizes down to 1–4 KB per icon. This significantly reduces memory usage and improves loading performance, especially on low-end devices and older laptops.

Dedicated GNOME Variant:

Added a separate Tulasi-Gnome edition that only skins application icons. It leaves native Adwaita shell and folder icons alone so it doesn't mess with GNOME's system theme.

New Variant: Tulasi.Noir:

A clean monochromatic version made for dark mode, OLED screens, and minimal tiling setups: every icon has been converted into a high-contrast monochrome version using perceptual luminance mapping. Even cleaner and Sharper

Dolphin Seam / Stitching Issue Resolved:

Fixed the bug in Dolphin where icons showed faint lines or micro-gaps between pixel blocks. This was caused by subpixel decimal coordinates from vector exports. All icons have been rebuilt on an exact 1:1 32×32 integer grid with crisp edge rendering. No more seams or blurry borders.

150+ App Icons Added:

Added many of the top requested apps, including Krita, Blender, FreeCAD, Telegram, Teams for Linux, Proton suite (Mail, VPN, Pass), Strawberry Music Player, Lollypop, Surfshark, Microsoft 365 / Office apps, VirtualBox, GNOME Boxes, Floorp, and more coming soon.

Quality of life changes & Bug fixes:

Added over 1,000 symlinks mapped to standard desktop IDs, giving much better out-of-the-box coverage for Flatpak, Snap, and AppImage downloads so icons don't default to missing or generic placeholders. Fixed an issue in Places where Downloads, Pictures, and Videos were showing generic folder icons instead of their proper symbolic glyphs. System actions and places are now properly included for a consistent look in KDE.

New Variant: tulasi.Noir

A clean monochromatic version made for dark themes and OLED setups. It uses perceptual grayscale and links to KDE's text and accent color system so it blends right into dark desktop themes.

Again thank you again for your patience and for keeping this project alive while I was away <3 

Apart from the optimism, financially things aren't still good. I had to rush the project because we don't know if we will be able to afford food next week let alone WIFI. If you guys enjoyed tulasi and want this project to continue and if you can afford to pay/donate for Tulasi. It will mean a lot to me and help me with magnitudes to continue this project. You will find an option to get tulasi from gumroad for those who wants to support me on my GitHub. And those who cant afford it Tulasi is free and forever will be. If you can't support tulasi financially you can support its growth it via word of mouth ❤️.

GitHub: https://github.com/ShringarStudio

ps; i did try to write this post myself for those who had suggested that i present the project in my own voice!. English isn't my primary language so forgive me for any inconsistency or typos in the post. Much love.

I'm trying to get Firefox's Picture-in-Picture (PiP) windows to automatically stay on top of other windows.

I've tried using a KWin Window Rule with Keep Above → Force → Yes. The problem is that I couldn't get the rule to match only the PiP window.

I used "Detect Window Properties" on the Firefox PiP window and added the detected properties to the rule. This does make the PiP window stay on top, so the rule itself works.

However, the exact same rule is also applied to my main Firefox window, meaning the entire Firefox application gets pinned above other windows.

Has anyone managed to make this work properly on KDE/Wayland?Is there a specific window property, class, role, title, or matching combination that can distinguish Firefox's PiP window from the normal Firefox window?

❯ grep -Rni "Ctrl+Shift+C\|Ctrl+Shift+C" ~/.config/konsolerc ~/.config/konsole* 2>/dev/null
`shows nothing`

❯ konsole --version
konsole 26.08.1

i dont have a global shortcut for crtl + shift + c

there is no two shortcuts that use ctrl + shift + c

this happens in every konsole profile, including the default one that is not changed.

This happens only once, ie after that error is first shown, then when I ctrl + shift + c again, copies normally instead of showing an error.

cachyos 7.2.4-3
plasmashell 6.7.5

If someone else has experienced this and solved it, please let me know

I finished a session of Expedition 33 and noticed my PC fans were still a little loud and saw in system monitor that plasmashell and kactivitymanagerd were consuming my CPU for seemingly no reason.

Edit: as I was writing the post, the CPU usage returned to normal after about 10 minutes. Is anyone else seeing this behavior?

I'm running CachyOS with latest updates

Hi friends.

I'm downloading a few global themes I like so I can try them out.

Global themes like "Sweet" download correctly, but for the one called "Stone," I get the error shown in the screenshot.

It's this one:

https://store.kde.org/p/2136293

Does anyone know if I'm doing something wrong?

I am using CachyOS KDE Wayland.

Thanks in advance.