Bug 1955150 - Incorrect file location of the dbus conf file
Summary: Incorrect file location of the dbus conf file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tpm2-abrmd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-29 14:37 UTC by Jóhann B. Guðmundsson
Modified: 2021-06-21 01:03 UTC (History)
4 users (show)

Fixed In Version: tpm2-abrmd-2.4.0-3.fc34
Clone Of:
Environment:
Last Closed: 2021-06-21 01:03:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jóhann B. Guðmundsson 2021-04-29 14:37:54 UTC
Description of problem:
The tpm2-abrmd.conf dbus file should be placed in /usr/share/dbus-1/system.d/ directory not under /etc as per the dbus specification. Not doing so you are also making sure that tpm2-abrmd cant be used on a immutable/volatile system. 

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

All of them 

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fedora Update System 2021-06-12 14:23:37 UTC
FEDORA-2021-59ff4e05ba has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-59ff4e05ba

Comment 2 Fedora Update System 2021-06-13 01:03:50 UTC
FEDORA-2021-59ff4e05ba has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-59ff4e05ba`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-59ff4e05ba

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2021-06-21 01:03:18 UTC
FEDORA-2021-59ff4e05ba has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.


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