Upgrade Feisty -> Gutsy: Privileged user not in "lpadmin" group any more

I've solved the issue. After upgrading to Gutsy, my user isn't in the lpadmin group, then I added my user to this group and all is OK now.

Best regards,
neuromancer

I grepped the entire cupsys source for userdel and deluser, and cupsys never removes any group from any user. So I doubt that the cupsys upgrade itself is responsible for this.

  * Did the user lose any other groups? What does "id" say?
  * Do you use a nondefault authentication schema like LDAP or NIS?
  * Did you use the Gnome user&groups admin tool in between? (bug 26338)
  * What does "getent group lpadmin" say?

O Ven, 24-08-2007 ás 14:18 +0000, Martin Pitt escribiu:

> I grepped the entire cupsys source for userdel and deluser, and cupsys
> never removes any group from any user. So I doubt that the cupsys
> upgrade itself is responsible for this.
>
> * Did the user lose any other groups? What does "id" say?

I don't know if my user belong to this group before the upgrade to Gutsy
(in Feisty, is necessary belongs to lpadmin to admin printers?, this is
could be the problem.)

> * Do you use a nondefault authentication schema like LDAP or NIS?

No, I use PAM auth.

> * Did you use the Gnome user&groups admin tool in between? (bug 26338)

Before the upgrade do Gutsy I used gnome-cups-manager

> * What does "getent group lpadmin" say?

Now, when all ok, this is the output: "lpadmin:x:113:neuromancer"
I added this manually in users-admin

>
> ** Changed in: cupsys (Ubuntu)
> Status: New => Incomplete
> Target: ubuntu-7.10-beta => None
>

 If you have any questions, I´ll try to answer them.

Best regards,
neuromancer

Thanks for your answers.

Yes, in Feisty users must be in the lpadmin group to be able to admin printers.

We do not nned to know which printer setup tool you have used before the upgrade. Instead we need to know whether you have changed something in the configuration of the users and groups (add/remove users or groups, put users into certain groups, ...) and if you have used the user/group admin tool of GNOME, as this tool suffers a long-standing bug (bug 26338).

O Ven, 24-08-2007 ás 15:07 +0000, Till Kamppeter escribiu:

> Thanks for your answers.
>
> Yes, in Feisty users must be in the lpadmin group to be able to admin
> printers.
>
> We do not nned to know which printer setup tool you have used before the
> upgrade. Instead we need to know whether you have changed something in
> the configuration of the users and groups (add/remove users or groups,
> put users into certain groups, ...) and if you have used the user/group
> admin tool of GNOME, as this tool suffers a long-standing bug (bug
> 26338).
>

In Feisty (gnome-cups-manager) works ok, I were able to manage/add
printers... Only upgrade to Gutsy (no user/group management) and
system-config-printer don't work, I manually added (before upgrade and
failed to admin printers) my user to the lpadmin group (with
users-admin) and now all works ok.

Best regards
neuromancer

So this means that simply the upgrade triggered your removal from the lpadmin group. On such an upgrade hundreds of packages are updated. So it is not necessarily cupsys which did this change.

I had same problem, I wasn't in the lpadmin group. Before gutsy update I was there. I have two sudo users in my machine, "admin" group was ok after update. But "lpadmin" not, only the other user was there, not me.

I can also confirm this issue on Gutsy. All options in the printer dialog were disabled. I was able to fix things by doing the following:

  # adduser cupsys shadow

  # adduser gporcel lpadmin

  # /etc/init.d/cups restart

I am wondering if this issue could be due to the fact that I use "non-standard" user ids, in other words, not those supplied by Ubuntu. For instance, my user and group ids begin at 6000.

I forgot to mention that I also performed an upgrade from Feisty to Gutsy, just to be clear on that issue.

Thanks,

Gonzalo

I can also confirm this problem. I upgraded from Feisty to gutsy beta, and wasn't able anymore to change anything in the print settings. It always asked me for a password, and supplying the correct password for the user didn't work. After adding myself to the lpadmin group, I could change the settings again.

This needs really to get fixed in Gutsy

I cannot reproduce this by installing a clean feisty and upgrading to Gutsy.

I uploaded a new cupsys which *might* be the cause of this. If it was, it would be very dubious how it happens, but it is a safe change anyway.

cupsys (1.3.2-1ubuntu7) gutsy; urgency=low

  * debian/cupsys.postinst: Drop ancient transitional code to remove root from
    group lpadmin. Under very odd circumstances ("root" has the same UID than
    the user) this could cause the user to be removed from group 'lpadmin'.
    Quite unlikely that this is the prime reason for LP #134503, but it's much
    cleaner in any case.

 -- Martin Pitt <email address hidden> Mon, 15 Oct 2007 12:32:16 +0200

Can you reproduce this from a clean Feisty installation?

In a clean gutsy install, my normal user is not able to add a printer. I resorted to
% sudo /usr/share/system-config-printer/system-config-printer.py
in order to do it. It sure seems a problem to me in gutsy. BTW, this was adding a network (JetDirect) printer for what its worth.

I inspected the update-manager code and I'm certain that this is not a something that u-m is causing. Has anyone experienced the problem after Martins upload of cupsys 1.3.2-1ubuntu7 ?

Does anyone still experience this?

Is this the same problem as described in https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/152504 ?

No feedback for more than a month, so I close this. Thank you for your report, and please cry out if you still have problems, then I'll reopen this.