Bug 449574 - Printerlist is too narrow and not resizable
Summary: Printerlist is too narrow and not resizable
Status: RESOLVED DUPLICATE of bug 414908
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_printer_manager (show other bugs)
Version: 5.23.5
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-03 20:39 UTC by Geert Janssens
Modified: 2022-02-04 16:56 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of printerlist with truncated printer names (312.04 KB, image/png)
2022-02-03 20:39 UTC, Geert Janssens
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Geert Janssens 2022-02-03 20:39:04 UTC
Created attachment 146236 [details]
Screenshot of printerlist with truncated printer names

SUMMARY

I have several print queues with fairly long names that only differ in their suffix, like
Bureau_Lade2_Duplex_Plain
Bureau_Lade2_Duplex_Film

These names won't fully fit in the printer list in System Settings and hence it's hard to distinguish them. I also can't widen the list to see the full names. This makes is harder than necessary to select the proper printer. Particularly as there is plenty of space on my screen to widen the full System Settings window and/or the printer list widget.

STEPS TO REPRODUCE
1.  Create multiple printer queues with long names
2. Open System Settings->Printers
3. Widen the System Settings window

OBSERVED RESULT
After step 2. the list of printers is presented, but the printer names are truncated.
Attempting to widen the window as suggested in step 3. doesn't make a difference.

EXPECTED RESULT
When there's enough room, just display the printer names in full or allow the user to widen the list.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Fedora 35
(available in About System)
KDE Plasma Version:  5.23.5
KDE Frameworks Version:  5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-02-04 16:56:00 UTC

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