Bug 59649 - [Patch] lpdunix always shows printer as rejecting jobs
Summary: [Patch] lpdunix always shows printer as rejecting jobs
Status: CLOSED INTENTIONAL
Alias: None
Product: kdeprint
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Solaris
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-11 12:57 UTC by Jonathan Marten
Modified: 2008-12-31 13:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Marten 2003-06-11 12:57:24 UTC
Version:            (using KDE KDE 3.1.2)
Installed from:    Compiled From Sources
Compiler:          gcc 3.2.1 
OS:          Solaris

When using the "Generic Unix LPD Print System", the print dialogue always shows the printer state
as "Idle (rejecting jobs)", even when the printer is accepting.  This seems to be because the accepting/rejecting state is never initialised when the printer is created.

The state needs to be initialised with

	printer->setState(KMPrinter::Idle);
+	printer->setAcceptJobs(true);

in four places in kdelibs/kdeprint/lpdunix/kmlpdunixmanager.cpp

Thinks... the accept/reject state really has 3 possibilities (accepting, rejecting and unknown) to cover
those print systems that don't yet implement job management.  But making this change may have
compatibility implications.
Comment 1 Cristian Tibirna 2005-08-22 20:48:40 UTC
UNCONFIRMED (batch reassigning messed this)
Comment 2 Kurt Pfeifle 2007-01-09 01:36:08 UTC
Setting bug to "Confirmed"/NEW now.

However, I don't think the LPD print subsystem for KDE will ever get much more love. There is just no developer around any more who uses it.
Comment 3 groot 2008-08-01 14:03:47 UTC
Closed; KDE4 uses cups on the still supported Solaris versions (S10U5 and later) -- and ships cups packages if you need them.
Comment 4 John Layt 2008-12-31 13:11:18 UTC
Closing old Resolved status bug.