Am Sat, Jul 20, 2024 at 03:52:25PM +0200 schrieb Michael Biebl:
> (please leave the moreinfo tag present until we actually have useful
> information to further investigate this)
OK.
> Am 20.07.24 um 14:58 schrieb Andreas Tille:
>
> This doesn't show any problem. Are you sure you ran this command on a system
> showing this failure?
It **WAS** showing the problem. As I said my action (as per the
forum suggested) fixed the problem.
> Or have you manually worked around this in the mean time
This is what I wanted to express.
> Thanks for the bash trace, but this doesn't show any problem.
>
> See my remark above. You obviously need to run this on a system showing the
> problem not where it has been worked around already.
>
> Or better yet, provide concise steps how this can be reproduced.
I guess installing a bullseye system with LXDE (which seems to rely on
policykit somehow - when I tried to remove policykit those lxde packages
would have been deleted as well) and upgrade to bookworm.
There might be a chance to ask the people on the forum about the issue.
I'm obviously not the only one who observed it.
In future I will have to upgrade more such similar systems. If I
meet the error again I will report *before* fixing.
Sorry, I can't deal with this any more now until August since I
prepare to leave for DebConf.
Kind regards
Andreas.
--
https://fam-tille.de
