today's updates - chrome bork

[Jeffrey Walton]

On Thu, May 25, 2023 at 6:30 PM Jack Dangler <tdldev at gmail.com> wrote:
>
> Good morning -
>
> Just ran today's updates on my Ubu laptop
>
> Distributor ID:    Ubuntu
> Description:    Ubuntu 22.04.2 LTS
> Release:    22.04
> Codename:    jammy
>
> and since the reboot, Chrome seems to have lost its way. Not sure it was
> specifically a Chrome issue, I grabbed the hist log latest updates
> (since that was the last thing I did this morning) and got this -
>
> Start-Date: 2023-05-25  06:30:06
> Commandline: /usr/bin/unattended-upgrade
> Upgrade: libbinutils:amd64 (2.38-4ubuntu2.1, 2.38-4ubuntu2.2),
> binutils-x86-64-l
> inux-gnu:amd64 (2.38-4ubuntu2.1, 2.38-4ubuntu2.2), libctf0:amd64
> (2.38-4ubuntu2.
> 1, 2.38-4ubuntu2.2), binutils-common:amd64 (2.38-4ubuntu2.1,
> 2.38-4ubuntu2.2), b
> inutils:amd64 (2.38-4ubuntu2.1, 2.38-4ubuntu2.2)
> End-Date: 2023-05-25  06:30:06
>
> Start-Date: 2023-05-25  06:30:09
> Commandline: /usr/bin/unattended-upgrade
> Upgrade: ca-certificates:amd64 (20211016ubuntu0.22.04.1,
> 20230311ubuntu0.22.04.1
> )
> End-Date: 2023-05-25  06:30:11
>
> Start-Date: 2023-05-25  06:30:12
> Commandline: /usr/bin/unattended-upgrade
> Upgrade: libctf-nobfd0:amd64 (2.38-4ubuntu2.1, 2.38-4ubuntu2.2)
>
> Start-Date: 2023-05-25  09:33:23
> Commandline: aptdaemon role='role-commit-packages' sender=':1.903'
> Upgrade: dpkg:amd64 (1.21.1ubuntu2.1, 1.21.1ubuntu2.2),
> libglx-mesa0:amd64 (22.2.5-0ubuntu0.1~22.04.1,
> 22.2.5-0ubuntu0.1~22.04.2), apport-gtk:amd64 (2.20.11-0ubuntu82.4,
> 2.20.11-0ubuntu82.5), libgbm1:amd64 (22.2.5-0ubuntu0.1~22.04.1,
> 22.2.5-0ubuntu0.1~22.04.2), libxatracker2:amd64
> (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2),
> libegl1-mesa:amd64 (22.2.5-0ubuntu0.1~22.04.1,
> 22.2.5-0ubuntu0.1~22.04.2), mesa-va-drivers:amd64
> (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2),
> libgl1-mesa-dri:amd64 (22.2.5-0ubuntu0.1~22.04.1,
> 22.2.5-0ubuntu0.1~22.04.2), libgl1-mesa-glx:amd64
> (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2), dpkg-dev:amd64
> (1.21.1ubuntu2.1, 1.21.1ubuntu2.2), mesa-vulkan-drivers:amd64
> (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2),
> libdpkg-perl:amd64 (1.21.1ubuntu2.1, 1.21.1ubuntu2.2),
> libglapi-mesa:amd64 (22.2.5-0ubuntu0.1~22.04.1,
> 22.2.5-0ubuntu0.1~22.04.2), python3-apport:amd64 (2.20.11-0ubuntu82.4,
> 2.20.11-0ubuntu82.5), libegl-mesa0:amd64 (22.2.5-0ubuntu0.1~22.04.1,
> 22.2.5-0ubuntu0.1~22.04.2), mesa-vdpau-drivers:amd64
> (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2),
> python3-problem-report:amd64 (2.20.11-0ubuntu82.4, 2.20.11-0ubuntu82.5),
> apport:amd64 (2.20.11-0ubuntu82.4, 2.20.11-0ubuntu82.5)
> End-Date: 2023-05-25  09:33:27
>
> As there was some activity with va drivers in there, I added this update
> for a look-see -
>
> Start-Date: 2023-05-25  10:46:11
> Commandline: apt install vainfo
> Requested-By: jack (1000)
> Install: vainfo:amd64 (2.12.0+ds1-1), libva-wayland2:amd64 (2.14.0-1,
> automatic)
> End-Date: 2023-05-25  10:46:12
>
> Output of vainfo --display wayland
>
>   vainfo --display wayland
> libva info: VA-API version 1.14.0
> libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
> libva info: Found init function __vaDriverInit_1_14
> libva info: va_openDriver() returns 0
> vainfo: VA-API version: 1.14 (libva 2.12.0)
> vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics -
> 22.3.1 ()
> vainfo: Supported profile and entrypoints
> {followed by long list of extraneous details}
>
> I tried running chrome at CLI with --va flag, but it does not change the
> behavior. It's hard to describe how it is behaving, but I can say that I
> have two other browsers on this box and they both work fine. I guess I
> could transfer all of my bookmarks over to FF and run with it until the
> next update, but I'd like to get a fix in for it if possible. Thanks for
> any input or guidance.

You did not state the problem you are experiencing. "Chrome seems to
have lost its way" is not a good problem statement.

Jeff