[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1003457: noisy fwupd error messages with (disabled) TPM 1.2



Package: fwupd
Version: 1.7.4-1
Followup-For: Bug #1003457

Dear Maintainer,

And also by the way without TPM at all:

[    1.278203] ima: No TPM chip found, activating TPM-bypass!

fwupd[2813]: 17:27:38:0894 FuPluginTpm          failed to load eventlog: Failed
to open file "/sys/kernel/security/tpm0/binary_bios_measurements": No such file
or directory

Thanks!
Patrice



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.0-rc8-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fwupd depends on:
ii  libc6                  2.33-2
ii  libcurl3-gnutls        7.81.0-1
ii  libefiboot1            37-6
ii  libflashrom1           1.2-5
ii  libfwupd2              1.7.4-1
ii  libfwupdplugin5        1.7.4-1
ii  libglib2.0-0           2.70.2-1
ii  libgnutls30            3.7.2-5
ii  libgudev-1.0-0         237-2
ii  libgusb2               0.3.8-1
ii  libjcat1               0.1.9-1
ii  libjson-glib-1.0-0     1.6.6-1
ii  libpolkit-gobject-1-0  0.105-31
ii  libprotobuf-c1         1.3.3-1+b2
ii  libsmbios-c2           2.4.3-1
ii  libsqlite3-0           3.37.2-2
ii  libsystemd0            250.2-3
ii  libtss2-esys-3.0.2-0   3.1.0-3
ii  libxmlb2               0.3.6-2
ii  shared-mime-info       2.1-2

Versions of packages fwupd recommends:
ii  bolt            0.9.1-2
ii  dbus            1.12.20-3
pn  fwupd-signed    <none>
pn  fwupd-unsigned  <none>
ii  python3         3.9.8-1
pn  secureboot-db   <none>
ii  udisks2         2.9.4-1

Versions of packages fwupd suggests:
pn  gir1.2-fwupd-2.0  <none>

-- no debconf information


Reply to: