Indeed, right now it seems to only support fuse2 libfuse-dev Run-time dependency fuse found: YES 2.9.9
libfuse3-dev Run-time dependency fuse found: NO (tried pkgconfig and cmake) This is only needed for libvirt-lxc which is universe only and strongly discouraged in favor of LXD (much better for the same use case). Introduced in [1] and not much changed since then it is pre-3.0 as that didn't exist back in 2012 afaik. I'll file an issue upstream to support fuse3 as I'm convinced it is generally the right thing. But if this is the last issue holding us back we can as well disable fuse support in ubuntu's libvirt without much consequence for users (libvirt-lxc still works, just some /proc info isn't as isolated) Note [2] holds transition instructions. And [3] shows that plenty of upstream projects got bugs filed back then when 3.0 released. Many of them changed, libvirt didn't get a bug back then and might therefore not be aware yet. Prio wishlist, since as I said worst-case we can disable it. [1]: https://libvirt.org/git/?p=libvirt.git;a=commit;h=2a596dac5e00c4fcf750a693fd6174b68188efc3 [2]: https://github.com/libfuse/libfuse/blob/master/ChangeLog.rst#libfuse-300-2016-12-08 [3]: https://letmegooglethat.com/?q=%22This+is+a+maintenance+release+from+the+2.9+branch+of+libfuse.+Users+are+encouraged+to+transition+to+the+actively+developed+libfuse+3.x.%22 ** Changed in: libvirt (Ubuntu) Importance: Undecided => Wishlist ** Changed in: libvirt (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935664 Title: Please switch to fuse3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1935664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
