Bug 507307 - crash when moving layer in krita
Summary: crash when moving layer in krita
Status: REPORTED
Alias: None
Product: krita
Classification: Applications
Component: Layer Stack (other bugs)
Version First Reported In: 5.2.11
Platform: Flatpak Linux
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-21 13:35 UTC by Ubiratan
Modified: 2025-07-22 03:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
print of the bug in fedora gnome (1.45 MB, image/png)
2025-07-21 13:35 UTC, Ubiratan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ubiratan 2025-07-21 13:35:18 UTC
Created attachment 183392 [details]
print of the bug in fedora gnome

SUMMARY

STEPS TO REPRODUCE
1. Open Krita
2. Create a new .kra file
3. Create a second layer
4. Try dragging the newly created layer below the old one or dragging it above the old one using the Wacom tablet pen

OBSERVED RESULT
The Krita window freezes and the layer remains stuck on the screen. You can only unlock it by right-clicking. Another detail: after completing the process mentioned above, the Krita screen prevents the mouse from clicking on the buttons. I also noticed this bug in Ubuntu 25.04. Interestingly, it doesn't appear in Zorin OS 17.3.

EXPECTED RESULT
With the tablet pen, you can drag the selected layer above or below the others in the stack. And the mouse can click on the file buttons, for example.

SOFTWARE/VERSIONS

Krita: 5.2.11 (Flatpak)

ADDITIONAL INFORMATION

Motherboard: GIGABYTE B450M GAMING
Linux: Fedora Linux 42 (Workstation Edition) x86_64
Kernel: Linux 6.15.6-200.fc42.x86_64
Shell: bash 5.2.37
FROM: GNOME 48.3
WM: Mutter (Wayland)
Terminal: Ptyxis 48.4
CPU: AMD Ryzen 5 5500 (12) @ 4.27 GHz
GPU: AMD Radeon RX 550/550 Series [Discrete]
Memory: 3.06 GiB / 15.48 GiB (20%)
Swap: 0 B/8.00 GiB (0%)
Disk (/): 46.97 GiB / 475.35 GiB (10%) - btrfs
Digitizing tablet: Wacom model CTL-472
Comment 1 Halla Rempt 2025-07-21 14:17:39 UTC
It sounds like either a Qt platform plugin problem or a window manager bug... Can you check whether you can reproduce this with the 5.2.11 appimage?
Comment 2 Ubiratan 2025-07-21 15:09:53 UTC
(In reply to Halla Rempt from comment #1)
> It sounds like either a Qt platform plugin problem or a window manager
> bug... Can you check whether you can reproduce this with the 5.2.11 appimage?

did as you requested. I tested it on the krita appimage version 5.2.11 and the problem persisted.
Comment 3 Bug Janitor Service 2025-07-22 03:47:12 UTC
๐Ÿ›๐Ÿงน Thanks for your comment!

Automatically switching the status to REPORTED so the team can perform further triage.

In the future you may also do this yourself when providing needed information.