Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 784824 - x11-drivers/nvidia-drivers with <xorg-server-1.20.10-r2 prevent upgrade when switching to display-manager-init
Summary: x11-drivers/nvidia-drivers with <xorg-server-1.20.10-r2 prevent upgrade when ...
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Ionen Wolkens
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-21 15:15 UTC by Mike Limansky
Modified: 2021-04-22 19:35 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Limansky 2021-04-21 15:15:19 UTC
nvidia-drivers-390.x requires x11-base/xorg-server-1.20.10 which cannot be installed with display-manager-init.

emerge -1p nvidia-drivers xorg-server

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N     ] acct-user/nvpd-0 
[ebuild     U  ] x11-drivers/nvidia-drivers-390.141-r1 [390.138-r5] USE="(-dist-kernel)" 
[ebuild  N     ] gui-libs/display-manager-init-1.0-r3 
[ebuild  r  U  ] x11-base/xorg-server-1.20.11 [1.20.10] USE="-test%" 
[ebuild  rR    ] x11-drivers/xf86-input-libinput-0.30.0 
[blocks B      ] <=sys-apps/sysvinit-2.98 ("<=sys-apps/sysvinit-2.98" is blocking gui-libs/display-manager-init-1.0-r3)
[blocks B      ] <=x11-apps/xinit-1.4.1 ("<=x11-apps/xinit-1.4.1" is blocking gui-libs/display-manager-init-1.0-r3)
[blocks B      ] <=x11-base/xorg-server-1.20.10 ("<=x11-base/xorg-server-1.20.10" is blocking gui-libs/display-manager-init-1.0-r3)
[blocks B      ] x11-drivers/nvidia-drivers[-libglvnd(-)] ("x11-drivers/nvidia-drivers[-libglvnd(-)]" is hard blocking x11-base/xorg-server-1.20.10)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (sys-apps/sysvinit-2.97:0/0::gentoo, installed) pulled in by
    >=sys-apps/sysvinit-2.86-r6 required by (sys-apps/openrc-0.42.1:0/0::gentoo, installed) USE="ncurses netifrc pam (split-usr) unicode -audit -bash -debug -newnet (-prefix) (-selinux) -static-libs -sysv-utils" ABI_X86="(64)"

  (gui-libs/display-manager-init-1.0-r3:0/0::gentoo, ebuild scheduled for merge) pulled in by
    gui-libs/display-manager-init required by (x11-base/xorg-server-1.20.11:0/1.20.11::gentoo, ebuild scheduled for merge) USE="elogind udev xorg -debug -dmx -doc -ipv6 -kdrive (-libressl) -minimal (-selinux) -suid -systemd -test -unwind -wayland -xcsecurity -xephyr -xnest -xvfb" ABI_X86="(64)"

  (x11-apps/xinit-1.4.1:0/0::gentoo, installed) pulled in by
    >=x11-apps/xinit-1.3.3-r1 required by (x11-base/xorg-server-1.20.11:0/1.20.11::gentoo, ebuild scheduled for merge) USE="elogind udev xorg -debug -dmx -doc -ipv6 -kdrive (-libressl) -minimal (-selinux) -suid -systemd -test -unwind -wayland -xcsecurity -xephyr -xnest -xvfb" ABI_X86="(64)"

  (x11-drivers/nvidia-drivers-390.141-r1:0/390::gentoo, ebuild scheduled for merge) pulled in by
    nvidia-drivers
    x11-drivers/nvidia-drivers required by (x11-base/xorg-drivers-1.20-r2:0/0::gentoo, installed) USE="" ABI_X86="(64)" INPUT_DEVICES="libinput -elographics -evdev -joystick -synaptics -vmmouse -void -wacom" VIDEO_CARDS="i965 intel nvidia -amdgpu -ast -dummy -fbdev (-freedreno) (-geode) -glint -i915 -mga -nouveau -nv (-omap) -qxl -r128 -radeon -radeonsi -siliconmotion (-tegra) (-vc4) -vesa -via -virtualbox -vmware"
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-04-21 18:02:13 UTC
Please share the output of emerge -p -uvDU @world. Partial upgrades lead to conflicts like this which, even if are similar to that with a full world upgrade, aren’t expected to work anyway. So let’s debug the problem we are able to solve.
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-04-21 18:03:04 UTC
(I’ll assign anyway given there might be some oversight Ionen can spot immediately.)
Comment 3 Mike Limansky 2021-04-21 18:41:57 UTC
(In reply to Sam James from comment #1)
> Please share the output of emerge -p -uvDU @world. Partial upgrades lead to
> conflicts like this which, even if are similar to that with a full world
> upgrade, aren’t expected to work anyway. So let’s debug the problem we are
> able to solve.

I've left only the last lines:

[ebuild     U  ] x11-drivers/nvidia-drivers-390.141-r1:0/390::gentoo [390.138-r5:0/390::gentoo] USE="X driver tools (-dist-kernel) -static-libs (-compat%) (-gtk3%*) (-kms%*) (-libglvnd%*) (-multilib%*) (-uvm%) (-wayland%)" ABI_X86="32 (64) (-x32)" 85 030 KiB
[ebuild     U  ] x11-base/xorg-server-1.20.10-r3:0/1.20.10::gentoo [1.20.10:0/1.20.10::gentoo] USE="elogind udev xorg -debug -dmx -doc -ipv6 -kdrive (-libressl) -minimal (-selinux) -suid -systemd -test% -unwind -wayland -xcsecurity -xephyr -xnest -xvfb (-static-libs%)" 0 KiB
[ebuild     U  ] x11-base/xorg-server-1.20.11:0/1.20.11::gentoo [1.20.10:0/1.20.10::gentoo] USE="elogind udev xorg -debug -dmx -doc -ipv6 -kdrive (-libressl) -minimal (-selinux) -suid -systemd -test% -unwind -wayland -xcsecurity -xephyr -xnest -xvfb (-static-libs%)" 6 325 KiB
[blocks B      ] x11-drivers/nvidia-drivers[-libglvnd(-)] ("x11-drivers/nvidia-drivers[-libglvnd(-)]" is hard blocking x11-base/xorg-server-1.20.10)
[blocks B      ] <=x11-base/xorg-server-1.20.10 ("<=x11-base/xorg-server-1.20.10" is blocking gui-libs/display-manager-init-1.0-r3)

Total: 79 packages (68 upgrades, 3 new, 1 in new slot, 7 reinstalls), Size of downloads: 155 450 KiB
Conflict: 2 blocks (2 unsatisfied)

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

x11-base/xorg-server:0

  (x11-base/xorg-server-1.20.11:0/1.20.11::gentoo, ebuild scheduled for merge) USE="elogind udev xorg -debug -dmx -doc -ipv6 -kdrive (-libressl) -minimal (-selinux) -suid -systemd -test -unwind -wayland -xcsecurity -xephyr -xnest -xvfb" ABI_X86="(64)" pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (x11-base/xorg-server-1.20.10-r3:0/1.20.10::gentoo, ebuild scheduled for merge) USE="elogind udev xorg -debug -dmx -doc -ipv6 -kdrive (-libressl) -minimal (-selinux) -suid -systemd -test -unwind -wayland -xcsecurity -xephyr -xnest -xvfb" ABI_X86="(64)" pulled in by
    x11-base/xorg-server:0/1.20.10= required by (x11-drivers/xf86-input-libinput-0.30.0:0/0::gentoo, installed) USE="" ABI_X86="(64)"
                        ^^^^^^^^^^^                                                                                                                                                         


It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (x11-drivers/nvidia-drivers-390.141-r1:0/390::gentoo, ebuild scheduled for merge) pulled in by
    x11-drivers/nvidia-drivers required by (x11-base/xorg-drivers-1.20-r2:0/0::gentoo, installed) USE="" ABI_X86="(64)" INPUT_DEVICES="libinput -elographics -evdev -joystick -synaptics -vmmouse -void -wacom" VIDEO_CARDS="i965 intel nvidia -amdgpu -ast -dummy -fbdev (-freedreno) (-geode) -glint -i915 -mga -nouveau -nv (-omap) -qxl -r128 -radeon -radeonsi -siliconmotion (-tegra) (-vc4) -vesa -via -virtualbox -vmware"

  (gui-libs/display-manager-init-1.0-r3:0/0::gentoo, ebuild scheduled for merge) pulled in by
    gui-libs/display-manager-init required by (x11-base/xorg-server-1.20.11:0/1.20.11::gentoo, ebuild scheduled for merge) USE="elogind udev xorg -debug -dmx -doc -ipv6 -kdrive (-libressl) -minimal (-selinux) -suid -systemd -test -unwind -wayland -xcsecurity -xephyr -xnest -xvfb" ABI_X86="(64)"
    gui-libs/display-manager-init required by (x11-base/xorg-server-1.20.10-r3:0/1.20.10::gentoo, ebuild scheduled for merge) USE="elogind udev xorg -debug -dmx -doc -ipv6 -kdrive (-libressl) -minimal (-selinux) -suid -systemd -test -unwind -wayland -xcsecurity -xephyr -xnest -xvfb" ABI_X86="(64)"
Comment 4 Mike Limansky 2021-04-21 18:45:43 UTC
Same with --backtrack=30
Comment 5 Ionen Wolkens gentoo-dev 2021-04-22 08:23:05 UTC
Since xorg-server-1.20.10-r2 is still in the tree, try:

emerge -1 =xorg-server-1.20.10-r2 nvidia-drivers

This will update the xorg blocker and then "should" let you upgrade to display-manager-init without issues.

(In reply to Sam James from comment #2)
> (I’ll assign anyway given there might be some oversight Ionen can spot
> immediately.)
<xorg-server-1.2.10-r2 have an outdated !!hard blocker, libglvnd(-) should be libglvnd(+), in -r0 this was fixed through dynamic-deps (and revbumped later) but since it's gone from the tree this can't be picked up anymore.

And because of display-manager-init's 4 soft blockers, seems portage doesn't know how to handle the situation.

I don't think there's really anything I can do from this side except add a no-op libglvnd IUSE forced-on which would be wrong.
Comment 6 Ionen Wolkens gentoo-dev 2021-04-22 09:37:58 UTC
When xorg-server-1.20.10-r2 is gone, it may be necessary to temporarily remove nvidia-drivers, upgrade, then re-install drivers.

Fortunately, most people should've upgraded to >=xorg-server-1.20.10-r2 already given the time it took for d-m-i to be stable.
Comment 7 Mike Limansky 2021-04-22 19:29:45 UTC
Thanks, that's fixed the problem.
Comment 8 Ionen Wolkens gentoo-dev 2021-04-22 19:35:57 UTC
(In reply to Mike Limansky from comment #7)
> Thanks, that's fixed the problem.
Good to hear, hopefully the issue won't hit too many people (I changed the summary so it's easier to find).

Changing from FIXED given it's not really fixed and just worked around, lacking a sane way to fix this.