Bug#1023124: libsystemd-shared-251.so: cannot open shared object file
Luca Boccassi
bluca at debian.org
Mon Oct 31 10:22:22 GMT 2022
Control: tags -1 -moreinfo
Control: close -1
On Sun, 30 Oct 2022 14:56:08 +0100 Salvo Tomaselli
<tiposchi at tiscali.it> wrote:
> systemd-machine-id-setup: /usr/bin/systemd-machine-id-setup
> /bin/systemd-machine-id-setup
> /usr/share/man/man1/systemd-machine-id-setup.1.gz
>
>
> stat /usr/bin/systemd-machine-id-setup /bin/systemd-machine-id-setup
> File: /usr/bin/systemd-machine-id-setup
> Size: 18928 Blocks: 40 IO Block: 4096 regular
file
> Device: 259,5 Inode: 4201937 Links: 1
> Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/
root)
> Access: 2022-10-30 13:34:13.098418093 +0100
> Modify: 2022-08-14 20:06:18.000000000 +0200
> Change: 2022-08-22 15:25:56.730012624 +0200
> Birth: 2022-08-22 15:25:56.610011671 +0200
> File: /bin/systemd-machine-id-setup
> Size: 18928 Blocks: 40 IO Block: 4096 regular
file
> Device: 259,5 Inode: 8650854 Links: 1
> Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/
root)
> Access: 2022-10-30 13:38:20.000000000 +0100
> Modify: 2022-10-14 16:34:00.000000000 +0200
> Change: 2022-10-30 13:38:20.944385494 +0100
> Birth: 2022-10-30 13:38:20.816384357 +0100
>
>
>
> It seems my system is in a weird status from some previous issues…
> Maybe originating when apt told me to split /usr, then I had some
> issues and had to manually install a bunch of packages.
Yes, your system is in a bad state and needs to be fixed, and it has
nothing to do with the systemd packages or this update, so I'll close
this now.
--
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20221031/a628c39a/attachment.sig>
More information about the Pkg-systemd-maintainers
mailing list