Bug 342254 - Smb-shared printer not used by Dosemu as the default printer
Summary: Smb-shared printer not used by Dosemu as the default printer
Status: RESOLVED INTENTIONAL
Alias: None
Product: print-manager
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.13.2
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-27 16:45 UTC by Dschoch
Modified: 2018-01-26 23:53 UTC (History)
0 users

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 Dschoch 2014-12-27 16:45:31 UTC
A shared printer (smb://server/hpdeskjet) which is connected via LPT at an old windows-pc within the network,  and then setup as the default printer in KDE system-setup at my Linux-Thinkpad, is still not be useable within DOSEMU. Using eg. 'copy autoexec.bat prn' will be routed still to my ethernet-attached Canon-printer, which is of course not able to understand the ASCSII-data. This is seen at the Printer-Applet, as the print-job will be seen with printer-type of 'Canon pixma....'
If using eg. Kate to open any document and selecting the shared printer (HPDeksjet) manually, the doc will be printed  at the remote printer. 
But as we can not select any printer within DOSEMU, we have first to setup the destination printer as the default-printer before starting DOSEMU.
So it looks as setting-up this printer as the default will not be presented to Dosemu as the current printer.
This was (and is still) working well with my old Ubuntu 10.04 Thinkpad.
I temporary deleted the Canon-Pixma, so that only this one and only shared printer is configured at the Thinkpad and of course setup as the default, the printjob will still not be routed to the remote printer.

Reproducible: Always

Steps to Reproduce:
1. select any remote smb-attached printer
2. open Dosemu
3. 'copy autoexec.bat prn'  (or LPT1)

Actual Results:  
still printing to the Canon-pixma Q, which will not manage the smb-printer

Expected Results:  
autoexec.bat should be printed at the remote smb-printer
Comment 1 Dschoch 2014-12-27 17:56:27 UTC
Found now the lpstat command-line command, which shows

schoch@LINUX-TP2:~$ lpstat -d -p
system default destination: Canon-IP5200R
printer Canon-IP5200R is idle.  enabled since Sa 27 Dez 2014 16:09:17 CET
printer HP-Deskjet-310 is idle.  enabled since Sa 27 Dez 2014 18:22:02 CET

indepentent of the setting with the printer-setup of the KDE.

Using lpoptions -d HP-Deskjet-310 will put this printer to the default and Dosemu will print as expected.
But this does show me, that the grafical printer-setup of KDE's 'Systemeinstellung' does NOT change anything in regard of the default printers.
It will always stay at 'his own' default-printer
Comment 2 Daniel Nicoletti 2014-12-27 18:06:15 UTC
We cannot give you any support for DOSEMU, and print-manager only talks to CUPS, if going to http://localhost:631 and seeing that the default printer there is not the same default printer in System Settings -> Printers then it's a bug, however it's working here so if that's the case please reopen and add more information.
Comment 3 Dschoch 2014-12-27 22:42:36 UTC
Find only with command lpstat the configured default-printer. In CUPS-webpage I could only find the printerlist, not any hint of the default printer.
But nevertheless, if I change the default printer within the KDE-settings graphical dialog, nothing will happen, the mark will move to the  selected printer as expected but using the lpstat command, the former default printer is still active, in my case the Canon IP5200 printer. Only using the lpoptions -d command will change the default printer.
So it looks as the KDE-settings are changing a different config-file, than CUPS (lpoptions) is actually using.
Comment 4 Daniel Nicoletti 2018-01-26 23:53:50 UTC
The printer settings panel changes the default server printer, not the user local one, that can be changed by changing some file and is not supported at the moment (maybe never will).