Bug 1775729 - fwupd-1.3.5 is available
Summary: fwupd-1.3.5 is available
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fwupd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-22 16:47 UTC by Upstream Release Monitoring
Modified: 2023-09-14 05:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-01 16:12:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2019-11-22 16:47:42 UTC
Latest upstream release: 1.3.4
Current version/release in rawhide: 1.3.3-1.fc32
URL: https://github.com/hughsie/fwupd

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/5833/

Comment 1 Upstream Release Monitoring 2019-11-22 16:47:44 UTC
One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs

Comment 2 Christian Labisch 2019-11-23 15:32:35 UTC
After upgrading fwupd to version 1.3 on fedora 31 workstation, the journal gets flooded with with these kind of messages :

journalctl | grep tpm2-abrmd

Nov 23 16:15:05 cl-fw-1 systemd[1]: tpm2-abrmd.service: Service RestartSec=5s expired, scheduling restart.
Nov 23 16:15:05 cl-fw-1 systemd[1]: tpm2-abrmd.service: Scheduled restart job, restart counter is at 162.
Nov 23 16:15:05 cl-fw-1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=tpm2-abrmd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 23 16:15:05 cl-fw-1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=tpm2-abrmd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 23 16:15:05 cl-fw-1 tpm2-abrmd[4715]: ERROR:tcti:src/tss2-tcti/tcti-device.c:439:Tss2_Tcti_Device_Init() Failed to open device file /dev/tpm0: No such file or directory
Nov 23 16:15:05 cl-fw-1 tpm2-abrmd[4715]: failed to initialize device TCTI context: 0xa000a
Nov 23 16:15:05 cl-fw-1 tpm2-abrmd[4715]: init_thread_func: failed to create TCTI with name "libtss2-tcti-device.so.0" and conf "(null)"
Nov 23 16:15:05 cl-fw-1 tpm2-abrmd[4715]: g_bus_unown_name: assertion 'owner_id > 0' failed
Nov 23 16:15:05 cl-fw-1 systemd[1]: tpm2-abrmd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 16:15:05 cl-fw-1 systemd[1]: tpm2-abrmd.service: Failed with result 'exit-code'.
Nov 23 16:15:05 cl-fw-1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=tpm2-abrmd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Nov 23 16:15:10 cl-fw-1 systemd[1]: tpm2-abrmd.service: Service RestartSec=5s expired, scheduling restart.
Nov 23 16:15:10 cl-fw-1 systemd[1]: tpm2-abrmd.service: Scheduled restart job, restart counter is at 163.
Nov 23 16:15:10 cl-fw-1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=tpm2-abrmd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 23 16:15:10 cl-fw-1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=tpm2-abrmd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 23 16:15:10 cl-fw-1 tpm2-abrmd[4720]: ERROR:tcti:src/tss2-tcti/tcti-device.c:439:Tss2_Tcti_Device_Init() Failed to open device file /dev/tpm0: No such file or directory
Nov 23 16:15:10 cl-fw-1 tpm2-abrmd[4720]: failed to initialize device TCTI context: 0xa000a
Nov 23 16:15:10 cl-fw-1 tpm2-abrmd[4720]: init_thread_func: failed to create TCTI with name "libtss2-tcti-device.so.0" and conf "(null)"
Nov 23 16:15:10 cl-fw-1 tpm2-abrmd[4720]: g_bus_unown_name: assertion 'owner_id > 0' failed
Nov 23 16:15:10 cl-fw-1 systemd[1]: tpm2-abrmd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 16:15:10 cl-fw-1 systemd[1]: tpm2-abrmd.service: Failed with result 'exit-code'.
Nov 23 16:15:10 cl-fw-1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=tpm2-abrmd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

Such messages didn't appear with fwupd version 1.2 - it happens with version 1.3.3 and version 1.3.4 ... every five seconds new entries get created !

fwupdmgr --version
client version:	1.3.4
compile-time dependency versions
	gusb:	0.3.0
	efivar:	37
daemon version:	1.3.4

Comment 3 Richard Hughes 2019-11-25 09:33:18 UTC
What hardware is this? I think it's a tpm2-abrmd bug as the message is "/dev/tpm0: No such file or directory"

Comment 4 Christian Labisch 2019-11-25 09:54:07 UTC
(In reply to Richard Hughes from comment #3)
> What hardware is this? I think it's a tpm2-abrmd bug as the message is
> "/dev/tpm0: No such file or directory"

I don't have any TPM's in use and a /dev/temp0 directory doesn't exist.
As I said, it started to appear after upgrading fwupd to version 1.3.
There were no updates for tpm2-abrmd and tpm2-tools packages lately.

Other users are affected as well : https://www.reddit.com/r/Fedora/comments/e0zwt1/fedora_31_keeps_telling_me_an_update_failed

Comment 5 Christian Labisch 2019-11-25 09:57:33 UTC
(In reply to Christian Labisch from comment #4)
> (In reply to Richard Hughes from comment #3)
> > What hardware is this? I think it's a tpm2-abrmd bug as the message is
> > "/dev/tpm0: No such file or directory"
> 
> I don't have any TPM's in use and a /dev/temp0 directory doesn't exist.
> As I said, it started to appear after upgrading fwupd to version 1.3.
> There were no updates for tpm2-abrmd and tpm2-tools packages lately.
> 
> Other users are affected as well :
> https://www.reddit.com/r/Fedora/comments/e0zwt1/
> fedora_31_keeps_telling_me_an_update_failed

Typo in response : Of course a /dev/tpm0 doesn't exist ... Sorry Richard :)

Comment 6 Christian Labisch 2019-11-25 10:07:03 UTC
(In reply to Richard Hughes from comment #3)
> What hardware is this? I think it's a tpm2-abrmd bug as the message is
> "/dev/tpm0: No such file or directory"

The affected machine is a SCHENKER XMG A704 notebook which is based on CLEVO W370SS barebone.

Comment 7 Upstream Release Monitoring 2019-11-29 18:48:12 UTC
Latest upstream release: 1.3.5
Current version/release in rawhide: 1.3.4-1.fc32
URL: https://github.com/hughsie/fwupd

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/5833/

Comment 8 Upstream Release Monitoring 2019-11-29 18:48:22 UTC
One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs

Comment 9 Christian Labisch 2019-11-30 10:25:42 UTC
@Richard : The problem I've reported still exists after upgrading fwupd to version 1.3.5 !

Comment 10 Richard Hughes 2019-12-01 16:12:31 UTC
> The problem I've reported still exists after upgrading fwupd to version 1.3.5

Right, but it's not upstream. This is an automatically filed bug that is no longer valid. Please create an issue upstream at https://github.com/fwupd/fwupd/issues and we can discuss there.

Comment 11 Red Hat Bugzilla 2023-09-14 05:47:28 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.