Adding "list" back into the reply...
On 06/02/18 11:41, Michael D. Setzer II wrote:
>
> These are the following things I would do/check....
>
> 1. You are running xfce and if you are also running lightdm as your display manager
> I would, based on another thread, check to see if the system has a
> /usr/lib64/security/pam_kwallet5.so file.
I had seen the messages earlier about issues with the pam_kwallet, so I
believe I removed that package on all my systems at home, but will have to
double check on these machines, since they are not my primary machines.
Generally have both gnome and xfce on machines. Usually local login is with
gnome, vnc session using the xfce.
OK...
> 2. Go to /var/lib/NetworkManager/ and delete any *lease files
and then try again.
Will check this, but getting ready to leave for summer vacation in 3 days, so
will have to see.
Not sure how this would get changed from one kernel to another. All the
previous kernels worked, and rebooting with the prior kernel works, so not
sure what would be changing configuration.
OK.... These are just things that I would do. In picking what I do I push out the
natural tendency to think "that can't be it". :-)
> 3. Again in /var/lib/NetworkManager/ check to see if there is a difference in the
> dhclient-enp0s3.conf file in the working case v.s. failing case
Again, not sure how booting a different kernel would make modifications to
this file?
Same with the other 3, why it works fine with the prior kernel, but not with the
latest, would leave me to think it is something that is different in the latest
kernel. I didn't see anything that showed the exact problem, and that is why I
included all of the journal stuff.
I leave no stone un-turned.
The dhclient-enp0s3.conf is a generated file. I think you'll notice that if you boot
with a static IP address that file doesn't exist and when you boot with
"automatic"
addresses configured it will have the timestamp of when the boot occured.
Thanks again, for the time.
> 4. Use wireshark and verify that the DHCP request is actually going out on the
wire.
>
> 5. Long shot.... "systemctl stop firewalld" and try again.
>
> 6. Longer shot.... "setenforce 0" and try again.
>
I probably should have put #4 at #1.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.