Yeah I know but they are also not providing any fallback for people hit by those bugs. Testing can be done without harming user workflows. And fedora punishing and forcing users will not get those bugs magically fixed. I am not sure some of these will be fixed now before fedora 40. Anyway Fedora can do whatever they want. My wish is to get these bugs more attention.
Yeah you are right and people who were using fedora will need to move distribution suddenly. Actually Fedora is a bad choice for production for this reason, we never know when fedora will ditch you and when we complain about this fedora fanboys will only say why did you choose fedora or they will say just change distribution. So taking that advice I already switched from fedora and I no longer recommend it for any artists use. After all there are bazzillion of distros to choose from.
Again as I said the post is not about fedora itself, it is about the false premise that unnecessary urgency fixes bugs, in this case it is did not do anything and this post is to get the people to notice these bugs to get them fixed
I disagree that Fedora doing this did nothing for the development. It generates bug reports, which in turn generates fixes. Sure, the fixes might not make it into Fedora 40 or even 41, but it helps the Plasma developers see what issues there still are out there as bug reports pop up.
The plasma devs likely don’t have a graphics tablet to test on, so they rely on the community to find these issues and test the fixes.
I am not against fedora pushing things and fedora helping in testing things it is its job as a test bed. Fedora does not give any fallback to people affected that is the issue. Again I do not use fedora now so that is not my issue what they do.
The plasma devs likely don’t have a graphics tablet to test on, so they rely on the community to find these issues and test the fixes.
Some of these things were communicated in 2019 (phabricator.kde.org/T11660) and again during artist and plasma developer meeting too. You can read about it here (phabricator.kde.org/T14971) So fedora is not the only medium by which bugs and requirement are conveyed to developers.
No they have not ported old KCM but created a new one from scratch. Hence any shortcoming or lack of feature is considered as wishlist and extra thing to implement.
So Plasma6 X.org has less graphic tablet settings, right?
Plasma 6 xorg might have the X11 KCm which is the most featureful configuration frontend for graphic tablet on linux. It is on par with windows and wacoms utility. KCM on wayland is not so much.
I would call that a regression and not a wishlist? You can for sure ask to tag those issues correctly.
I had changed the severity once but it was reverted back and then other discussion about this was not entertained you can check the bug reports see the comments marked as spam.
they are also not providing any fallback for people hit by those bugs.
The fallback is announcing this in the release notes, so users depending on removed features can wait with the upgrade until the issues are fixed or move to another distro.
Backwards compatibility is nice and all, but at some point you’ll have to break things or you’ll end up like Windows, where the current version still includes user-visible GUI elements released 33 years ago.
The fallback is announcing this in the release notes, so users depending on removed features can wait with the upgrade until the issues are fixed or move to another distro.
Yeah I understand hence I won’t be advising or suggesting any artist to use fedora :)
Yeah and i think x11 itself will be available until 2032 on redhat atleast , that is not the issue. Artist can use old distros too but it would be nice to see these things get attention after all linux is for everyone and not just for developers right.
no more frames within frames! Instead Breeze-themed apps adopt the clean design of modern Kirigami apps, with views separated from one another with single-pixel lines!
Does this talk about that little blue square that is inside of dolphin where the folders reside?
@mokazemi
You may want to take a look at the @tuxedocomputers repositories, that's how I get my #Firefox.
(Full disclosure: I bought a machine with it preinstalled) @JTskulk
Why use flatpak when you can just use deb repositories?
I listed one way that I know works because that’s how I use Firefox on my Steam Deck (which in turn uses Plasma 5 as desktop, same as Kubuntu). If a deb package from some PPA works just as well: great.
In the future, if you plan to add sync, consider reimplementing Joplin sync algorithm
That would give you tens of thousands of passionate users, dedicated FOSS server as well as webdav/s3/dropbox/onedrive client sync ability, webclipper and a lot of support to navigate future issues/roadmap
If you ever decide to do that, there's even a plan to repackage the algorithm as a standalone library
I'm not to much worried about the syntax, KleverNotes follows Common Mark, so as long as the other app follows it too (which it should) this part is okay
I'm more worried about directory structure and things like that, but I'll have to read more about both API before I can really say anything concrete on this subject
By the way, if you have something in Joplin that you really can't live without, let me know, I'm always looking for pottential features :)
I... don't think I have ever seen it do that automatically unless I missed some steps in the installation guide...? most of the time I just created the partitions I needed. I did a quick CTRL + F on tmpfs or tmp but not seeing anything...
Anyhow, I don't see on my desktop which still has Arch Linux installed which I want to move to KDE Neon but extremely lazy when you have an immense backup to do...
It's default since systemd afaik. I think systemd-tmpfiles manages this. It's never been a problem for me, it pretty much remains fairly empty most of the time. Most things like sockets are in /run which is also tmpfs.
KDE
Top