Bug 50537

Summary: print error priority (first letter of Class) not 'A' to 'Z'
Product: [Applications] kdeprint Reporter: D.L.C.Burggraaff <burdi>
Component: generalAssignee: Michael Goffioul <kdeprint_bugs>
Status: CLOSED DUPLICATE    
Severity: normal CC: jlayt
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: a screenshot to show the way the site is rendered

Description D.L.C.Burggraaff 2002-11-10 21:18:46 UTC 
Version:           4.1 (using KDE 3.0.9)
Compiler:          gcc version 2.95.3 20010315 (release)
OS:          Linux (i686) release 2.4.18

When printing from Kwrite (and the embedded text viewer) a "Catastrophy! - Knotify"
message pops up. It reads:

A print error occured. Error message received from system:
/usr/bin/lpr -P 'lp' -C 
'#000000:6:1:#d3d3d3:#000000:||%U:true:#d3d3d3:#000000:%y|%f|%p:true::false:false:false:false:false:true:true'
'/tmp/kde-root/kdeprint_vqxDjOY' : execution failed with message:
Fatal error - Priority (first letter of Class) not 'A' (lowest) to 'Z' (highest) 

No printout is produced.
I am running an LPR/LPRng Print System.
Kind regards, Dick
Comment 1 Christoph Cullmann 2002-11-11 22:49:43 UTC 
works here, never got that, perhaps kprint bug
Comment 2 D.L.C.Burggraaff 2003-01-09 22:30:23 UTC 
With 3.1 RC6 I still have the problem ...
Comment 3 D.L.C.Burggraaff 2003-01-09 22:35:39 UTC 
Did a search for "print priority", "print class" and got no relevant hits ...
Comment 4 Christoph Cullmann 2003-03-04 23:09:11 UTC 
seems to be no kate but, or ?
Comment 5 Matt Rogers 2003-03-04 23:48:56 UTC 
Created attachment 1104 [details]
a screenshot to show the way the site is rendered

screenshot showing behavior of konqueror when rendering this site.
Comment 6 Matt Rogers 2003-03-04 23:50:03 UTC 
ok, disregard that attachement and stuff, i should really pay more 
attention when updating bugs.
Comment 7 Michael Goffioul 2003-03-05 09:41:59 UTC 
Already solved (HEAD and 3.1 BRANCH).

*** This bug has been marked as a duplicate of 52605 ***
Comment 8 John Layt 2008-12-31 12:33:25 UTC 
Closing old Resolved status bug.