Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2127183 - Backport upstream d4001c5 commit to fix missing Device Security panel in Settings
Summary: Backport upstream d4001c5 commit to fix missing Device Security panel in Sett...
Keywords:
Status: CLOSED DUPLICATE of bug 2129343
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-15 15:09 UTC by hozhengxuan
Modified: 2022-10-01 18:41 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-01 18:41:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description hozhengxuan 2022-09-15 15:09:32 UTC 
Description of problem:
When requesting the chassis type through systemd-hostnamed, it sometimes
returns an empty string, causing Device Security panel in Settings to be hidden. The fix has been backported upstream to v251-stable through commit d4001c5.
https://github.com/systemd/systemd/commit/d4001c518a5a3b5b22fd74983e413d0242b84b5e
https://github.com/systemd/systemd/pull/24385

Version-Release number of selected component (if applicable):
251

How reproducible:

Steps to Reproduce:
1. Terminal: "$ hostnamectl chassis"

Actual results:
Value returned is empty string

Expected results:
Value returned should be 'laptop' in my case

Additional info:
Original upstream bug report(https://github.com/systemd/systemd/issues/24384) was produced in a VM, but it happens in my case which is on real hardware too. Nonetheless the upstream fix should be good enough for all cases.
Comment 1 Zbigniew Jędrzejewski-Szmek 2022-10-01 18:41:49 UTC 

*** This bug has been marked as a duplicate of bug 2129343 ***
Note You need to log in before you can comment on or make changes to this bug.