On Mon, 29 Jan 2018 01:34:38 +0100 Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: Thanks for the reply. > Hi Stan! One *possible* source of this might be a recent glibc change: > > * Fri Jan 19 2018 Björn Esser <besser82@xxxxxxxxxxxxxxxxx> - > 2.26.9000-46 > - Remove deprecated libcrypt, gets replaced by libxcrypt > > you could try downgrading to a glibc from before that and see if it > helps? Only a possibility, though. Thanks! It fits the time frame. Name : libxcrypt Version : 4.0.0 Release : 0.204.20180120git3436e7b.fc28 Architecture: x86_64 Install Date: Thu 25 Jan 2018 02:36:09 PM MST Name : glibc Version : 2.26.9000 Release : 48.fc28 Architecture: x86_64 Install Date: Thu 25 Jan 2018 02:36:05 PM MST The libxcrypt info says ... programs linked against libxcrypt will not work with glibc's libcrypt ... I think that means an earlier glibc might cause problems with libxcrypt installed, since programs must be linked against it, though I'll still try it. _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
