Bug 514495 - In Discover, the interface in the Flatpak (Flathub) settings section is incorrect. The text indicating the repository is visually merged with the Flatpak repository action buttons.
Summary: In Discover, the interface in the Flatpak (Flathub) settings section is incor...
Status: RESOLVED DUPLICATE of bug 513324
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 6.5.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-12 16:21 UTC by ignazweis
Modified: 2026-01-12 18:52 UTC (History)
2 users (show)

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

Attachments
Screenshot of the issue (69.73 KB, image/png)
2026-01-12 16:21 UTC, ignazweis 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description ignazweis 2026-01-12 16:21:48 UTC 
Created attachment 188442 [details]
Screenshot of the issue

SUMMARY
In Discover, the interface in the Flatpak (Flathub) settings section is incorrect. The text indicating the repository is visually merged with the Flatpak repository action buttons.

STEPS TO REPRODUCE
1. Open Discover
2. Go to the settings tab.
3. Observe the Flatpak section.

OBSERVED RESULT
The buttons "Increase priority," "Decrease priority," "Remove repository," and "Show contents" are merged with the text "Flathub - dl.flathub.org".

EXPECTED RESULT
The buttons "Increase priority," "Decrease priority," "Remove repository," and "Show contents" should be separated from the text to make them easier to read.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
The buttons work correctly, but the user interface layout is incorrect. There hasn't been a single time it hasn't happened since I installed openSUSE KDE yesterday.
Comment 1 Nate Graham 2026-01-12 18:52:08 UTC 

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