Bug 3181 – Cups Listener Modul

Bug 3181 - Cups Listener Modul


Summary:	Cups Listener Modul

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	Printserver
Version:	UCS 1.2
Hardware:	Other Linux

Importance:	P3 normal (vote)
Target Milestone:	UCS 2.3
Assigned To:	Felix Botner
QA Contact:	Janek Walkenhorst

URL:
Keywords:

Duplicates:	14858 (view as bug list)
Depends on:
Blocks:	14432
	Show dependency tree / graph

Reported:	2005-05-23 17:14 CEST by Stefan Gohmann
Modified:	2009-12-21 08:47 CET (History)
CC List:	2 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
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 Stefan Gohmann

2005-05-23 17:14:17 CEST

In der listener.log tauchen immer wieder Fehlermeldungen auf: 
15.05.05 06:25:19  DEBUG_INIT 
15.05.05 06:25:19  USERS       ( WARN    ) : Did not found "notifier/server" 
 
15.05.05 06:25:19  LISTENER    ( ERROR   ) : connection okay to host 
rhea.pgvsalzburg.com 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
testing group 
Traceback (most recent call last): 
  File "/usr/lib/univention-ldap-listener/system/cups-printers.py", line 93, in 
handler 
    if old['univentionPrinterQuotaSupport'][0] == "1": 
KeyError: univentionPrinterQuotaSupport 
20.05.05 10:27:21  LISTENER    ( WARN    ) : at least one delete handler failed 
 
 
 
Reloading /etc/samba/smb.conf (smbd only). 
Reloading /etc/samba/smb.conf (smbd only). 
ERROR: PyKota v1.21alpha17_unofficial 
ERROR: pkprinters failed 
ERROR: Traceback (most recent call last): 
ERROR:   File "/usr/bin/pkprinters", line 300, in ? 
ERROR:     retcode = manager.main(args, options) 
ERROR:   File "/usr/bin/pkprinters", line 239, in main 
ERROR:     raise PyKotaToolError, _("There's no printer matching %s") % " 
".join 
(names) 
ERROR: PyKotaToolError: There's no printer matching testdrucker3 
testing group

Comment 1 Andreas Büsching

2007-11-27 09:59:01 CET

(In reply to comment #0)
> Traceback (most recent call last): 
>   File "/usr/lib/univention-ldap-listener/system/cups-printers.py", line 93, in 
> handler 
>     if old['univentionPrinterQuotaSupport'][0] == "1": 
> KeyError: univentionPrinterQuotaSupport 
> 20.05.05 10:27:21  LISTENER    ( WARN    ) : at least one delete handler failed 

Dieser Traceback tritt weiterhin auf. Die Drucker werden aber trotzdem aus CUPS entfernt

Comment 2 Stefan Gohmann

2009-06-24 13:29:55 CEST

*** Bug 14858 has been marked as a duplicate of this bug. ***

Comment 3 Felix Botner

2009-09-28 15:26:33 CEST

Die entsprechenden Stellen wurden mit einem xyz.has_key("univentionPrinterQuotaSupport") versehen.

Comment 4 Janek Walkenhorst

2009-11-03 14:54:51 CET

Fehler tritt nicht mehr auf, sowohl wenn das Attribut "univentionPrinterQuotaSupport" nicht gesetzt ist, als auch, wenn es auf 1 oder 0 gesetzt ist.

Changelog fehlt noch

Comment 5 Janis Meybohm

2009-11-03 15:03:27 CET

test

Comment 6 Janek Walkenhorst

2009-11-03 15:11:00 CET

(In reply to comment #5)
> test
Test

Comment 7 Felix Botner

2009-11-03 15:17:31 CET

Changelog angepasst.

Comment 8 Janek Walkenhorst

2009-11-03 15:21:50 CET

(In reply to comment #7)
> Changelog angepasst.
Verified

Comment 9 Stefan Gohmann

2009-12-21 08:47:12 CET

UCS 2.3 wurde veröffentlicht. Sollte der hier beschriebene Bug mit einer neueren Version von UCS erneut auftreten, so sollte der Bug dupliziert werden: "Clone This Bug".