Bug 482019 - When in rectangular capture mode, UI disappears after starting to annotate image
Summary: When in rectangular capture mode, UI disappears after starting to annotate image
Status: RESOLVED FIXED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 24.02.0
Platform: Other Linux
: HI major
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords: qt6
: 482592 482758 482814 482850 483110 483211 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-02-29 12:59 UTC by Naxdy
Modified: 2024-03-20 11:26 UTC (History)
17 users (show)

See Also:
Latest Commit:
Version Fixed In: 24.02.1
Sentry Crash Report:


Attachments
Bug showcase (713.82 KB, video/webm)
2024-02-29 20:07 UTC, Naxdy
Details
screen record (1.63 MB, video/mp4)
2024-03-01 20:16 UTC, Onur Ankut
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Naxdy 2024-02-29 12:59:02 UTC
SUMMARY
Since 24.02, launching Spectacle in rectangular region mode and beginning to annotate the picture causes the UI to disappear in an unrecoverable manner.


STEPS TO REPRODUCE
1. Open Spectacle in rectangular region mode (via keyboard shortcut)
2. Drag out any region on the screen
3. Begin to annotate (e.g. use the highlight marker to highlight something)

OBSERVED RESULT
Spectacle's UI disappears and doesn't return, even upon finishing to annotate

EXPECTED RESULT
EITHER: Spectacle's UI disappears while annotating, and then returns; OR: Spectacle's UI never disappears

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: NixOS
(available in About System)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2 

ADDITIONAL INFORMATION
This happened fairly recently, I remember at least rc1 not having this problem.
Comment 1 Noah Davis 2024-02-29 20:02:59 UTC
I'm currently unable to reproduce this.
Comment 2 Naxdy 2024-02-29 20:07:09 UTC
Created attachment 166216 [details]
Bug showcase
Comment 3 Naxdy 2024-02-29 20:13:24 UTC
Journal output (probably not useful)

Feb 29 21:12:05 nxnix spectacle[1161952]: libva info: VA-API version 1.20.0
Feb 29 21:12:05 nxnix spectacle[1161952]: libva info: Trying to open /run/opengl-driver/lib/dri/radeonsi_drv_video.so
Feb 29 21:12:05 nxnix spectacle[1161952]: libva info: Found init function __vaDriverInit_1_20
Feb 29 21:12:05 nxnix spectacle[1161952]: libva info: va_openDriver() returns 0
Feb 29 21:12:05 nxnix spectacle[1161952]: kpipewire_record_logging: VAAPI: Display initialized
Feb 29 21:12:05 nxnix spectacle[1161952]: kpipewire_record_logging: VAAPI: API version 1 . 20
Feb 29 21:12:05 nxnix spectacle[1161952]: kpipewire_record_logging: VAAPI: Mesa Gallium driver 24.0.1 for AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 16.0.6, DRM 3.57, 6.7.6-zen1) in use for device "/dev/dri/renderD128"
Feb 29 21:12:05 nxnix spectacle[1161952]: qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
Comment 4 Nate Graham 2024-03-01 19:36:37 UTC
I also can't reproduce it. I suspect a GPU driver glitch somewhere. :/
Comment 5 Naxdy 2024-03-01 19:41:27 UTC
Happens for me on multiple machines (AMD 7900 XTX, AMD integrated GPU, Intel integrated GPU), so I think a driver issue is unlikely.

