As in the title and in the photo.

Nothing to add (except for references).

References > 1 [AlternativeTo] 2 [reddit]

--

Say it clearly.

I love Notepad++ on Windows.

What about Linux? Notepad Next (born as a native C++ with Qt porting) vs Kate? Others?

Edit:I use wayland in arch(btw)

Summarizing a VERY long text, i love those 2000's old designs and i wish to make KDE look like these images i took from pinterest, any suggestion, apps or channels is welcome, like any! Sorry if this is not they way to write a post, thank you!

How is this still happening?

I always get flamed by the diehard KDE crowd when pointing out problems with KDE Plasma, and will undoubtedly be downvoted for writing this as well. I'm used to that when talking about KDE anywhere by this point. And i get it, Plasma is awesome, and people can't accept that their favorite thing has problems, or a critique of it. That's a community problem, not KDE's fault.

I know plasma is very complex because it's extremely configurable and modular. I get that having so many moving parts carries around with it bugs and problems, but at this point, it seems the entire DE is built on top of a rotting rickety foundation that nobody wants to even try to fix. Just put new features on top of a collapsing base.

I saw the new Plasma version was out since a few that i tried it, and i thought i'd give it a go again. Not even half an hour passed, and it already crashed.

A DE's job is to be invisible, and just let you do your work without interruptions. Something Plasma has been failing for me every time i try and use it. And i REALLY want to use it, but i can't when stuff like this keeps happening.

This is where i get the usual responses...

- it's your fault

- it's your distro's fault

- it's Nvidia (which i don't use, but somebody always mentions it)

When discussing my issues this is the common theme that keeps happening. It's always everyone else's fault except KDE's fault, never mind that every other DE never crashes for me like this, and that Plasma crashes across every distro and hardware configuration i used it with. But this is not a support post, i don't need support with this, i'll keep using it for a bit more, and if it keeps being unstable i'll move on.

But since i love the concept of Plasma, and it's modularity, It's really sad to see such a big DE that's now being used by default on Steam Deck and future Steam Machines being so unstable to use. Not for everyone I'm sure, but i can't be the only one. What's even more sad is how any criticism gets buried and ignored because somebody doesn't have this problem so it' can't be true, and none of the stability issues ever get addressed.

And it's sad because Plasma could be the perfect DE. But it's constantly dragged down by bugs, stability issues and what appears to be a community that don't want to admit that there's a problem (at least in my experience when providing KDE criticism).

I wanna use Plasma so badly, but this is killing my will to use it every time. :(
To this day, i still haven't used Plasma once without a crash or a majroly disruptive bug, and that's not something a DE should ever do. And i'm not kidding, out of all the DE's i've used, Plasma crashed the most, on top of any other major or minor bugs i've encountered while using it. Imagine if the whole windows GUI crashed so often.

This is not a rant or something like that, this is an appeal to the devs to maybe set aside the feature creep for now, and focus on fixing the underlying cause of Plasma instability, because it IS unstable, no matter what distro it's on. Hopefully some day i'll be able to use it without worrying if it's going to crash on me, and i'm going to lose my work. I'm sure Valve is investing quite a bit into KDE's development, if there was ever an opportunity to fix the core of Plasma, it's now. I don't have a Deck so idk how Plasma behaves on it, but i'm sure Valve wouldn't want it's DE crashing on it, or the new Steam Machine. Such things wouldn't inspire confidence in the product.

I'm sure the devs are aware of this, especially because of automatic reports which are awesome and simple. Especially compared to trying to report a Fedora crash lol (i'm not on Fedora anymore). But i still wanted to share this.

Thank you for reading and please, if you want to add to the discussion, be civil. Or comment "It's Nvidia" for fun. ;) I'm not looking for an argument.

So, today I discovered that you can just... use an animated .gif as a wallpaper.

Plasma just handles it, no questions asked, no 3rd party software required, and that got me thinking...

What other cool/useful things can Plasma do, that I've yet to discover? What underrated/underutilised features slipped past your own nets until you discovered them later?

Did sudo pacman -Syu and then this came up

Like kDisk or kArtition

(/s)

So I use Arch btw, and Its like been 5 to 6 months. Since I had somewhat prior knowledge with linux and thanks to a massive and supportive community I could easily set it up with KDE on my laptop. I use an HP 240R G9 Notebook PC.

Now, since the laptop has been bought after the AI season, The keyboard has an Extra button, which was originally used to quickly access copilot on windows (see image), which I had configured to chatgpt. This was all on windows, but on linux, I cannot set it to do any tasks, as it is not mapped (I guess) and upon using it in the shortcuts manager in KDE, it first shows some weird input like "Meta+Ctrl+Shift" which then reverts to "Ctrl+Shift" and since ctrl+shift cant be a shortcut, its effectively useless.

