I've used KDE on a Thinkpad T60, it's about 17 years old, has 3GB of RAM, and a Core Duo. It ran surprisingly well. Replacing the HDD with a SSD can also make a noticeable difference, so you should consider that if you haven't already. I also turned off a lot of the animations and effects for better performance.
@boredsquirrel
While tedious, those effects can all be turned off in *"Workspace Effects" or whatever it's called. Not at my laptop to check. @Mint_Raccoon
The only effects relevant for performance are blur and background contrast. Turn those off if you feel the system is slow, maybe increase the animation speed and you’re done
I discovered kdenlive a few months ago and it’s amazing! I can’t believe I didn’t even know it existed. How come it’s not as popular as paid options? It even runs on Windows
It’s not quite as feature rich as something like davinci resolve, which is straight up movie industry level software, yet it’s free to use.
And resolve actually runs on Linux, too.
KDEnlive has also had some bugs over years. I personally started editing with it first, but ditched it for resolve due to a bug that would cause audio and video to gradually go out of sync over time, but only when actually rendering, and there was literally no way to work around It. I had no way to turn my completed edit into an actual usable video file…
I am back to using it, and it has improved a ton. It’s extremely capable and has all the features most editing projects would ever need.
kscreen-doctor -o
Then adjust the below command accordingly : kscreen-doctor output.1.hdr.disable
Make sure you go open a bug report.
When you do, you can use hw-probe and run : sudo -E hw-probe -all -upload -dump-acpi -decode-acpi
And use the given link in your BR.
I see you got it fixed.
When you run hw-prope make sure your offending monitor is connected. hw-prope will help identify the monitor by hardware ID which is used in various areas like kernel space and will help with identifying the exact model of the problem monitor hopefully allowing for devs to reproduce the bug in a lab environment.
Looking through the probe logs, and seeing that your monitor is using EISA bus and works fine without HDR, there doesn’t appear to be any issues on the Linux side of things. My guess is that they didn’t implement HDR on the monitors side exactly to spec and that’s where the problem resides. So, in this sense some monitor specific quirk fixup code is needed on the Linux side of things to get it working properly. If the devs ask any additional steps from you, be sure to do it and provide feedback.
Don’t create a social media hype of something before discussing it with Plasma devs. That’s obviously going to antagonise people, and puts us in an awkward situation afterwards.
Looks like this “vote” is not really official and blindsided the devs a bit.
It would be nice if it were at least configurable to set as the default extract option. If I had to take a guess, it’d be that it’s not the default option because the amount of single files before needing a subfolder could vary between different people. Some folks may want only one, and others may be fine if it goes up to say 3. However, I suppose that could also just be a configurable option.
That being said, I’ve at the very least developed the muscle memory to always click that option no matter what. I can’t tell by your comment if you weren’t aware of the feature, but if not then hopefully it can be of use to you moving forward as well!
Want more exposure? Easy: Treat Steam Deck’s game mode as first class citizen for Kirigami apps and release those on Steam, most notably the Angelfish web browser. Too bad whenever I inquired whether that’s even under consideration, the replies I’ve got were along the lines of “just launch desktop mode”.
I tried the beta out for a week, and overall it was fine. One super annoying thing I can into I couldnt figure out though was paste was borked. I could copy text, see it in the clipboard cache, but when trying to paste, the window I would try to paste into (several apps) would freeze for 30 seconds or so, and then not paste. Very odd.
Yes. Because it comes in two parts. The OS level package and the browser extension, if the extension can’t communicate with the OS level package then it won’t work.
Maybe because not every system is Debian, and Plasma has to work on systems that either don’t have /usr/share/i18n/supported or put is somewhere else?
I manage a project that encounters this sort of thing regularly; my biggest problem is terminfo entries. Not all distributions contain all of the same terminfos. It is one of the biggest source of bug reports my project gets. I’ve been considering just embedding all of the terminfos in my project, just so I know they’ll all be there on every system it’s installed.
I don’t know this is Plasma’s reason for including their own list, but it could easily be. It could also be because those are the locales Plasma supports, and it may not support every locale that might be in the distro system list.
I don’t know what you mean by that. It’s a locale, it has nothing to do with KDE or Plasma. It doesn’t even need a desktop environment. Plasma Settings will just pick up the ones you have installed.
I don’t know what you mean by that. It’s a locale, it has nothing to do with KDE or Plasma. It doesn’t even need a desktop environment. Plasma Settings will just pick up the ones you have installed.
I used to think so too.
However, Plasma apparently has its own list of locales not identical to the system one. (See the first post)
kde
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.