Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1694996 - Change in printer name not persisted when it contains spaces
Summary: Change in printer name not persisted when it contains spaces
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-control-center
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pete Walter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-02 08:59 UTC by Jan Vlug
Modified: 2019-04-03 15:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Jan Vlug 2019-04-02 08:59:51 UTC
Description of problem:
I tried to change the name of a printer in
GNOME Settings | Printers | Printer Details | Name
The new name contained spaces. This name was not persisted. I got no feedback that this was because of the spaces in the name, which lead to the assumption that I could not change the name. Please provide clear feedback when using spaces in the printer name.


Version-Release number of selected component (if applicable):
gnome-control-center.x86_64                        3.30.3-1.fc29

Comment 1 Jan Vlug 2019-04-03 15:51:58 UTC
I also noticed that you cannot change the names of the printers that are discovered by DNS-SD.
This is annoying, because you cannot remove them, and they are not working either, so I would like to indicate in the name that users should not use them.
See also:
* https://gitlab.gnome.org/GNOME/gnome-control-center/issues/63
* https://gitlab.gnome.org/GNOME/gnome-control-center/issues/404
* https://gitlab.gnome.org/GNOME/gnome-control-center/issues/187


Note You need to log in before you can comment on or make changes to this bug.