With the test snap that uses core20 as it's base, test-snapd-rsync- core20 (installable on the edge channel), I see it segfaulting when running the snap on both a UC20 system with the core20 snap as a base snap, as well as on my groovy desktop:
https://pastebin.ubuntu.com/p/qbq86DYw5Q/ You can reproduce this with: ``` snap install core20 --beta || snap refresh core20 --beta snap install test-snapd-rsync-core20 --edge snap run --experimental-gdbserver test-snapd-rsync-core20.rsync ... you will see the gdb command to use to connect to the gdbserver running inside the snap's mount namespace gdb -ex="target remote :33021" -ex=continue -ex="signal SIGCONT" # in another window ``` My gdb output seems to imply the segfault is coming from 0x000056287d57a2d4 in time@plt ? I haven't been able to load debug symbols for this gdb version into the snap mount namespace yet so I don't have more info, but presumably you could copy debug symbols into the snap's dir somewhere like $HOME/snap/test-snapd-rsync- core20/current/debug.sym and then load it from the gdb shell. For reference, I've also attached the output of strace too in case that's more useful: https://pastebin.ubuntu.com/p/rpqKrnBHrg/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926355 Title: Snap applications segfault with new core20 (rev: 1015+) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-core20/+bug/1926355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
