Bug 1822227 - remove pam_console dependency in lxdm
Summary: remove pam_console dependency in lxdm
Alias: None
Product: Fedora
Classification: Fedora
Component: lxdm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 2166692
TreeView+ depends on / blocked
Reported: 2020-04-08 14:12 UTC by Iker Pedrosa
Modified: 2023-03-02 11:04 UTC (History)
2 users (show)

Fixed In Version: lxdm-0.5.3-26.D20220831git2d4ba970.fc39
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-03-02 11:04:33 UTC
Type: Bug

Attachments (Terms of Use)

Description Iker Pedrosa 2020-04-08 14:12:01 UTC
Description of problem: pam_console is mostly broken and needs to be deleted. This package has some dependencies with it that have to be removed beforehand. I have found that at least pam/lxdm and pam.lxdm depend on pam_console but please check for any other hidden dependency.

Comment 1 Mamoru TASAKA 2020-04-16 05:11:35 UTC
Well, I cannot judge anything from the word "mostly broken" or so.

* Please provide the information how it is broken
* And can you provide some information that it is really safe to remove pam_console without breaking anything else?

Comment 2 Iker Pedrosa 2020-04-16 09:11:02 UTC
* The module is not included into the upstream Linux PAM sources, thus it is not maintained by the community. Moreover, the management of user sessions is taken over by systemd.
* From what I can see in this package, pam stack settings have the following: "session    optional    pam_console.so"
The purpose of that line is to configure and manage user sessions with pam_console. If it success it will change permissions and ownership of files as described in the file /etc/security/console.perms, which nowadays is empty. So, it will have no effect. If it fails the configuration process can continue and the failure is recorded[1].

[1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system-level_authentication_guide/pam_configuration_files

Comment 3 Ben Cotton 2020-08-11 13:17:05 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 4 Ben Cotton 2021-11-04 17:39:56 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2022-02-08 21:32:55 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 6 Fedora Admin user for bugzilla script actions 2023-02-16 12:37:41 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 7 Fedora Update System 2023-03-02 11:02:52 UTC
FEDORA-2023-2d01217888 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-2d01217888

Comment 8 Fedora Update System 2023-03-02 11:04:33 UTC
FEDORA-2023-2d01217888 has been pushed to the Fedora 39 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.