Bug 2761 - Support multiple local printers
Summary: Support multiple local printers
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Printing (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Pierre Ossman
URL:
Keywords:
: 467 (view as bug list)
Depends on: 4814
Blocks:
  Show dependency treegraph
 
Reported: 2008-04-11 12:04 CEST by Erik Forsberg
Modified: 2022-06-22 10:18 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:


Attachments

Comment 1 Erik Forsberg cendio 2008-04-11 14:06:17 CEST
I've checked if options added on the commandline of the ipp client are transferred over to the receiving side - they are _not_, which is a pity as it would have helped. 
Comment 3 Peter Åstrand cendio 2008-05-08 11:01:29 CEST
*** Bug 467 has been marked as a duplicate of this bug. ***
Comment 4 Peter Åstrand cendio 2008-05-08 11:02:26 CEST
The current idea is to implement a solution where, optionally, the printer selection dialog pops up at the client on every print. 
Comment 5 Peter Åstrand cendio 2008-05-19 14:16:50 CEST
The printer selection dialog popup has been moved to bug 2787 and bug 2789. Moving this to Future, for possible generalized solution. 
Comment 6 Peter Åstrand cendio 2013-09-25 10:46:49 CEST
Our current idea is to add options to the client, where the user can choose to export:

* No printer
* All printers
* A list of printers

The exported printers will be transferred in client_params to VSM, which will need to create the queues and make sure that it is only visible for users which actually have such a printer. Then, the backend needs to include the printer name when transferring the print job to the client. 

Getting a list of local printers should be fairly easy on Windows and OS X; might be more difficult to UNIX since the output format of "lpstat -a" and others are not standardized. However, we can likely create something that works in practice.

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