Bug 1958542 - Misleading comment in the logind configuration file
Summary: Misleading comment in the logind configuration file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 34
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: 2021-05-08 16:44 UTC by Göran Uddeborg
Modified: 2023-04-26 20:18 UTC (History)
13 users (show)

Fixed In Version: systemd-248.2-1.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-11 02:08:20 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Göran Uddeborg 2021-05-08 16:44:43 UTC 
Description of problem:
The comment in the beginning of /etc/systemd/logind.conf says

    # should be created by either modifying this file, or by creating "drop-ins" in
    # the system.conf.d/ subdirectory. The latter is generally recommended.

However, the correct subdirectory seems (according to the manual and my own experimentation) to be logind.conf.d.
Comment 1 Göran Uddeborg 2021-05-08 18:44:22 UTC 
Looking closer, it seems the analogous problems applies to most if not all /etc/systemd/*.conf files. All of them refer to system.conf.d rather than their respective *.conf.d directories. (The comment is correct in system.conf.)

systemd-248-2.fc34.x86_64
Comment 2 Zbigniew Jędrzejewski-Szmek 2021-05-09 08:04:31 UTC 
We're one step ahead already ;)
Comment 3 Fedora Update System 2021-05-09 08:05:01 UTC 
FEDORA-2021-775e2373a1 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-775e2373a1
Comment 4 Fedora Update System 2021-05-11 02:08:20 UTC 
FEDORA-2021-775e2373a1 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 5 Göran Uddeborg 2021-05-11 18:42:21 UTC 
Looks good now. Quick fix! :-)
Comment 7 Göran Uddeborg 2023-04-25 09:40:58 UTC 
This was fixed just a few days after the report.
Note You need to log in before you can comment on or make changes to this bug.