In a Debian Testing System one of the packages solved my problem. Secure
Boot is now displayed as active.
Start-Date: 2024-01-12 18:59:31
Commandline: apt full-upgrade
Requested-By: user (1000)
Upgrade: orca:amd64 (45.1-2, 45.2-1), dmeventd:amd64 (2:1.02.185-2,
2:1.02.185-3), libldb2:amd64 (2:2.8.0+samba4.19.3+dfsg-2,
2:2.8.0+samba4.19.4+dfsg-2), libgs10-common:amd64 (10.02.1~dfsg-1,
10.02.1~dfsg-2), liblua5.4-0:amd64 (5.4.6-1, 5.4.6-2),
liblvm2cmd2.03:amd64 (2.03.16-2, 2.03.16-3), libgs10:amd64
(10.02.1~dfsg-1, 10.02.1~dfsg-2), logrotate:amd64 (3.21.0-1, 3.21.0-2),
libwbclient0:amd64 (2:4.19.3+dfsg-2, 2:4.19.4+dfsg-2),
libsmbclient:amd64 (2:4.19.3+dfsg-2, 2:4.19.4+dfsg-2), lvm2:amd64
(2.03.16-2, 2.03.16-3), ghostscript:amd64 (10.02.1~dfsg-1,
10.02.1~dfsg-2), gir1.2-ibus-1.0:amd64 (1.5.29~rc2-1, 1.5.29-1),
grep:amd64 (3.11-3, 3.11-4), libopenni2-0:amd64 (2.2.0.33+dfsg-17,
2.2.0.33+dfsg-18), dmsetup:amd64 (2:1.02.185-2, 2:1.02.185-3),
libdevmapper-event1.02.1:amd64 (2:1.02.185-2, 2:1.02.185-3),
samba-libs:amd64 (2:4.19.3+dfsg-2, 2:4.19.4+dfsg-2), libgs-common:amd64
(10.02.1~dfsg-1, 10.02.1~dfsg-2), libibus-1.0-5:amd64 (1.5.29~rc2-1,
1.5.29-1), libdevmapper1.02.1:amd64 (2:1.02.185-2, 2:1.02.185-3)
End-Date: 2024-01-12 18:59:53
