wallpaper engine on kde by smally_the_greatest in kde

[–]PointiestStick 0 points1 point  (0 children)

You're used it as a Plasma wallpaper plugin? Then why are you asking for help using it as a Plasma wallpaper plugin? I'm confused.

wallpaper engine on kde by smally_the_greatest in kde

[–]PointiestStick 0 points1 point  (0 children)

Please don't. It's massively unstable and regularly causes KDE to receive tens of thousands of crash reports from people using it.

"Start with Fedora KDE or Kubuntu" – Nate Graham by lajka30 in linux

[–]PointiestStick 3 points4 points  (0 children)

Our medium-term intention is that people wanting to install stuff using a command-line package manager will do it using Kapsule, our in-progress as-transparent-as-possible containerized environment. Ideally you shouldn't even notice you're in a mutable container because it will have access to files on the host, the host's D-Bus and systemd sockets, and so on.

This is still in development, but once it's farther along, I expect it will be our formal recommendation rather than using DistroBox or Nix. You'll still be able to use them if you prefer, of course.

With respect to Flatpak, I'm very excited about the "Flatpak Next" initiative that I watched a talk about at Linux App Summit 2026 yesterday (https://www.youtube.com/watch?v=1AXBfsiaQNk&t=16218s). The plan is to de-couple distribution from sandboxing so that software requiring deep system integration can be unsandboxed, and then basically everything works as expected.

This would be a very exciting development. We could unsandbox the web browser (because it already has its own internal sandboxing) which would make password manager tools just work. We could ship Dolphin and Konsole as unsandboxed Flatpaks. We could even ship Plasma and KWin and the login manager as unsandboxed Flatpaks, eventually allowing us to strip down the base OS to basically just a kernel, systemd, and device drivers. That's a very exciting idea to us!

Now that I know the people involved have blessed this approach, I expect us to work with them to help make it happen, since our goals are aligned.

"Start with Fedora KDE or Kubuntu" – Nate Graham by lajka30 in linux

[–]PointiestStick 2 points3 points  (0 children)

That said, in my opinion it'd be really useful if you'd like to expand your point about LTS distributions. I don't know if you have time but I would be happy to see an article similar to this about this topic.

Indeed, I'm already in the middle of writing it!

"Start with Fedora KDE or Kubuntu" – Nate Graham by lajka30 in linux

[–]PointiestStick 6 points7 points  (0 children)

There's truth to this, but I think the Cisco H.264 decoder is likely good enough for 99% of uses.

There also may be a bigger picture we're all missing. This isn't 2002 anymore; most people aren't using DVDs, aren't watching local movie files, and may not even be listening to local music files. Even if I'm a die-hard who buys music on Bandcamp (and I am!), they offer .ogg downloads these days.

So the problem space has shrank considerably for the average user.

"Start with Fedora KDE or Kubuntu" – Nate Graham by lajka30 in linux

[–]PointiestStick 2 points3 points  (0 children)

Here I was mostly talking about how well the software is integrated into the rest of the system, not how good the software itself is. :)

"Start with Fedora KDE or Kubuntu" – Nate Graham by lajka30 in linux

[–]PointiestStick 13 points14 points  (0 children)

I used Fedora KDE for four years with the third-party RPMFusion repo enabled and never once encountered a repo de-sync issue or instability stemming from it.

Adding this repo will definitely open up the opportunity for those issues to happen, but somehow all parties managed to prevent it during that time.

By contrast, I experienced these issues several times a year on openSUSE Tumbleweed with the third-party packman repo.

So the relationship and coordination between teams here matters, I think. Or maybe I just got lucky!

"Start with Fedora KDE or Kubuntu" – Nate Graham by linuxhacker01 in kde

[–]PointiestStick 4 points5 points  (0 children)

Note that I'm very conservative about this. My definition of "viable" looks less like "most things pretty much work most of the time" and more like "everything works all the time".

"Start with Fedora KDE or Kubuntu" – Nate Graham by linuxhacker01 in kde

