Hi Paolo. I unfortunately have only a few hours per month for studying
these, and this particular laptop is already now going to be with a user
that I can't that easily reach. Since the user really needs the feature,
I enabled LTS upgrades and switched to 24.04, hopefully without any
other regressions, and there this feature works (again) so I didn't need
to use the Lenovo recovery media to switch back.
However, I will note that I managed to boot the original installation to
the original (as of that time still installed) linux-oem-kernel together
with the mutter 42.9-0ubuntu7, and that did not resolve the issue, so
I'm a bit unsure what could be the cause unless I did a mistake in that
testing. It's almost as if the key press Fn+D is double interpreted, so
maybe it's input related and not mutter or kernel related (but doesn't
mutter handle input too to an extent?). It cannot be firmware related
because T14s Gen 5 didn't have any updates available yet.
The pre-installed OEM image seemed to be dated about March, there
haven't been eg meaningful gnome-control-center updates since then.
I do have access to another T14s Gen 5 with Privacy Screen and will be
able to access it on certain Mondays, and I can try your custom kernel
with that at some point, but it's a longer term thing. Also, if it's not
a kernel related item after all then that custom build wouldn't help and
I would need guesses on what other packages to downgrade. That machine
is currently on default OEM configuration - which as of September update
to oem-sutton-carr-meta switched to 6.8 generic kernel - and it was also
observed the Privacy Screen no longer works like it did in the very
beginning but that user is ok without it.
If you have some other developer with a such machine, the test steps
should be relatively easy once you install the recovery image, observe
it works, then update to up-to-date 22.04 (on OEM machines LTS -> LTS
upgrades aren't default so all one gets is 22.04 updates). According to
changelogs at least Marco Trevisan was working on Mutter related
enablement so had access to a computer or access to someone with the
computer.
Anyway, hints about what to try to debug if/when I have access to
suitable machine are welcome. I will not be able to do reinstallation,
but can downgrade any package to any earlier version or install custom
packages. I'm mostly interested in how the "enabled-disabled" could
happen in practice. I originally thought the feature is "erroring" and
then reverting, but because it actually _does_ enable the privacy screen
for a fraction of a second, I'm wondering whether it indeed could be
input related problem.
** Changed in: mutter (Ubuntu)
Status: New => Fix Released
** Changed in: linux-hwe-6.8 (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085119
Title:
Regression on Ubuntu 22.04 LTS after upgrading from shipped OEM
installation to current versions of 22.04 - Lenovo privacy guard does
not work (flashes on and then off)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085119/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
