Bug 495979

Summary:	Amarok uses the wrong cursor on Plasma 6.2
Product:	[Applications] amarok	Reporter:	cameronbosch
Component:	general	Assignee:	Amarok Bugs <amarok-bugs-null>
Status:	RESOLVED FIXED
Severity:	minor	CC:	tuomas
Priority:	NOR
Version First Reported In:	3.1.1
Target Milestone:	kf5
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	A short screen capture of this Qt bug.

Description cameronbosch 2024-11-08 17:09:22 UTC

SUMMARY
When using the Amarok flatpak on KDE Plasma 6.2 on Arch Linux, the cursor is the dark Breeze cursor, however, in my system settings, I have explicitly set it to Breeze Light. Changing the cursor doesn't change the cursor in Amarok.

STEPS TO REPRODUCE
1. Change the cursor in KDE System Settings to any non default Cursor (such as Breeze Light)
2. Open the Amarok Flatpak.
3. The cursor is wrong when it is inside the Amarok application.

OBSERVED RESULT
The cursor is wrong when it is inside the Amarok application.

EXPECTED RESULT
The cursor should match the KDE system settings when it is inside the Amarok application.

SOFTWARE/OS VERSIONS (running kinfo)
Operating System: EndeavourOS (Arch Linux)
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 9 7940HS w/ Radeon 780M Graphics
Memory: 58.7 GiB of RAM
Graphics Processor: AMD Radeon 780M

ADDITIONAL INFORMATION
This obviously is a minor issue, but no other KDE or Qt application has had this issue to my knowledge, either as a system package, AppImage, or Flatpak.

Comment 1 Tuomas Nurmi 2024-11-16 09:25:04 UTC

Thank you for the report, interesting to hear. Didn't try reproducing myself yet, but sounds like something that well might be caused by it being a Qt5/KF5 app in Qt6/KF6 environment (and possibly getting fixed when changing to Qt6/KF6).

Comment 2 cameronbosch 2024-12-01 16:46:16 UTC

(In reply to Tuomas Nurmi from comment #1)
> Thank you for the report, interesting to hear. Didn't try reproducing myself
> yet, but sounds like something that well might be caused by it being a
> Qt5/KF5 app in Qt6/KF6 environment (and possibly getting fixed when changing
> to Qt6/KF6).

That sounds about right. I have the exact same problem with Proton Mail Bridge, which I'm 90% sure also uses Qt 5, although the one difference is that instead of using the Breeze cursor, it uses the default X cursor (or Adwaita, I'm not 100% sure), but it's definitely not the right cursor.

Both Proton Mail Bridge and Amarok on my system that produces the bug are in Flatpaks from Flathub. I can upload a short screen capture of the issue with both applications if you want.

Comment 3 cameronbosch 2024-12-01 16:50:38 UTC

Created attachment 176265 [details]
A short screen capture of this Qt bug.

Comment 4 Tuomas Nurmi 2025-07-12 09:58:25 UTC

Flatpak for Qt6/KF6-based 3.3.0 is now available, can you test if this one's fixed?

Comment 5 cameronbosch 2025-07-12 10:23:48 UTC

(In reply to Tuomas Nurmi from comment #4)
> Flatpak for Qt6/KF6-based 3.3.0 is now available, can you test if this one's fixed?

I can confirm that with Amarok 3.3 that the problem has been fixed. Thank you and everybody who worked on the Qt 6 port of Amarok!

Comment 6 Tuomas Nurmi 2025-07-13 15:33:07 UTC

Great to hear, thank you for verifying!