Re: KDM 4:4.6.3-1 upgrade fails
Am Friday, 27. May 2011, 12:47:16 schrieb firstname.lastname@example.org:
> 27/05/2011 10:45, Ferdinand Thommes wrote:
> > Hi,
> > I cannot confirm this, upgrading from 4.6.2 to 4.6.3 on a unstable
> > system. Everything went fine on 32 and 64-bit. No errors at all.
> Like I said it's an upgrade from Wheezy (kdm 4:4.4.5-9), not an
> experimental or Sid version.
> My questions are do you have a kdm group (/etc/group) or not ? If so
> with which GID, and what is kdm system user "standard" UID ?
"getent group | grep kdm" is empty for me, so no kdm group.
The kdm binary is owned by root:root and the kdm process runs as root too.
But "getent passwd | grep kdm" gives:
> > Great work, *many thanks* to debian-kde team.
> > 2011/5/27 email@example.com <mailto:firstname.lastname@example.org>
> > <email@example.com <mailto:firstname.lastname@example.org>>
> > Hi everyone, I was thrilled this morning to see KDE 4.6 landing in
> > Sid, great !
> > When upgrading from Wheezy to the current Sid version I got a
> > post-install error leaving kdm in a broken state. Looking into it I
> > found that the "adduser" command from /var/lib/dpkg/info/kdm.postinst
> > was the culprit, spitting errors about an non existing ID in the
> > 62455 range (decrementing -1 every new error).
> > So I created manually a kdm system user and group with:
> > adduser --system --group --no-create-home kdm
> > (original postinstall command is without --group)
> > and also took care of:
> > chown -R kdm /var/lib/kdm
> > Then kdm installed fine.
> > Now everything works, but did anyone else encounter this error
> > (didn't find it in the BTS) ? Is what I did a foolish move and KDE
> > will explode in my face at some point ?
> > --
> > To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
> > <mailto:debian-kde-REQUEST@lists.debian.org>
> > with a subject of "unsubscribe". Trouble? Contact
> > email@example.com <mailto:firstname.lastname@example.org>
> > Archive: 4DDF6270.email@example.com">http://lists.debian.org/4DDF6270.firstname.lastname@example.org