Thanks for the tip. Without kwindowprop I will have to wait though.
Stopwatch1986
joined 2 years ago
I am on Debian 13 KDE Plasma with Wayland. I tried kdotool as @Erwan suggests but as expected xprop doesn't return anything. Apparently, I will also have to use kwindowprop which will take a while to appear on Debian Stable.
There used to be a thing in KDE where you could execute actions and macros based on window titles
Now, that would be nice but unless there is another way it looks like I will have to wait.
Thanks for the help.
My understanding is that sandboxing is not mandatory for Snaps, but it is for flatpaks. Some of the Snap code not being open source, and generally the technology being centralised around Canonical apparently is off-putting for some.
I share your concerns about trust. With flatpaks we can still read the source and commits, but not many will or can do this every time they install and update software anyway. In this sense, we have little choice but to trust the verified developer and the community, who may of course be compromised too, regardless of distribution method. I suppose with flatpaks we have to check permissions and make them as restrictive as possible.
This ranking is very close to how I see this. Anything after Docker/Podman is out unless I absolutely need an application in which case keeping a record of dependencies is a good idea. But I want to know the work system will absolutely start in the morning hours from a deadline. Avoiding single points of failure is another way of course (ie multiple systems, OSes, backups, password managers etc).
I remember the time applications came on floppies, 640kb of RAM was indeed enough for anyone, and people competed in writing games in one line of BASIC (yes, that was 255 characters code max). Containers feel horribly wasteful to me, but I came to accept there aren't many realistic alternatives for the average users who need reliability with zero effort. Making a note of dependencies in case you need to backtrack is not a realistic proposition for most. But I can understand why some users will want full control and a lean setup.
I agree with the popular view that Debian Stable + KDE Plasma + Flatpaks (or Appimage, Docker) strikes a balance between system reliability and freshness in selected applications when that counts. I may be missing updates for KDE Plasma but v6 is quite mature so I don't mind. I know storage is cheap but I am instinctively uneasy with containerisation as it's done by Flatpaks etc because of the duplication you get with all-in. But if that's the price of reliability, so be it. It's just that sometimes there is only a PPA or a .deb, which is why I asked.
EDIT: I just tried distrobox for the first time. It is amazing how efficient it is. I ran Firefox on Arch and I couldn't tell the difference in resources. Amazing really.
I have been preparing the move to Linux for years, switching to FOSS cross-platform applications on Windows and installing Linux on my secondary machines. A few weeks ago I made my work machine dual boot with the intention to remove Windows completely. I find that I never log into Windows at all already, and my Debian Trixie + KDE Plasma experience is the same in many areas (mainly because I use the same applications as before) and vastly better in others.
There were issues I had to solve but nothing major. It is true that Windows has been very stable and efficient for me, but people forget that when this happens it is the result of many years of learning, fine-tuning, decluttering and getting used to Windows. You get to that stage with Linux very quickly, and it feels much better.
True for most scenarios. Specifically with Syncthing, I find that it rarely fails and when it does there are good reasons and I need to do something about it (eg I used the wrong version config.xml recently trying to migrate between Syncthing setups).
You learn something new every day here ;) The good thing about kdialog is you can't miss it. Thanks.
I have tried Syncthingtray and Syncthingy. I found the former did too much that I never used, and the latter was an unnecessary process doing very little while always running and adding another icon to the tray. For me periodic checking with a script is enough and more efficient for the rare situation where Syncthing crashes of fails to start.
view more: next ›
Windows refugee here. I installed Debian 13 with KDE Plasma on my main machine four months ago and I am still ironing out issues. Eg CUPS was asking me to login all the time and didn't accept my credentials. After some days researching I discovered I had to log in as root. Then, I discovered I didn't have root credentials for some reason. I had to create them and then add my local user to a group! Just to be able to use my home printer.
Or suddenly my clock was 62 minutes off. I discovered the NTP service was never set up properly and I had to install chrony.
I don't see how I could have avoided using the terminal. These are only a couple of examples. No deal-breakers and on this occasion I had the time and determination to resolve them. I could have easily given up.