[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#254066: marked as done (kprinter "default printer" handling broken)

Your message dated Fri, 16 Feb 2007 23:15:00 +0100
with message-id <2007021623150016@ekaia.org>
and subject line Closing bug 254066
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: kdeprint
Version: 4:3.2.2-1

Hi all,

I'm experiencing major issues here with a
kdeprint/CUPS (1.1.20final+cvs20040330-1) combo (kprinter configured to
use CUPS print architecture).

I have two CUPS printers configured here, a hp4p and a hplj4000tn.

I did configure hplj4000tn to be the default destination
("Systemvoreingestelltes Druckziel") in CUPS.
However, upon invoking kprint it always selects the outdated hp4p
as currently active entry. This doesn't make any sense at all to me,
in fact it's very annoying to have to select the REAL default printer
every time one invokes kprinter to print a document.

Also, both printers are being listed as "Status: inactive" in kprinter,
even though on localhost:631 they're clearly NOT inactive, and lpstat
doesn't show anything to that extent either.

Any ideas? What should I try to debug that issue?


Andreas Mohr

--- End Message ---
--- Begin Message ---
Submitter was asked to provide more information about this bug
( http://bugs.debian.org/254066 ) four weeks ago.

Since more info was not provided, we are closing the bug.
Feel free to reopen this bug if you are still experiencing this issue
and you have extra information on how reproduce the issue.

Ana Guerrero,
  on behalf of the Debian Qt/KDE team

--- End Message ---

Reply to: