Bug#257917: About your bug: "kdeprint: "stopped" printers (after print error) cannot be restarted" on the Debian BTS
ok, since then, i've discovered that you have to put users into lpadmin.
of course, that then allows them to do a lot more damage - such as
removing the printer entirely, and totally screwing up a configuration
that they don't understand.
if you don't _want_ them to be in the lpadmin group, you're stuffed.
there really _does_ have to be a way for the printer queue to recover,
automatically, from failures.
whilst this should probably be a cupsys 'wishlist' item, it could also
just as easily be handled kde-side.
l.
On Fri, Jan 12, 2007 at 11:40:59AM +0100, Ana Guerrero wrote:
> Hi,
>
> We (the Debian Qt/KDE team) are trying to update the bug status of some
> old bugs in the BTS.
>
> You filed the bug
> #257917 "kdeprint: "stopped" printers (after print error) cannot be restarted"
> some time ago, you can read the bug report at:
> http://bugs.debian.org/257917
>
> We are sorry if nobody responded when you filed the bug, KDE has gotten more bugs
> in the past years than the maintainers could handle. We are trying to fix this now,
> but we need your help. So please respond to this mail and tell us if:
>
> - you are still experiencing this bug (adding in what version)
> - the bug was already fixed,
> - or if you have extra information on how reproduce this bug.
>
> ---
> Thanks in advance,
> Ana Guerrero,
> on behalf of the Debian Qt/KDE team
>
--
--
lkcl.net - mad free software computer person, visionary and poet.
--
Reply to: