[Pkg-cups-devel] Bug#680195: base: sudoer not added to lpadmin, cannot add printer

[R33D3M33R]

Hello Jonathan,

my cups version is 1.5.3-1

The first problem with this permissions problem is the lack of feedback.
IIRC the webinterface didn't give any feedback when the buttons were
pressed also system-config-printer-kde just hanged. As I was adding a
network printer, I assumed this could be a network problem at first and
wasted many time on researching this. Also the "cupsdAuthorize: Empty Basic
password!" isn't as descriptive as I would hope for. What I would expect is
something like: "cupsdAuthorize: Permission denied" and that would
immediately point me to the right direction.

The prompt idea is great. So if the root password is not set, the cups
should prompt via checkbox which sudo account should be added to the group
that can add printers. It can be similar to debian tasksel prompt All the
privileged users should be listed and the user installing can simply check
one or multiple values. But I'm not sure how this would work with GUI
frontends Apper, Synaptic, etc.

Best Regards,
Andrej

2012/7/7 Jonathan Nieder <jrnieder at gmail.com>

> retitle 680195 cups: please document need to add administrator to lpadmin
> group more clearly
> reassign 680195 cups
> # documentation
> severity 680195 minor
> tags 680195 + upstream moreinfo
> quit
>
> Hi Andrej,
>
> R33D3M33R wrote:
>
> > 1. Leave root password blank at install (first user is "ruser" and has
> administration privileges)
> > 2. Login as "ruser" and try to add printer through web interface or
> system-config-printer-kde (nothing works)
> > 3. In webinterface the buttons Find and Add don't work at all, the
> system-config-printer-kde hangs
> > 4. Error log entries appear in /var/log/cups/error_log: "cupsdAuthorize:
> Empty Basic password!"
> > 5. Add rootuser to lpadmin (I used KUser) and restart
> > 6. Adding printer works
> >
> > I'm not sure if this is intentional or it's a bug, but it could be a
> major showstopper for new users.
>
> Thanks for reporting.  It's intentional.
>
> What version of cups do you use?  What documentation do you think new
> users will first look at when they first run into this problem, and
> could it be improved?
>
> Is there some other way to avoid confusion here --- for example,
> should there be a debconf prompt that asks if a user should be added
> to the lpadmin group?
>
> Hope that helps,
> Jonathan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-cups-devel/attachments/20120708/fc2ced64/attachment-0001.html>