Bug 498149 - Lack of automatic encoding of printer SMB URI causes failure of adding a new printer
Summary: Lack of automatic encoding of printer SMB URI causes failure of adding a new ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_printer_manager (show other bugs)
Version: 5.27.5
Platform: Debian stable Linux
: NOR major
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-02 11:11 UTC by Patrik Grgurić
Modified: 2025-01-10 07:27 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrik Grgurić 2025-01-02 11:11:24 UTC
SUMMARY

I'm trying to add my company's printer, which is available through SMB at this URI:

smb://name.surname@firm.com@share/Xerox VersaLink B7030 ITIS

Which gets encoded to:

smb://name.surname%40firm.com@share/Xerox VersaLink B7030 ITIS

This causes an error when adding the printer:

1028 "Bad device-uri \"smb://name.surname%40firm.com@share/Xerox VersaLink B7030 ITIS\"."

Troubleshooting with ChatGPT, I got to this URI:

smb://name.surname%2540firm.com@share/Xerox%20VersaLink%20B7030%20ITIS

It works, so I'm guessing the encoding done by this utility/CUPS is insufficient?

STEPS TO REPRODUCE
1. Try to add a new printer that has spaces in its name with SMB

OBSERVED RESULT

The process silently fails at the "Finish" step with the aforementioned log line seen in the journal.

EXPECTED RESULT

The printer is successfully added.

SOFTWARE/OS VERSIONS

Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.11.10+bpo-amd64 (64-bit)
Graphics Platform: offscreen
Processors: 16 × AMD Ryzen 7 7735HS with Radeon Graphics
Memory: 13.3 GiB of RAM
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION

CUPS version: 2.4.2-3+deb12u8
Comment 1 John Kizer 2025-01-10 07:27:48 UTC
Thank you for your bug report!

Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), as this version of the KDE software is out of support from KDE, and so it's possible that the bug exists only in Debian at this point. Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream.

Thanks for understanding!