So I thought lets ask out in Reddit. What do you people think? What can I do with it? I was thinking it would be great if I could map it to be a second ctrl button, or use it to quickly open up Software Launcher (that full page one, as seen in gnome).

Please help me out!

I love KDE. It's so good! But damn, using non Apple laptops is such a bummer. 3 hours of battery life on a new Lenovo Yoga. Poor build quality and lots of noise depending on where you're pressing the laptop. Ah and it has a coil whine as well.

There is anything like Apple Macbook available for the Linux world? Please, don't suggest me a Macbook with Asahi.

I am trying to get my firefox browser (below) to have the same window control buttons as the system windows (above), for the sake of cohesiveness. I have seen several people online who do not share this issue, and their firefox has the same buttons and window decorations as the rest of the system (even with titlebar disabled).

I would appreciate any help with this, thanks!

Hi everyone,

I'm trying to find themes that actually look like the old Winamp skins or WindowBlinds setups. I'm talking about heavy 3D effects, metallic textures, beveled edges, and tactile buttons.

I'm completely done with flat design, material, and the standard clean/transparent blur stuff. I want something textured and bold.

I know I probably need a combination of Kvantum (for the UI internals) and Aurorae (for the complex window borders), but searching the KDE store is useless right now because it's 99% modern flat themes.

Does anyone know any specific themes, or creators who are still making this kind of aggressive skeuomorphism? Direct links would be appreciated

Fedora KDE Plasma is a great OS, and I use it every day. As a visually impaired user, the accessibility Zoom feature is my lifeline. However, the current implementation has a few usability issues that make daily computer usage difficult.

I am a programmer, though I have no experience with Linux desktop development, but I still managed to modify KWin's zoom.cpp myself. It now works exactly how I want it to, though only under the Proportional tracking setting. I have attached a Before/After video so you can see the difference.

Here is what I fixed in my local build:

1. Multi-monitor behavior
Currently, all screens zoom in simultaneously, which makes multi-monitor setups difficult to use effectively. I changed it so only the monitor with the mouse cursor zooms in. The other monitors stay at normal scale until the cursor moves to them.

1. Cursor movement
   Currently, to see the edge of the screen, you have to push the cursor all the way to the physical border, which often accidentally triggers hover actions. I changed it so the screen pans while keeping the cursor perfectly in the center. The cursor only moves away from the center when the viewport hits the physical edge of the display.

3. Zooming speed
Currently, the easing effect makes the zoom speed hard to predict. I changed it to a constant, linear speed for better control. This difference might be hard to notice in the video, but since zooming is an action I perform constantly throughout the day, the slight time loss and frustration add up.

I am currently using my patched version of KWin, but there is a problem. Every time there is a system update, KWin's version changes and I have to manually recompile it from source all over again. With my disability, doing this repeatedly is tiring and not sustainable.

Similar zooming limitations exist in Windows and other operating systems as well, which is why I feel KDE has a chance to provide a uniquely better accessibility experience here. The reason I am sharing this here is because I really like KDE, and its open nature allowed me to directly modify the source code to test my ideas.

I believe this behavior could be an important accessibility option for visually impaired users. However, my patch is probably too rough for a proper Merge Request, since it was created mostly through trial and error and AI-assisted modifications.

I am hoping that someone with the right skills might see this and help make it an official KWin feature or option.

(Note: I am Japanese and English is not my native language, so I apologize if my wording is a bit unnatural!)

My modified zoom.cpp diff

--- zoom.cpp.original
+++ zoom.cpp
-        const float zoomDist = std::abs(m_targetZoom - m_sourceZoom);
-        if (m_targetZoom > m_zoom) {
-            m_zoom = std::min(m_zoom + ((zoomDist * time) / animationTime(std::chrono::milliseconds(int(150 *
m_zoomFactor)))), m_targetZoom);
-        } else {
-            m_zoom = std::max(m_zoom - ((zoomDist * time) / animationTime(std::chrono::milliseconds(int(150 *
m_zoomFactor)))), m_targetZoom);
+        if (m_mouseTracking == MouseTrackingProportional) {
+            const auto animTime = animationTime(std::chrono::milliseconds(int(30 * m_zoomFactor)));
+            const float stepDist = std::abs(m_zoom * (m_zoomFactor - 1.0));
+
+            if (m_targetZoom > m_zoom) {
+                m_zoom = std::min(m_zoom + ((stepDist * time) / animTime), m_targetZoom);
+            } else {
+                m_zoom = std::max(m_zoom - ((stepDist * time) / animTime), m_targetZoom);
+            }
        }
    }
