Bug 494086

Summary:	GTK3 spinbox negative button is an X, instead of a -
Product:	[Plasma] Breeze	Reporter:	Mors Mortium <morsmortium>
Component:	Icons	Assignee:	visual-design
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	kainz.a, kbtr.buffer098, m, nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Mors Mortium 2024-10-04 04:22:09 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
As title says.

STEPS TO REPRODUCE
1. Have Breeze (or Breeze Dark) as your icon theme
2. Open a GTK3 application, that has a spinbutton widget (number input with -+ buttons)
3. Look at the widget

OBSERVED RESULT
The widget has an X instead of a - for the icon

EXPECTED RESULT
The decrease value icon is still a -, as it was previously

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3

ADDITIONAL INFORMATION
 I use Artix (based on Arch), fully upgraded. With downgrade I see that version 6.6.0-1 shows the bug, but 6.5.0-1 does not. It happens with new users and switching to another icon theme also fixes it (papirus was tested). GTK4 is not affected.

Comment 1 Nate Graham 2024-10-11 19:40:25 UTC

This is a bug in GTK, which uses that icon inappropriately. So when we changed it in the Breeze theme, it made spinboxes look wrong. In GTK4 they fixed this and made their spinboxes use a different icon that isn't also used for removing list items.

Can you report this to GTK and ask them to backport that change to GTK 3 as well? Thanks!

Comment 2 Nate Graham 2024-11-01 14:24:32 UTC

*** Bug 495663 has been marked as a duplicate of this bug. ***