Could be NixOS related perhaps? Would be a very weird bug to be introduced by packaging however.
Comment 6 Onur Ankut 2024-03-01 20:15:53 UTC
I can reproduce this. I'm on Arch and I installed Plasma 6 from extra-testing repo. I have R5 5600H's APU as a gpu unit. Screen record is available as an attachment.
Comment 7 Onur Ankut 2024-03-01 20:16:13 UTC
Created attachment 166273 [details]
screen record
Comment 8 ZeroGo 2024-03-04 06:49:09 UTC
I can reproduce this issue and I am using KDE neon with AMD Ryzen 7 7840H w/ Radeon 780M Graphics.
Comment 9 Nate Graham 2024-03-07 23:10:16 UTC
*** Bug 482592 has been marked as a duplicate of this bug. ***
Comment 10 Nate Graham 2024-03-07 23:10:19 UTC
*** Bug 482758 has been marked as a duplicate of this bug. ***
Comment 11 Nate Graham 2024-03-07 23:10:56 UTC
Marking as confirmed based on duplicate reports.
Comment 12 Jet 2024-03-07 23:13:58 UTC
(In reply to Naxdy from comment #5)
> Happens for me on multiple machines (AMD 7900 XTX, AMD integrated GPU, Intel
> integrated GPU), so I think a driver issue is unlikely.
> 
> Could be NixOS related perhaps? Would be a very weird bug to be introduced
> by packaging however.

I got this on both my physical machines (Both Arch, one AMD gfx, other one Intel gfx) and a VM with virtio gfx
Comment 13 Nate Graham 2024-03-08 06:25:03 UTC
*** Bug 482814 has been marked as a duplicate of this bug. ***
Comment 14 Nate Graham 2024-03-10 20:53:03 UTC
*** Bug 482850 has been marked as a duplicate of this bug. ***
Comment 15 Nate Graham 2024-03-11 20:18:07 UTC
*** Bug 483211 has been marked as a duplicate of this bug. ***
Comment 16 Nate Graham 2024-03-11 20:18:30 UTC
*** Bug 483110 has been marked as a duplicate of this bug. ***
Comment 17 Jakob Petsovits 2024-03-12 00:20:59 UTC
I'm not able to reproduce this in my Wayland dev session.

I am, however, able to reproduce it in my Arch-packaged Wayland session, on the same system, just switching between two different users.

So I'd say we can safely eliminate GPU driver bugs from the list of possible causes. Here's a version comparison.

spectacle in my dev session: built with commit 87108b1c05529bab9aaccbd119b39a95e914e6d9 (from Mar 3)
kwin_wayland in my dev session: built with commit 3b2878859222a6e5488a1bde9e3f6f474e963f67 (also Mar 3)

Installed Arch package for Spectacle: 24.02.0-2 (build date: Feb 23)
Installed Arch package for kwin: 6.0.1-1 (build date: Mar 6)
Comment 18 Jakob Petsovits 2024-03-12 00:35:07 UTC
(In reply to Jakob Petsovits from comment #17)
> spectacle in my dev session: built with commit 87108b1c05529bab9aaccbd119b39a95e914e6d9 (from Mar 3)
> Installed Arch package for Spectacle: 24.02.0-2 (build date: Feb 23)

I looked through the list of commits between Feb 23 and Mar 3. Commit 1b309ee3d56f1aaed08d636b20490d9af10f21c1 caught my eye, so I tried reverting that. Voilà, a quick rebuild later I can reproduce the bug also in my dev session.

Meaning it's already fixed, and that's why KDE devs weren't able to reproduce it.

So yeah, I think the answer here is to update to a version that includes commit 1b309ee3d56f1aaed08d636b20490d9af10f21c1. As per https://community.kde.org/Schedules/KDE_Gear_24.02_Schedule, it looks like KDE Gear 24.02.1 is scheduled to release on Mar 18. Perhaps one or the other distro maintainer will pick it up before then.
Comment 19 Naxdy 2024-03-12 07:35:50 UTC
Cherrypicked 1b309ee3d56f1aaed08d636b20490d9af10f21c1 into my installation and it does indeed solve the problem. Many thanks!
Comment 20 WKoA 2024-03-13 19:36:42 UTC
I just noticed this issue now on my fully up to date system.
Comment 21 Jet 2024-03-20 11:24:59 UTC
In the bug details it says:

Version fixed in: 24.0.1

But it still occurs in 24.02.0
Comment 22 Naxdy 2024-03-20 11:26:37 UTC
Pretty sure it was meant to say 24.02.1, went ahead and changed it.