1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • [gentoo-user] chrome vs. wayland wierdness

    From Grant Edwards@21:1/5 to All on Fri Aug 5 00:00:01 2022
    I just did my usual

    emerge --sync
    emerge -auvND world

    Everything seemed to be fine (IIRC, it upgraded chrome).

    emerge --depeclean --ask

    That removed a couple wayland packages (yay! I didn't really want
    wayland). Then it warned me

    !!! existing preserved libs:
    >>> package: dev-libs/wayland-1.21.0
    * - /usr/lib64/libwayland-client.so.0
    * - /usr/lib64/libwayland-client.so.0.21.0
    * used by /opt/google/chrome/libGLESv2.so (www-client/google-chrome-104.0.5112.79)
    Use emerge @preserved-rebuild to rebuild packages using these libraries

    I do as instructed and run 'emerge @preserved-rebuild' and it reinstalls chrome.

    But a subsequent emerge --depeclean --ask again produces the same
    warnings about wayland libraries that have been preserved.

    Are the dependencies for chrome broken?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Neil Bothwick@21:1/5 to Grant Edwards on Fri Aug 5 01:20:01 2022
    On Thu, 4 Aug 2022 21:49:59 -0000 (UTC), Grant Edwards wrote:

    verything seemed to be fine (IIRC, it upgraded chrome).

    emerge --depeclean --ask

    That removed a couple wayland packages (yay! I didn't really want
    wayland). Then it warned me

    !!! existing preserved libs:
    >>> package: dev-libs/wayland-1.21.0
    * - /usr/lib64/libwayland-client.so.0
    * - /usr/lib64/libwayland-client.so.0.21.0
    * used by /opt/google/chrome/libGLESv2.so (www-client/google-chrome-104.0.5112.79) Use emerge @preserved-rebuild
    to rebuild packages using these libraries

    I do as instructed and run 'emerge @preserved-rebuild' and it
    reinstalls chrome.

    But a subsequent emerge --depeclean --ask again produces the same
    warnings about wayland libraries that have been preserved.

    Are the dependencies for chrome broken?

    chrome is a binary package, unlike chromium, so rebuilding will not change
    the libraries it depends on. It sounds like those wayland packages should
    not have been depcleaned and are a requirement for chrome.


    --
    Neil Bothwick

    Zmodem has bigger bits, softer blocks, and tighter ASCII

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmLsUkIACgkQ92eFu0QS MJhRQQ//Vh38FSHIhXp6sz9YjoGXfFtYv07vVoNWrOy2ESK2TV2/kSKiufKUIBlW Zo7VBL6BH8rxN+ceZF7Omg5LdHRbtH2tcLGFdB+64TOqxcNuZbhicHbhqNnZzNvE InE2NS9osegaryyqSoqP280UbnpISM5hxMjIDDCyzn25NebUcD0kY4b866A5iPvL HyUloio4v1s5smu3QJ2uhEFoEQ4nFA8ZsXHfhtDJ5J/pl618WH2lP9OCn901kdNg 9KGGgfxy+q00WkSqYdwXLIHG2srTNIuWU+p2xQhHUOLUlqD2oOR+0XB1iBrjxj+Y ijXqvMKdxfGMWZ1sdwIwVskKCEbK8vkvyPlTMZs9Z1LWW/bZOU+2dFXDFV6f4ddd iRnK+IAm47w2kYSFDy+e+VJIehK2PIM6k7DmnNKjQg0GjmUAGEOn1mC5f0+hHjHW XFDctOL+/AHJ7G2e6NZTgsc90lvR3WY/ELUGwweVFLOFuRqffcBtcce30q7ffv2y WoQCVE1SazXqK8z74yyWd8hgoDMhudaiOiCRCVOeMS3Sgu6Px42BC88imed4Ibh7 EZBTYtefG2Dyw6CwpvrpuRrV9PMY7dgZQu63zQW6OvIBBb/Skhmfp/cN/1zjhEUp dgBc5DJ59WStm1XhkW2M165z1lK0hi1UuVJsLxokzxL21p1Xcjg=
    =nCOn
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Grant Edwards@21:1/5 to Neil Bothwick on Fri Aug 5 02:40:01 2022
    On 2022-08-04, Neil Bothwick <[email protected]> wrote:
    On Thu, 4 Aug 2022 21:49:59 -0000 (UTC), Grant Edwards wrote:

    emerge --depeclean --ask

    That removed a couple wayland packages (yay! I didn't really want
    wayland). Then it warned me

    !!! existing preserved libs:
    >>> package: dev-libs/wayland-1.21.0
    * - /usr/lib64/libwayland-client.so.0
    * - /usr/lib64/libwayland-client.so.0.21.0
    * used by /opt/google/chrome/libGLESv2.so
    (www-client/google-chrome-104.0.5112.79) Use emerge @preserved-rebuild
    to rebuild packages using these libraries

    I do as instructed and run 'emerge @preserved-rebuild' and it
    reinstalls chrome.

    But a subsequent emerge --depeclean --ask again produces the same
    warnings about wayland libraries that have been preserved.

    Are the dependencies for chrome broken?

    chrome is a binary package, unlike chromium, so rebuilding will not change the libraries it depends on.

    Right. I didn't expect that it would.

    It sounds like those wayland packages should not have been
    depcleaned and are a requirement for chrome.

    I'm pretty sure that wayland was originally installed a few weeks ago
    to satisfy a dependency of chrome that had been newly added (and now
    apparently removed).

    This bug might be related:

    https://bugs.gentoo.org/858191

    It seems to mostly be a debate over whether wayland is really required
    for the chrome binary package. Removing wayland reportedly breaks
    webGL, sometimes, for some people, depending on how chrome is invoked.

    If I read that issue's history correctly...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)