I mean, Krita actually works on Wayland because of XWayland, but having wrong cursors when using a graphic tablet is more problematic than it sounds.
Sometimes I’m drawing with a brush, then switch to the Move tool accidentally, but the cursor doesn’t update, and I end moving everything because the cursor shows that I’m still using the brush.
I looked at the KDE Bugtracking System and Krita’s repo, but I don’t see anything speaking of Wayland support, apart from multiple reports of this same issue.
PS: I sent this same topic to KDE Discuss website, but decided to send it here too.
Krita will have to support Wayland eventually, but there’s not any specific plans for that right now. Wayland’s support for some features Krita relys on is still evolving, and Krita developers are busy with other things.
Unless the artist crowd voices their concerns the developers in linux community will think that linux is only used by gamers and grandmas and developers like themselves. so the workflow will be ignored and other things will be prioritized like HDR over real colour management tools.
Hi @Alessandro_D_Arcange I am moving your question here in this thread since both seem to be same.
To answer your question, the team is currently gearing up for porting Krita to Qt6 any wayland plans will likely materialize after that. Until then Wayland is not officially supported.
Yes. And if someone can help the team to do it quickly then please join the irc and discuss things. Meanwhile use the distro which will have fallback like debian etc. The team is small, no amount of hype and urgency will help. If the distros feel that their user needs are not a priority then that is their problem.
In a scenario where all the distribution drop X11 tomorrow user will migrate to windows, BSD Macos (even haiku) etc because krita runs great in those platforms. Users should use an operating system which doesn’t break their workflow and pull the rug under their feet. Doing artwork is important for artists not wayland not linux etc so they will chose what helps them the most.
Krita started as a linux app. The development is primarily done on linux. So eventually wayland support will arrive. But there is no point in hurrying it. Red hat will support xorg till 2032 debian till 2028. So there is time and it is not good to hype things up. If your distro does not support xorg choose a different one.
Wayland is still not ready for artists, though. Tablet support is lacking, and the color management protocol isn’t even written down yet. How is a professional graphic application supposed to support a platform that doesn’t have a professional color management yet? Colors are pretty important when making art. And we were trying to be involved in the process of creating the protocol, but our suggestions were not added to the protocol, so there is a chance we won’t even be able to guarantee a proper color management on Wayland at all, we might need to rely on correct implementations on a few specific Wayland implementations like possibly KWin.
In the meantime, talking to the distributions to still allow a way to install XOrg would be a great idea. I’m sure Krita isn’t the only application that isn’t using Wayland yet, so distributions dropping it completely - instead of, for example, making it non-default or requiring the user to install it later - is imho not a good decision. Maybe I don’t understand something in that community.
Don’t the Wayland devs understand that if Linux is to remain an alternative to commercial operating systems, then these functions must also be integrated into Wayland, otherwise all those who depend on color management, for example, will have to turn their backs on Linux? I cannot understand this short-sightedness!
Well I use Krita in Wayland and the only thing that really bothers me now is the cursor problem, my tablet works fine in wayland, there are even already two tools that replace xsetwacom, I think that for wayland to move forward you have to do some pushing as @raghukamath says.
ok as i said i m not using wayland but for what i’m reading seems like wayland after all of these years still missing basic stuff that it’s really crazy to me…i would like to help but unfortunately i don’t have enough technical skill
For the cursor issue, the bug report linked in the bug report linked by raghukamath suggests it’s an issue between Qt and Wayland. If it were to get fixed on the Qt side, Krita wouldn’t get the fix without porting the fix to the older version of Qt or updating Qt- which is one of the reasons that updating to Qt6 is a main priority.
It may seem counterintuitive, but technical skills are rarely the main obstacle… Sure, you need people who know how to do something, but I think the main problem is the politics, reaching an agreement, or deciding the direction of the project
Not talking about the Wayland situation specifically (I don’t know anything), but I’m taking in general.
The main problem it’s not Qt, is XWayland because I did some tests with XWayland and my Wacom tablet with some programs made in Qt and GTK, and the result is the same.
I asked about Wayland support because I really wanted to know about it, and if is there any chance I can help to add a native Wayland support for Krita (I’m a developer), but I don’t know how to reach the developers or where to start.
Also, changing my distro and having to start from scratch again only to use X11 is not a good option, it feels like asking someone to move to another house because of the place.
I’m using my Wacom tablet in Fedora 40 with Wayland, and they work like a charm, even Wacom mentioned that Wayland was built with Wacom tablets in mind in their website. My only main problem is the XWayland cursor issue, as I mentioned here.
You reached at least 3 developer with your post, but those are krita developer.
As I understand it is a problem between qt and wayland. Krita only uses qt, so it is in my opinion, better to ask wayland or qt developer about that. If it would be fixed in krita it would be fixing a symptom and if a fix finally come through qt and wayland it could be, that it creates a bug in krita.
@BeARToys, Qt ≥ 5 has supported Wayland for a long time. This is a concern of the Krita developers, not the Qt ones. They’ll contact Qt when they encounter a problem with it.
