Can't update lightdm

[systemdCottboy]

translation of output of

Code: Select all

yum update

:

Code: Select all

-> Launch of test transaction
---> The lightdm.x86_64 0: 1.10.6-4.el7 package will be updated
---> The lightdm.x86_64 0: 1.18.3-4.el7 package will be used
---> The lightdm-gobject.x86_64 0: 1.10.6-4.el7 package will be updated
---> The lightdm-gobject.x86_64 0: 1.18.3-4.el7 package will be used
-> Dependency processing: glib2 (x86-64)> = 2.50.3 for package: lightdm-gobject-1.18.3-4.el7.x86_64
-> Dependency resolution completed
Error: Package: lightdm-gobject-1.18.3-4.el7.x86_64 (epel)
             Requires: glib2 (x86-64)> = 2.50.3
             Installed: glib2-2.46.2-4.el7.x86_64 (@base)
                 glib2 (x86-64) = 2.46.2-4.el7
 You can try using --skip-broken to work around the problem
** 4 pre-existing RPMDB problems found, the output of "yum check" is as follows:
ipa-client-4.4.0-14.el7.centos.7.x86_64 conflicts are installed freeipa-client: ipa-client-4.4.0-14.el7.centos.7.x86_64
ipa-client-common-4.4.0-14.el7.centos.7.noarch conflicts are installed freeipa-client-common: ipa-client-common-4.4.0-14.el7.centos.7.noarch
ipa-common-4.4.0-14.el7.centos.7.noarch conflicts are installed freeipa-common: ipa-common-4.4.0-14.el7.centos.7.noarch
ipa-python-compat-4.4.0-14.el7.centos.7.noarch conflicts are installed freeipa-python-compat: ipa-python-compat-4.4.0-14.el7.centos.7.noarch

Does anyone know please how to fix it ?

[TrevorH]

That package comes from EPEL who track RHEL 7.4 not CentOS and as CentOS 7.4 is not yet GA, you cannot install it that way. You either need to enable the CR repo and update to what will be CentOS 7.4 when it goes GA or you need to track down and use the previous EPEL lightdm packages.

[jjblanch]

It seems that it is not possible even to install lightdm from epel repository in clean new installations, nor it is possible to obtain a previous version of the lightdm package

I have installed the epel repo version that comes inside the Centos Distro: yum --enablerepo=extras install epel-release

Does anyone know please how to obtain a previous version that works ?

[TrevorH]

"You either need to enable the CR repo and update to what will be CentOS 7.4 when it goes GA or you need to track down and use the previous EPEL lightdm packages."

If you can't find the older one then CR is the only route left.

[MartinR]

Are you actually using lightdm? I had this come up in a VM and simply using

Code: Select all

# yum remove lightdm-gobject

sorted things out. I've rebooted the VM and logged into the MATE desktop and nothing seems broken so far ...

[Max]

I am using lightdm, so I'm in trouble since I seem to have the same error?

And will adding the CR repo make my system unstable?

[Max]

What I have done is adding the CR repo and install those 2 glibc2 packages and all went fine.

[upnort]

Are you actually using lightdm?

Yes.

Looks like the new lightdm-gobject package was compiled against glib2 2.50, which is in the CR repo, rather than against the current glib2 2.46.2 package. Temporarily enabling the CR repo is a possible solution, but I would rather wait until the packages are pushed officially to 7.4. Would be nice if the package maintainer compiled against 2.46.2 or reverted the package.

[avij]

Would be nice if the package maintainer compiled against 2.46.2 or reverted the package.

Then it would not work for those EPEL users using RHEL 7.4 or other RHEL derivatives.

I'd suggest using the CR packages, because those are the exact same packages that will eventually end up to CentOS 7.4.

[upnort]

I'd suggest using the CR packages, because those are the exact same packages that will eventually end up to CentOS 7.4.

On production systems I prefer to wait rather than enable CR. I am testing CR in a VM . Yes, now that CR is populated an official ISO is around the corner.

A similar problem noted here. I realize RHEL EPEL users have priority, but seems there is a timing hurdle here. I'm not pointing fingers or screaming, but MATE/LightDM are not "officially" supported upstream. The maintainer could have waited until the CentOS 7.4 ISOs were released. That the packages are in CR is one thing, but pushing them to base is another.