Bug 511723 - Rendering of list of ppd files broken - exceeds screen limit
Summary: Rendering of list of ppd files broken - exceeds screen limit
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_printer_manager (other bugs)
Version First Reported In: 6.3.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-06 17:00 UTC by Lukas Sommer
Modified: 2025-11-06 19:59 UTC (History)
2 users (show)

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


Attachments
screenshot.png (297.86 KB, image/png)
2025-11-06 17:00 UTC, Lukas Sommer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Sommer 2025-11-06 17:00:02 UTC
Created attachment 186550 [details]
screenshot.png

SUMMARY
Rendering of list of ppd files broken - exceeds screen limit. See screenshot.

STEPS TO REPRODUCE
1.  Open systemsettings
2.  Go to printer module
3.  Add a new printer connection

OBSERVED RESULT
There is a list of ppd files that exceeds the window that is shown. The entries on the lower side cannot be chosen. The blue help text (left botton) is rendered on top of the PPD list.

EXPECTED RESULT
The rendering is visually pleasant. If there are more list entries than the window has space, on the right side a scrollbar is shown. All enries can be chosen.

ADDITIONAL INFORMATION
Also, it seems to me that less PPD entries would be better. Why are there so many duplicates?

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 25.04
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.3
Kernel Version: 6.14.0-35-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.5 Gio of RAM
Graphics Processor 1: Intel® HD Graphics 630
Graphics Processor 2: llvmpipe
Manufacturer: LENOVO
Product Name: 80WK
System Version: Lenovo Y520-15IKBN
Comment 1 Mike 2025-11-06 17:30:47 UTC
This is fixed in 6.4+
Comment 2 Mike 2025-11-06 17:59:31 UTC
(In reply to Mike from comment #1)
> This is fixed in 6.4+

Ooops, sorry, fixed in 6.5
Comment 3 Lukas Sommer 2025-11-06 19:59:41 UTC
Thanks a lot!