/etc/cups/cupsd.conf cannot be read by lpadmin

[Paul M Edwards]

Executing the "System \ Admin \ Printing" application does not evoke priveledge
escalation to access /usr/share/cups/ for proper configuration.

<[Chameleon]> Should the change made by the script in this bug be instant or
require a restart of X or a reboot or something?
<[Chameleon]> https://bugzilla.ubuntu.com/show_bug.cgi?id=2251
<[Chameleon]> basically this:
<[Chameleon]> $ sudo /usr/share/cups/enable_browsing 1
<sivang> [Chameleon]: it doesn't require restart.
<sivang> [Chameleon]: actually, it does :) but the cups-manager now handles it.
The bug we have with it is that it doesn't ask to be sudo'd when executed, which
it needs to be able to executed that script
<[Chameleon]> because, it's not enabling the "Global Settings \ Detect LAN
Printers" menu in gnome-cups-manager
<[Chameleon]> sivang: oh, so the menu not being enabled is because the script
doesn't ask to be sudo'd?
<[Chameleon]> I ran it manually with sudo and restarted gnome-cups-manager, but
I still don't get the menu.
<sivang> [Chameleon]: well, the cups-manager has be executed sudo'd in order to
be able to access /usr/share/cups/..
<[Chameleon]> OIC
<sivang> [Chameleon]: sudo gnome-cups-manager
<[Chameleon]> $ sudo gnome-cups-manager
<[Chameleon]> Password:
<[Chameleon]> ** (gnome-cups-manager:5562): WARNING **: IPP request failed with
status 1030
<[Chameleon]> it's repeating the error message
<[Chameleon]> every 5 seconds
<sivang> [Chameleon]: you're cups server is un accessible
<sivang> [Chameleon]: so it seems, but am not sure. anyways it works great for
me with sudo g-c-m
<[Chameleon]> yeah, it was the server
<[Chameleon]> my server seems to be flaky lately
<[Chameleon]> the cups service needs to be restarted frequently
<[Chameleon]> I should probably remove the FC3 on it and put Ubuntu there, too.
<[Chameleon]> :)
<sivang> [Chameleon]: hehe, sure :)
<[Chameleon]> sivang: thank you for your help.
<[Chameleon]> I was going to write this up since it seemed to be a bug, but
apparently it's already a known issue.
<sivang> [Chameleon]: I'd appriciate if you opene a bug about the fact it must
be executed sudo manually
<sivang> [Chameleon]: this does seems a bug to me :)
<[Chameleon]> sivang: you got it. :)
<sivang> [Chameleon]: if you can , assign it to me
<[Chameleon]> k

[Martin Pitt (pitti)]

There is no reason to have so little permissions on cupsd.conf. cupsys should
just stop to fiddle with conffile permissions in the first place.

[Sivan Greenberg (sivan)]

(In reply to comment #1)
> There is no reason to have so little permissions on cupsd.conf. cupsys should
> just stop to fiddle with conffile permissions in the first place.

Martin, do you know if cupsys is messing around with the conffile permissions,
or maybe this has something to do with the packaging itself?

[Martin Pitt (pitti)]

(In reply to comment #2)

> Martin, do you know if cupsys is messing around with the conffile permissions,

Yes, that's upstream code.

[Martin Pitt (pitti)]

 cupsys (1.1.23-10ubuntu4) breezy; urgency=low
 .
   * Add debian/patches/ubuntu-disable-conffile-chmod.dpatch:
     - Stop fiddling with the /etc/cups/cupsd.conf permissions at server
       startup. The default permissions as shipped (root:root 0644) are just
       fine for that file, and cupsys modifies it in a way that normal users
       cannot read them any more, which breaks gnome-cups-manager.
     - Ubuntu #15165
   * debian/cupsys.postinst:
     - If the package is upgraded from a version earlier than this one, correct
       permissions of cupsd.conf.

[Martin Pitt (pitti)]

*** Bug 21795 has been marked as a duplicate of this bug. ***