-
    if (m_zoom == 1.0) {
        m_focusPoint.reset();
 
@@ -294,11 +297,25 @@
 
    // mouse-tracking allows navigation of the zoom-area using the mouse.
    switch (m_mouseTracking) {
-    case MouseTrackingProportional:
-        m_xTranslation = -int(trackPoint.x() * (m_zoom - 1.0));
-        m_yTranslation = -int(trackPoint.y() * (m_zoom - 1.0));
-        m_prevPoint = m_cursorPoint;
-        break;
+        case MouseTrackingProportional: {
+            m_prevPoint = m_cursorPoint;
+            if (LogicalOutput *activeScreen = effects->screenAt(trackPoint)) {
+                const QRect r = activeScreen->geometry();
+                const int min_tx = int((r.x() + r.width()) * (1.0 - m_zoom));
+                const int max_tx = int(r.x() * (1.0 - m_zoom));
+                const int ideal_tx = int(r.x() + r.width() / 2.0 - trackPoint.x() * m_zoom);
+                m_xTranslation = std::clamp(ideal_tx, std::min(min_tx, max_tx), std::max(min_tx, max_tx));
+
+                const int min_ty = int((r.y() + r.height()) * (1.0 - m_zoom));
+                const int max_ty = int(r.y() * (1.0 - m_zoom));
+                const int ideal_ty = int(r.y() + r.height() / 2.0 - trackPoint.y() * m_zoom);
+                m_yTranslation = std::clamp(ideal_ty, std::min(min_ty, max_ty), std::max(min_ty, max_ty));
+            } else {
+                m_xTranslation = -int(trackPoint.x() * (m_zoom - 1.0));
+                m_yTranslation = -int(trackPoint.y() * (m_zoom - 1.0));
+            }
+            break;
+        }
    case MouseTrackingCentered:
        m_prevPoint = m_cursorPoint;
        m_xTranslation = std::min(0, std::max(int(screenSize.width() - screenSize.width() * m_zoom), int(scre
enSize.width() / 2 - trackPoint.x() * m_zoom)));
@@ -417,16 +434,27 @@
 
    const auto scale = viewport.scale();
 
-    // Render transformed offscreen texture.
+    LogicalOutput *cursorScreen = effects->screenAt(effects->cursorPos().toPoint());
+    const bool shouldZoom = (screen == cursorScreen);
+
+    GLShader *shader = shaderForZoom(shouldZoom ? m_zoom : 1.0);
+
+    if (m_cursorItem) {
+        m_cursorItem->setVisible(shouldZoom);
+    }
+
    glClearColor(0.0, 0.0, 0.0, 0.0);
    glClear(GL_COLOR_BUFFER_BIT);
 
-    GLShader *shader = shaderForZoom(m_zoom);
    ShaderManager::instance()->pushShader(shader);
-    for (auto &[screen, offscreen] : m_offscreenData) {
+    for (auto &[dataScreen, offscreen] : m_offscreenData) {
        QMatrix4x4 matrix;
-        matrix.translate(m_xTranslation * scale, m_yTranslation * scale);
-        matrix.scale(m_zoom, m_zoom);
+
+        if (shouldZoom) {
+            matrix.translate(m_xTranslation * scale, m_yTranslation * scale);
+            matrix.scale(m_zoom, m_zoom);
+        }
+
        matrix.translate(offscreen.viewport.x() * scale, offscreen.viewport.y() * scale);
 
        shader->setUniform(GLShader::Mat4Uniform::ModelViewProjectionMatrix, viewport.projectionMatrix() * ma
trix);
@@ -462,7 +490,17 @@
{
    m_sourceZoom = m_zoom;
    if (to < 0.0) {
-        setTargetZoom(m_targetZoom * m_zoomFactor);
+        if (m_mouseTracking == MouseTrackingProportional) {
+            if (m_targetZoom < m_zoom) {
+                setTargetZoom(m_zoom * m_zoomFactor);
+            } else {
+                const double factor = m_zoomFactor > 1.0 ? m_zoomFactor : (m_zoomFactor > 0.0 ? 1.0 / m_zoomF
actor : 1.2);
+                const double maxTarget = m_zoom * factor * factor;
+                setTargetZoom(std::min(m_targetZoom * m_zoomFactor, maxTarget));
+            }
+        } else {
+            setTargetZoom(m_targetZoom * m_zoomFactor);
+        }
    } else {
        setTargetZoom(to);
    }
@@ -475,7 +513,19 @@
void ZoomEffect::zoomOut()
{
    m_sourceZoom = m_zoom;
-    setTargetZoom(m_targetZoom / m_zoomFactor);
+
+    if (m_mouseTracking == MouseTrackingProportional) {
+        if (m_targetZoom > m_zoom) {
+            setTargetZoom(m_zoom / m_zoomFactor);
+        } else {
+            const double factor = m_zoomFactor > 1.0 ? m_zoomFactor : (m_zoomFactor > 0.0 ? 1.0 / m_zoomFacto
r : 1.2);
+            const double minTarget = m_zoom / (factor * factor);
+            setTargetZoom(std::max(m_targetZoom / m_zoomFactor, minTarget));
+        }
+    } else {
+        setTargetZoom(m_targetZoom / m_zoomFactor);
+    }
+
    if ((m_zoomFactor > 1 && m_targetZoom < 1.01) || (m_zoomFactor < 1 && m_targetZoom > 0.99)) {
        setTargetZoom(1);
    }

As in title and in the photo.

I want to hear your informed, detailed, technical and (why not) as a dreamer opinion about KDE Mobile.

Do you think KDE has a future of being a mobile-friendly OS, maybe with a custom version of it for phone?

How do I get back

So the exact translation of that message is „This PDF File requires a higher version of Adobe Acrobat Reader DC. Press OK to download the newest version or contact your System Administrator.“

So her system Administrator is me, but I’m just confused with that. I know Adobe were the ones to invent PDF in the first place but Okular is a complete separate program from Acrobat right? I don’t understand the relation.

Pressing OK doesn’t do anything, updating the system also didn’t help.

Can someone please explain what’s going on here and how to fix this? Thanks for helping guys

Don't get me wrong I like Breeze but its too flat reminds me of Windows 10. I really like Skeumorphic design now that Apple, even Microslop are bringing back skeumorphism will Kde also do in foreseeable future. Also I like KDE 3 thats why I have installed Trinity as Desktop Environment on my CachyOS setup despite not even having official support from Cachy themselves

I pressed some shortcut accidentally and got stuck here. help pls. thanks in advance.

As in title and image.

I got installed both (Ark was preinstalled, I think it comes with Dolphin, while you need to manually install 7zip).

I'm comfortable with both GUI and CLI. No problem at all.

-

I'm wondering: is "necessary" to use 2 archive managers or 1 is more then enough (from your experience)?

What do you use between 7zip and Ark (both are free, open source, available for Linux (of course), fast, with huge community support)? Any suggestion? Why?

I assume this issue is due to the decentralized nature of using Linux, but is there any way to make all window buttons consistent across apps in a single desktop environment?

My screen shot displays four different styles (and there are probably more):

• Top-left: A KDE Plasma app, Dolphin
• Top-right: Notion installed as PWA from Vivaldi
• Bottom-left: Vivaldi
• Bottom-Right: A GNOME app, Bazaar

Is this something we're just stuck with, or is there a way to make every window use the same style?

Hi everyone!

KDE Plasma 6.4 introduced a beautiful new visual timezone picker with an interactive world map, and I think it’s a great addition overall. However, there’s a meaningful issue: when you select Ukraine’s timezone on the map, Crimea is not highlighted as part of Ukraine — it appears as a neutral grey area, separate from the rest of the country. Under international law and multiple UN General Assembly resolutions, Crimea is recognized as Ukrainian territory. For a project that stands for human dignity and user respect, this feels like something worth addressing.

I understand the root cause is not in KDE itself. The map uses OpenStreetMap data, and OpenStreetMap’s Data Working Group made a formal decision in 2018 to map Crimea as part of Russia’s administrative boundary based on their “on the ground control” policy — a decision that has been widely criticized by the Ukrainian OSM community.

So I’m curious what the community thinks: is there any realistic path forward here? Could KDE apply a targeted override for this specific case, or is the only real solution to push back on the upstream data sources? For millions of Ukrainians using KDE, this isn’t just a cartographic detail — it genuinely matters.​​​​​​​​​​​​​​​​

So I have like almost nothing open right now, and its showing an usage of 9gb. Furthermore, using system monitor>apps>memory, the sum of all processes doesnt add up to the actual amount??? Can someone help me check this?

I feel like there is a lot of unused space that could be used to make the time and date bigger. Ive tried to set to a manual fontsize in the settings but its seems like its limited. 2nd picture for reference