On 05/23/18 04:24, Rick Stevens wrote:
On 05/22/2018 10:32 AM, Francis.Montagnac(a)inria.fr wrote:
> On Tue, 22 May 2018 09:56:25 -0700 Rick Stevens wrote:
>
>> And I just had lightdm screw up royally. First, upon login I got an
>> XFCE polkit error popup, which is singularly useless in telling you
>> anything you can troubleshoot with. Then, I had no access to the sound
>> hardware on my machine, nor could I enable/disable wireless, play
>> with firewall settings or anything else, as polkit thought I didn't have
>> permissions to do anything, nor did it ever pop up an authentication
>> dialog.
> This is not the fault of lightdm but of pam-kwallet. See this other
> thread:
>
> F27 problems with pam?
>
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
Well, very that's very interesting and, yup, that appears to be what I'm
dealing with. Really odd that lightdm would have such a dependency. I
could see it if I were using KDE, but wow!
FWIW, I have an F28/xfce system installed in a VM. It uses lightdm
root 776 1 0 05:54 ? 00:00:00 /usr/sbin/lightdm
root 876 776 0 05:54 tty1 00:00:10 /usr/libexec/Xorg -core -noreset :0
-seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch -background none
root 1058 776 0 05:54 ? 00:00:00 lightdm --session-child 12 19
The only "pam" packages installed on the system are...
gnome-keyring-pam-3.28.2-1.fc28.x86_64
pam-1.3.0-10.fc28.x86_64
systemd-pam-238-8.git0e0aa59.fc28.x86_64
pam_krb5-2.4.13-9.fc28.x86_64
fprintd-pam-0.8.0-2.fc28.x86_64
So, it seems to me, something else you've installed on your system pulled in
pam-kwallet and it isn't lightdm.
Maybe try removing it to see what else it tries to remove?
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.