Hide Forgot
Description of problem: When I wish to install a network printer within the gnome setting tool "Printer" I can add a printer but printing with that printer fails. If I install a network printer as root with "system-config-printer" I can add a printer and I can print with that printer. So maybe when adding a printer with the gnome-tool it has a privileg problem or some name resolution to this network printer isn't correctly executed. I don't know. Maybe the problem is the following: I tried this with a printer which is not directly connected to the network. The printer is connected to a Server with "MS Windows 2003 Server" and it is a shared in a windows network. It is regardless which printertype I try. All printers on the servers fails to print. Version-Release number of selected component (if applicable): Fedora 20 Beta How reproducible: always Steps to Reproduce: 1. Connect a printer to a (Windows(?))-Server. 2. Connect the (Windows)-Server to the local network. 3. Connect another computer to the same local network. 4. Go in gnome settings and open the tool "Printer" 5. Add a new network printer and search this printer behind the (Windows)-Server (take your login/password to gain access to that server) Actual results: Printer adds correctly and a new entry appear in the printer list. Try to print with that printer (testpage or a document with another application) -> nothing happens, even no error message! Expected results: Printer adds correctly and a new entry appear in the printer list. Try to print with that printer (testpage or a document with another application) -> it should print flawlessly Additional info:
Hi Rolle, maybe this is a problem with authentication info. Could you have a look into /etc/cups/printers.conf and find line starting with "DeviceURI"? Does it contain your username and password for the samba server for the printer configured by system-config-printer ? Regards Marek
Ah, you're right. With system-config-printer the generated DeviceURI have the loginname and password included: smb://myname:mypassword@servercomputer/Samsung With the gnome control center the generated DeviceURI doesn't have the loginname nor the password included: smb://servercomputer/Samsung The rest of the files are nearly identically. It differs in the UUID, the StateTime and the control-center-version has an additionaly line "Option media iso-a4". I think this is ok. A security remark: The loginname and password are plain text. So the printers.conf is only readable for root but I think it's not so nice to store it as plain text.
That's why system-config-printer would default to omitting the credentials and instead watching for jobs requiring authentication (in system-config-printer-applet) and giving a notification for such jobs. Marek, it looks like GNOME doesn't do this, which is a pretty major regression. :-( Here's a link to the system-config-printer code for this. https://git.fedorahosted.org/cgit/system-config-printer.git/tree/jobviewer.py#n908
(In reply to Rolle from comment #2) > Ah, you're right. > > With system-config-printer the generated DeviceURI have the loginname and > password included: > smb://myname:mypassword@servercomputer/Samsung > > With the gnome control center the generated DeviceURI doesn't have the > loginname nor the password included: > smb://servercomputer/Samsung Yeah, we've decided to not store the password in the file so this is the cause of the problem. Does the print dialog ask you for password if you print from e.g. evince or gedit? (gtk+ should recognize jobs needing auth info) (In reply to Tim Waugh from comment #3) > Marek, it looks like GNOME doesn't do this, which is a pretty major > regression. :-( I'll look at how to solve this.
> Does the print dialog ask you for password if you print from e.g. evince > or gedit? (gtk+ should recognize jobs needing auth info) No. There is no dialog or something else. No information for the user, that there could be a problem.
Addition to comment 5: If I print a document I can see the failed status in the printer queue. But I must know this and open it manually. Gnome Control Center -> Select the printer -> show the print jobs: Status is "Zurückgehalten" (in english maybe "Stopped"?) system-config-printer -> Select the printer -> look at the printer status: "Untätig - Tree connect failed (NT_STATUS_ACCESS_DENIED)" I think this is very complicated to see. Are there no printer applet, like in Ubuntu 13.xx?
The problem still exist in Fedora 21 alpha LiveCD.
A duplicate(?) of this: bug 956216
The problem still exist in Fedora 21 Official Release.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.