Comment 23 for bug 2035406

On Thu, Sep 14, 2023 at 07:52:49PM -0000, Philip A Swiderski Jr wrote:
> PROBLEM STILL PERSISTS, and Now I HAVE NO AUDIO.

You didn't show the output of the apt command or otherwise confirm, but I
did stipulate that:

> This should offer to downgrade all binary packages from the systemd source
> package to the current jammy-updates versions, without removing any other
> packages.

If other packages were removed, but you proceeded with the downgrade, then
there could understandably be other regressions.

If no other packages were removed, but systemd was downgraded to the
249.11-0ubuntu3.9 version that you had installed before the most recent
stable release update, and you are having these problems, then there is no
evidence to indicate these problems are caused by either the downgrade, OR
the upgrade of systemd.

> Because they can not talk to the camera, I understand the appimage has
> everything self contained, so it makes sense it works that way.

No, that doesn't make sense, because the only point at which any of these
applications, either as appimage or deb, should be interacting with anything
handled by systemd, is when opening the device file and either succeeding
or getting permission denied. This is a question of udev acls, which should
apply equally to the appimage and the native .deb, unless the appimage runs
as a different user with different privileges. (And if it runs with
different privileges, whatever is setting up those "different privileges"
could be the actual source of your bug.)

My next step for debugging this problem would be to run 'strace -efile
digikam 2>&1 | grep /dev.*EPERM' to confirm whether there is a permissions
problem on your device files.

> Now back to re-installing
> ubuntu and putting it all back together, hoping your update does not
> break it again.

Yours is the only bug report of problems with this SRU and it so far has not
been reproducible. If we continue to be unable to reproduce it and you are
not able to assist with further debugging to isolate the problem on your
system, then this bug will eventually be closed and the update will be
re-published to jammy-updates.