https://bugs.kde.org/show_bug.cgi?id=380496
Aleix Pol <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #7 from Aleix Pol <[email protected]> --- (In reply to Antonio Rojas from comment #4) > @Aleix I've gotten a few reports of this one, though I can't reproduce it > myself. It happens when flatpak is not installed but packagekit is, not when > both are installed or both aren't. See > https://bbs.archlinux.org/viewtopic.php?id=226752 for more details including > a BT with debug symbols This is certainly a weird bug report. So, it looks like what's happening is ld loading flatpak-backend.so which uses libappstream.so and libflatpak.so. libappstream is loaded but libflatpak isn't because it isn't there. It's libappstream when is loaded again by the flatpak backend that it explodes. I use ArchLinux but Qt5/KF5 compiled locally in debug mode and it does work for some reason. :( I have never seen anything like this and I can't think of something I can do fix it on Discover side. What other distros do is to split the flatpak-backend package and make it depend on flatpak. One thing we could do is maybe to look for flatpak (as in `which flatpak`) before actually loading it, but I'd prefer we didn't have to get to that. What do you think Antonio? -- You are receiving this mail because: You are watching all bug changes.
