| Summary: | [Wayland+Plasma6] All actions delayed in Krita after opening document | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | deresiant |
| Component: | * Unknown | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | dimula73, info |
| Priority: | NOR | Keywords: | qt6 |
| Version First Reported In: | git master (please specify the git hash!) | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | video of opening krita and drawing a line. | ||
|
Description
deresiant
2024-02-20 10:41:25 UTC
This happens whether or not canvas hardware acceleration is enabled or not and happens on both my nvidia and amd gpus. If i have canvas hardware acceleration enabled then more of krita goes black like it's not updating the screen. > Graphics Platform: Wayland As far as I know, Krita is still not a native Wayland app and runs in a XWindows, an overlay that might bring its own share of issues. It reminds me a report I met on Krita-Artist forum : https://krita-artists.org/t/sometimes-krita-will-launch-in-a-bugged-state-and-the-only-way-to-fix-it-is-to-restart-my-computer/84044/1 especially the part of this reporter telling "application it will freeze for 5+ seconds". After switching back to stable on both krita and kde plasma, this issue is no where near as bad as in the originally attached video so I'm going to close this. |