Univention Bugzilla – Bug 32669
Traceback in cups-printer.py if univentionPrinterUseClientDriver is missing at LDAP printer share object
Last modified: 2013-10-07 14:43:55 CEST
If an old printer object is changed with UCS 3.1-1 erratum165, a traceback in listener.log is shown: Traceback (most recent call last): File "/usr/lib/univention-directory-listener/system/cups-printers.py", line 364, in handler if new['univentionPrinterUseClientDriver'][0] == '1': KeyError: 'univentionPrinterUseClientDriver' The traceback results in a 0-byte-file in /etc/samba/printers.conf.d/ for the affected printer share object. Workaround: set the property useClientDriver via UDM to "0". This bug seems to be fixed together with bug 30432 in UCS 3.2 (has to be checked).
errata3.1-1: univention-printserver 6.0.21-4.626.201309241657 YAML 2013-09-24-univention-printserver.yaml ucs3.2: univention-printserver 7.0.7-4.627.201309241701 added changelog entry
Code review: OK Tests: Traceback happens before update: OK Installation: OK Traceback gone after update: OK Printer files generated correctly: OK Advisory: Missing
(In reply to Janek Walkenhorst from comment #2) > ... > > Advisory: Missing added
(In reply to Felix Botner from comment #3) > (In reply to Janek Walkenhorst from comment #2) > > Advisory: Missing > added OK
http://errata.univention.de/ucs/3.1/187.html