enough is enough…I’m going to give up Krita…after all these years there is no solution to the problem…maybe another time, I’ll learn more about Clipstudio, it’s really annoying…but KRITA solves the problem…
see you soon or something
Since this is just an announcement of your decision to leave Krita, rather than a request for help, I’ve moved it to the Off-Topic section as it doesn’t contain enough information for Artists Feedback & Testing.
Michelist
What problem are you having, exactly?
3 Likes
I’ve now tested a few things again, all monitors off, just the Wcom Touch and other configurations. It’s the touch, when I turn it on it starts acting up after a while or even straight away… I haven’t been able to get rid of it for a few hours.
My mouse pointer flashes very quickly and the touch is unusable, I have everything up to date in terms of drivers, I’ve also tried older drivers, unfortunately without success…
I don’t know what to do.
1 Like
That’s some info, but you have to provide more if you want to see this fixed.
You need to offer more information still. Like: are you using Windows?? How can we guess?
It MATTERS because only in windows is there a setting to switch between Windows 8+ Pointer Input and Wintab to see which works better for you.
It might be frustrating to come back here and see one by one more things we’re asking to clarify on but keep in mind there are whole LIST of information that is required so I thought I’d just get to the point.
You’re dealing with a buggy Wacom Touch in Krita—the mouse pointer flickers, and touch stops working. You’ve tried turning it off, updating drivers, rolling back drivers, and it still doesn’t work.
Here’s how to report bugs like this so that it has the best chance of a fix:
1. Clearly Describe the Bug
Instead of saying:
“Touch is unusable, nothing works, I give up!”
Write something like:
“When Wacom Touch is enabled, my cursor flickers rapidly and the touch function stops working after a while. Disabling touch stops the issue, but I need it enabled.” Good on you for steering more towards this kind of explanation, as this can be far more helpful.
Why? This gives a clear description of the problem instead of just frustration.
2. Include Your System Information
Before reporting, gather these details:
- Krita version: (Find this in Help > About Krita)
- Operating System: (Windows 10, Windows 11, Linux?)
- Tablet Model: (e.g., Wacom Intuos Pro, Cintiq 16, (some require tweaks))
- Tablet Driver Version: (Check Wacom Desktop Center)
- Are you using multiple monitors? (Yes/No)
Why? Different setups cause different bugs. Krita developers can’t reproduce the issue unless they know what system you’re using.
3. Explain How to Trigger the Bug
Example of a step-by-step bug report:
- Connect Wacom Intuos Pro and enable touch.
- Open Krita and create a new document.
- Move the pen/mouse—everything works fine.
- Touch the tablet with your fingers → The cursor starts flickering rapidly.
- Touch stops working completely, making it unusable.
Why? If a developer can’t make the bug happen on their system, they can’t fix it. It’s hard enough with the difference in hardware and OS.
4. Explain What Should Happen vs. What Happens
Expected Behavior: Touch should work smoothly without affecting the cursor or performance.
Actual Behavior: Cursor flickers rapidly, and touch stops responding after a short time.
Why? Helps devs understand what’s broken and what’s supposed to happen.
5. Gather Logs & Screenshots
If Krita crashes, get logs:
- Open Help > Show Krita Log for Bug Reports
- Copy the log and attach it to your report.
If the bug doesn’t crash Krita, record a short video showing the issue.
Why? A log is text file created by krita to report on all of what it is doing when ever it can. That info is essential in seeing the problem in action to help developers understand faster when the issue occurs and what’s causing it.
6. Report the Bug in the Right Place
Now that you have everything, file an official report:
KDE Bug Tracker
Why? Posting complaints on a forum Might not get it fixed, but a proper report most likely will. Here, we can confirm an issue exists… there’s a chance that either a dev MIGHT come across it, or a community member might want to fix the issue, but generally the bug tracker is the core team’s workstation area for addressing problems.
7. Be Patient & Follow Up
- Check for responses—developers might ask for more info.
- Try updates—a fix could come in a new Krita version.
Final Reminder: A Clear Bug Report = Faster Fixes
“Touch doesn’t work! I give up!” = Ignored.
“Cursor flickers and touch stops working on Wacom Intuos Pro with latest drivers in Krita 5.2. Issue happens when touch is enabled.” = Gets fixed faster.
Help Krita improve by reporting bugs the right way!
Good luck with your trouble,
-S
10 Likes
1…cool thing, thank you very much, maybe that could be the solution if you install the latest drivers? However, I have now used tablet drivers from 5 years ago and it has been running quite stable so far, I no longer have these crashes…until now =)
Did you skim over entire sections of what we carefully explained to you?
Yeah the details we asked you for mattered, doesn’t matter if you don’t care.
Just go use Clip Studio.
I’ve been doing this commercially for 14 years and I don’t know what to say. We made it clear what we needed. Yet you seem to have ignored that and provided just one vague, unusable fact like you know better. So, off you go. That lack of trust or laziness or what ever has cost you a real solution. I’ll leave this one to someone with endless patience—if such a person exists.
Bug reports are hard.
You make them impossible by not respecting the process.
If you think any software—Krita, Clip Studio, or any professional tool—will just magically work without structured bug reports, you’re in for a rude awakening. Every single industry support channel will demand exactly what was asked of you here.
Let this be a learning moment.
I’m out.
-S
EDIT:
LOL, I basically had to stalk his profile to get this information FINALLY!!
‘Operating System and GPU: WIN 11 and GeForce 3060 Dual’
Still not enough to form a full bug report, but it’s hilarious that he didn’t just ‘Ctrl-P’, ‘Ctrl-V’ to do the minimum of answering ONE of our questions.
If you don’t laugh, you cry.
-S
We should really stop giving attention to threads that are so obviously not worth the effort. If someone has already given up and gives no specifics but general discontent, we can just leave it at that. It is not like he was even asking for assistance, but just come around to complain.
Going into these threads with the kindness of our hearts because we want to help is really just a waste of our efforts. Krita is not for everyone, is not perfect and neither is any other software. If someone prefers to use another program, fine. I use CSP, Krita, Affinity and lots more. Just use whatever you can work with.
1 Like
There is some very helpful info in this thread but I’m not sure that is what OP is looking for. This seems to be an announcement that they are leaving Krita. Maybe we should just leave it at that.
I’m tempted to close the topic but I don’t want to add to anyone’s frustration.
4 Likes
OP will probably be back next week. There’s a phenomenon on the internet called “quitting IRC forever” where when one makes a big announcement of their departure, they’ll be back in a matter of days (usually with a new account).
Or OP was trolling. Your call.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.