Bug 52605 - kdeprint not working on 3.1.x but works with 3.0.x (lprng)
Summary: kdeprint not working on 3.1.x but works with 3.0.x (lprng)
Status: CLOSED WORKSFORME
Alias: None
Product: kdeprint
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Goffioul
URL:
Keywords:
: 50537 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-01-04 22:01 UTC by Damian Kolkowski
Modified: 2008-12-31 12:38 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Patch (2.16 KB, patch)
2003-01-06 10:23 UTC, Michael Goffioul 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Damian Kolkowski 2003-01-04 22:01:26 UTC 
Version:           unknown (using KDE 3.1.0 (RC6))
Installed from:    compiled sources
Compiler:          gcc version 3.2.1
OS:          Linux (i686) release 2.4.20-ac2

After I upgrade KDE to version 3.1-rc6 the lprng spooling deamon is not workin correctly (not working).

There is a window box with:

A print error occured. Error message received from system:

/usr/bin/lpr -P 'aps1' -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_VdBj4hV' : execution failed with message:
Fatal error - Priority (first letter of Class) not 'A' (lowest) to 'Z'
(highest)

Thats KDE bug! Becouse when I hint:

lpr som_text_document

It's works. And also kdeprint works correctly with 3.0.x
Comment 1 Damian Kolkowski 2003-01-04 22:40:56 UTC 
Bugs is only in kate, kwrite (konqueror is printing correctly).
Comment 2 Michael Goffioul 2003-01-06 10:23:23 UTC 
Created attachment 703 [details]
Patch

Does this patch solve the problem? (to be applied in kdelibs/kdeprint/lpr/)

Michael.
Comment 3 Damian Kolkowski 2003-01-06 11:01:01 UTC 
Yes it's works again THX Michael :-)
Comment 4 Michael Goffioul 2003-03-05 09:42:02 UTC 
*** Bug 50537 has been marked as a duplicate of this bug. ***
Comment 5 John Layt 2008-12-31 12:38:55 UTC 
Closing old Resolved status bug.