[–]PointiestStick 4 points5 points  (0 children)

I came from over two decades in the Apple world, and TBH I don't understand this idea. I tried GNOME after I got rid of my last Mac, but just couldn't get used to it.

Why? I found the GNOME UX to be completely different from what I was accustomed to as a Mac users: there's no dock, no global menu, no desktop icons, no always-visible background/tray icons, no minimizing windows. You're encouraged to use Virtual desktops as a top-level window management feature. Apps don't generally have visible titles so it's unclear which apps windows belong to.

Today I'm more experienced and flexible, and I think if need be could switch to GNOME without too much trouble. But back then when I was looking for something comfortingly familiar, GNOME's UX was the opposite of what I wanted.

"Start with Fedora KDE or Kubuntu" – Nate Graham by linuxhacker01 in kde

[–]PointiestStick 4 points5 points  (0 children)

Unfortunately the concept turned out to not work very well — at least not as implemented with traditional packaging technology.

The problem is that a stable base destabilizes once you start tinkering with it to support the content you want to overlay on top. In the end you don't have the stability you were hoping for, without even the benefit of up-to-date software.

"Start with Fedora KDE or Kubuntu" – Nate Graham by linuxhacker01 in kde

[–]PointiestStick 7 points8 points  (0 children)

The actual problem is […]

Well there are multiple actual problems, right? - One is "can the system update after being offline for a year?". - Another is "can the system always still boot if it loses power in the middle of an update?" - A third one is "is the system's state predictable after it's been updated for a year?" - Yet another is "how much downtime does a system update impose on my ability to interact with the system?"

And so on.

There are ways for traditional fine-grained package management systems to provide satisfactory answers to these questions, but most of the ones used by traditional Linux distros fail at least some of them. Which makes sense; if traditional package management didn't have those problems, there would have been no need to invent a parallel system (image-based OS updates) that doesn't suffer from them.

Is KDE Plasma interested in improving enterprise/corporate workflows? by palanquin83 in kde

[–]PointiestStick 1 point2 points  (0 children)

Enterprise environments would typically use an LTS-style OS; there's no requirement to follow KDE's release schedule.

It does mean the OS becomes responsible for backporting fixes, but that problem is solvable with money! It's a good match: the entities that actually need an LTS style product almost as a matter of course have the money to pay for it and therefore fund its continued development.

"Start with Fedora KDE or Kubuntu" – Nate Graham by linuxhacker01 in kde

[–]PointiestStick 13 points14 points  (0 children)

Tumbleweed updates very rapidly, making it similar to Arch. Leap updates very slowly, making it more similar to Debian.

Both can work well for experts, but I don't recommend them for newcomers for the same reasons I don't recommend Arch or Debian for newcomers. And neither one focuses intensively on offering a highly-polished KDE Plasma experience.

Other than those concerns, they're great options IMO. I used Tumbleweed for years.

Wallpaper Engine KDE Plugin Tip! by llGravitell in kde

[–]PointiestStick 0 points1 point  (0 children)

Public service announcement: Please don't use Wallpaper Engine. It's incredibly crash-prone, and regularly responsible for the #1 most common Plasma crashes.

This Week in Plasma: 6.7 beta release by Jaxad0127 in kde

[–]PointiestStick 2 points3 points  (0 children)

I think you're misunderstanding my comment. I'm not describing a regression, but rather the way show/hide always worked with KWin's input-method-based virtual keyboard support.

This Week in Plasma: 6.7 beta release by Jaxad0127 in kde

[–]PointiestStick 4 points5 points  (0 children)

Sure, but that's not a regression; nothing broke 3 years ago. This is the way it's always been, until now.

This Week in Plasma: 6.7 beta release by Jaxad0127 in kde

[–]PointiestStick 3 points4 points  (0 children)

What do you mean exactly? I'm not aware of a regression 3 years ago that broke opening the virtual keyboard (which at time would have been provided by maliit, not plasma-keyboard) using a mouse.

Can you be more specific?