Sure, I was not aware test-snapd-rsync-core20 was shipping glibc, that
is indeed not a good idea.
I went looking on my system for other snaps which experienced the crash,
and it seems that every snap that ships glibc in it crashes with the
beta channel of core20, but snaps that (properly) do not ship libc6 in
them do not crash. For example these other well known snaps ship glibc
in them:
* matterhorn
* okular
* htop
and some others that are perhaps less well known. So I think it is
unfortunately a bit common to do this even though it is not advisable.
Sergio, do you know why these snaps would have libc6 staged in them?
Matterhorn for example does not declare libc6 as a stage-package, yet it
is listed as a primed-stage-packages in the manifest.yaml:
```snapcraft.yaml
stage-packages:
- libatomic1
- libsecret-tools
- libnotify-bin
- xclip
```
```manifest.yaml
primed-stage-packages:
- libc6=2.31-0ubuntu9.2
```
** Also affects: snapcraft
Importance: Undecided
Status: New
--
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
