Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#80192 - [phosh] Lock screen does not accept user PIN/passphrase due to missing PAM configuration

Attached to Project: Arch Linux
Opened by eomanis (eomanis) - Tuesday, 07 November 2023, 21:22 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 11 November 2023, 13:43 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Upon locking the phosh session, unlocking it again with the PIN or passphrase is impossible; the correct PIN/passphrase is rejected by the lock screen, making phosh effectively unusable.
This is because the package does not ship an appropriate /etc/pam.d/phosh file.

The issue is known to the AUR package [1] that precedes this precompiled package; the AUR package manually adds such a file.
Manually placing the AUR package's pam_phosh file [2] into the file system as /etc/pam.d/phosh resolves the issue.

Additional info:
* package version(s): phosh-0.32.0-1
* config and/or log files etc.: (not available)
* link to upstream bug report, if any: AUR comment [3]

Steps to reproduce:
* Install phosh
* Create a new user with a login PIN/passphrase
* Log out
* In GDM, log in as the new user using phosh as desktop environment
* Lock the phosh session
* Attempt to unlock the phosh session with touch input

[1] https://aur.archlinux.org/packages/phosh
[2] https://aur.archlinux.org/cgit/aur.git/tree/pam_phosh?h=phosh
[3] https://aur.archlinux.org/packages/phosh#comment-942359
This task depends upon

Closed by  Jelle van der Waa (jelly)
Saturday, 11 November 2023, 13:43 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 0.32.0-2 in [testing] and soon [extra].

Loading...