Hi Sid, I just performed an update and hit the same problem. Digging a bit, I see the network:wicked:master logs pointing to builds involving libgcrypt-1.6.2, yet both my systems still have 1.6.1. To confirm, I did a quick local RPM build of wicked on my system with ligbcrypt-1.6.1. This fixed this little hiccup. I suppose the updated libgcrypt has not yet been released? # zypper up libgcrypt20 Loading repository data... Reading installed packages... No update candidate for 'libgcrypt20-1.6.1-11.2.x86_64'. The highest available version is already installed. Resolving package dependencies... -Karol On Mon, Nov 17, 2014 at 09:39:21PM +0000, Sid Boyce wrote:
No problem on 2 other x86_64 boxes with factory at the latest level via zypper dup with the same versions of libgcrypt and wicked.
tindog:~ # systemctl status wickedd.service wickedd.service - wicked network management service daemon Loaded: loaded (/usr/lib/systemd/system/wickedd.service; enabled) Active: failed (Result: exit-code) since Mon 2014-11-17 21:02:43 GMT; 6min ago Process: 655 ExecStart=/usr/sbin/wickedd --systemd --foreground (code=exited, status=1/FAILURE) Main PID: 655 (code=exited, status=1/FAILURE)
Nov 17 21:02:43 tindog wickedd[655]: libgcrypt version mismatch