Bug 509600 - Menu of Kolour paint is disconfigured
Summary: Menu of Kolour paint is disconfigured
Status: RESOLVED DUPLICATE of bug 448133
Alias: None
Product: kolourpaint
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.04.0
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: kolourpaint-support
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-17 14:42 UTC by Eduardo Dantas
Modified: 2025-09-17 16:21 UTC (History)
1 user (show)

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

Attachments
Screenshot of kolourpaint after removing qt5ct and qt6ct (319.73 KB, image/jpeg)
2025-09-17 15:58 UTC, Eduardo Dantas 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Eduardo Dantas 2025-09-17 14:42:13 UTC 
Hello there,

I am using kolourpaint 25.04.0 in Debian 13, in gnome environment, and in menu is appearing disconfigured.
I tried to install breeze font and install qt5ct and qt6ct. Nevertheless, anything worked.
Is there some way to solve this configuration problem?

***

SUMMARY

Menu of Kolour paint is  disconfigured

STEPS TO REPRODUCE
1. Open Kolourpaint in gnome 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Debian with gnome
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 5 and 6

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-09-17 14:51:54 UTC 
Can you attach a screenshot showing the problem *without* qt5ct and qt6ct installed?
Comment 2 Eduardo Dantas 2025-09-17 15:58:16 UTC 
Created attachment 185012 [details]
Screenshot of kolourpaint after removing qt5ct and qt6ct
Comment 3 Eduardo Dantas 2025-09-17 16:07:15 UTC 
Of course. The attached screenshot was taken after removing qt5ct and qt6ct. I have restarted Kolourpaint, but the problem persists.
Comment 4 Antonio Rojas 2025-09-17 16:21:11 UTC 

*** This bug has been marked as a duplicate of bug 448133 ***