| Summary: | net-misc/networkmanager-1.22.10-r11: segfault when connecting to openvswitch database | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Stijn Tintel <stijn+gentoo> |
| Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Stijn Tintel
2020-05-25 13:32:18 UTC
Thanks to thaller and bengal for helping me figure this out. Looks like the problem is caused by util-linux. It was upgraded from 2.33.2 to 2.35.1-r2 during my upgrade this weekend. The latter seems to link against libcryptsetup, which in turn links to libjson-c. NM uses jansson instead of json-c, but both libraries have a symbol clash and neither use symbol versioning. So NM now tries to use json-c instead of jansson to talk to ovsdb-server, but the libraries are not compatible and hence the crash. As I have cryptsetup as a global USE flag, the new version of util-linux was built with support for this. From the 2.35 release notes: mount(8) and libmount now provides built-in dm-verity support if linked with libcryptsetup. This new feature is EXPERIMENTAL and disabled by default; use --with-cryptsetup to enable. So I am going to disable this for now. Maybe the NetworkManager ebuild can be changed to depend on util-linux[-cryptsetup]? Reported upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/453 Looks like this is now fixed. |