Bug 33000 – Printer drivers for multiple devices of the same model

Bug 33000 - Printer drivers for multiple devices of the same model


Summary:	Printer drivers for multiple devices of the same model

Status:	CLOSED FIXED

Product:	UCS manual
Classification:	Unclassified
Component:	Print services
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.0-2-errata
Assigned To:	Stefan Gohmann
QA Contact:	Arvid Requate

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-10-29 10:42 CET by Tim Petersen
Modified:	2015-08-06 18:05 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Clarify purpose of x64/x86 driver upload (2.18 KB, patch) 2014-06-05 12:54 CEST, Arvid Requate	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

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

Description Tim Petersen

2013-10-29 10:42:49 CET

It seems that you cannot allocate an uploaded driver twice.
At least a customer said that every time he successfully allocates an uploaded driver to a printer, the second time he tries to do this with a second printer of the same model, he gets "Es wurde kein Treiber gefunden".

He found http://www.linuxtopia.org/online_books/network_administration_guides/samba_reference_guide/28_classicalprinting_37.html and uses rpcclient setdriver now.

Please see 2013042221002743 for further reference.

Comment 1 Arvid Requate

2014-06-05 12:54:55 CEST

Created attachment 5938 [details]
Clarify purpose of x64/x86 driver upload

The customer did not exactly follow the UCS documentation. The documentation should be improved:

He stumbled upon a strange Windows Client behavior: Experiments with Windows 7 clients (and Samba logs) show that a Windows 7 client only looks for x86 driver names to fill the printer specific driver assignment dropdown.

One of the screenshots provided by the customer shows that only x64 drivers had been uploaded in this case.

Comment 2 Stefan Gohmann

2015-06-27 22:47:20 CEST

Please have a look at the changes for Bug #38136. Do you want to see more changes?

Comment 3 Arvid Requate

2015-07-16 17:47:44 CEST

Ok, I did some adjustments in svn r62168, mostly for Bug 33000, Bug 35846,
Bug 34903 and Bug 37148.