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!
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!
FS#12911 - Kdebase-workspace pam configuration erased by Pacman.
Attached to Project:
Arch Linux
Opened by Paul Ezvan (paulez) - Friday, 23 January 2009, 17:35 GMT
Last edited by Pierre Schmitz (Pierre) - Sunday, 25 January 2009, 11:07 GMT
Opened by Paul Ezvan (paulez) - Friday, 23 January 2009, 17:35 GMT
Last edited by Pierre Schmitz (Pierre) - Sunday, 25 January 2009, 11:07 GMT
|
DetailsDescription:
/etc/pam.d/kde and /etc/pam.d/kde-np are not in the backup array of the package PKGBUILD, so if custom conf is created by the user (for example for LDAP auth), it is erased with an update of the package, and so KDM LDAP login (for example) is broken. Additional info: * package version(s) kdebase-workspace 4.1.3-2 Steps to reproduce: 1 - Configure LDAP auth for KDM ; 2 - Update kdebase-workspace ; 3 - Your conf is lost ! |
This task depends upon
Closed by Pierre Schmitz (Pierre)
Sunday, 25 January 2009, 11:07 GMT
Reason for closing: Fixed
Additional comments about closing: Thanks for the report. Fixed with kdebase-workspace-4.2.0-2
Sunday, 25 January 2009, 11:07 GMT
Reason for closing: Fixed
Additional comments about closing: Thanks for the report. Fixed with kdebase-workspace-4.2.0-2