https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #17 from Harald Sitter <[email protected]> --- (In reply to Patrick Silva from comment #16) > Thanks for your detailed explanation Harald. > > libsnapd-glib1 package owns /lib/x86_64-linux-gnu/libsnapd-glib.so.1. > > $ sudo apt-file search /lib/x86_64-linux-gnu/libsnapd-glib.so.1 > libsnapd-glib1: /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1 > libsnapd-glib1: /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1.0.0 It's cool that this worked but there's still something funny about it /lib/x86_64-linux-gnu/libsnapd-glib.so.1 (the path you have) is not /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1 (the path the package has) I have the package installed and the file in /lib doesn't exist for me. Yet they must be the same file otherwise you'd not have managed to generate a trace (gdb resolves symbols by a build-specific debug id set at build time, meaning that since gdb found the symbols it must be the same file from the same build). Perhaps something copied the file to /lib? It's very strange but doesn't really change the fact that we can't resolve the debug package for a file path that dpkg doesn't know about ^^ BTW, you need also libsnapd-qt1-dbgsym. The top most frame still is missing source context. -- You are receiving this mail because: You are watching all bug changes.
