[pkg-gnupg-maint] Bug#941076: debsign crashes gnome on wayland session
Simon McVittie
smcv at debian.org
Wed Sep 25 08:54:11 BST 2019
On Wed, 25 Sep 2019 at 12:33:08 +0530, Pirate Praveen wrote:
> On Wed, 25 Sep, 2019 at 12:13, Pirate Praveen <praveen at onenetbeyond.org>
> wrote:
> > I think I found the relevant part from the log. Attaching log from the
> > point of crash.
> >
> > Sep 25 11:44:47 andhaka kernel: gnome-shell[1634]: segfault at 8 ip
> > 00007f85dbfdf468 sp 00007ffda39321c0 error 4 in
> > libgcr-base-3.so.1.0.0[7f85dbfa2000+8c000]
> >
>
> After upgrading libgcr-base-3-1, it does not crash anymore.
> 2019-09-25 12:13:52 upgrade libgcr-base-3-1:amd64 3.28.0-1 3.33.4-2
>
> I tried rebooting and running debsign again. So probably gcr should bump its
> dependency version.
gnome-shell in experimental was compiled against gcr from unstable,
so a higher version in dpkg-shlibdeps wouldn't have helped here; and I
don't see any recent source changes that should have prompted a higher
build-dependency.
Not much has changed in gcr between 3.28 and 3.33 at all, although there
are some annotation fixes that might affect gnome-shell. Did you also
upgrade gir1.2-gcr-3, or just libgcr-base-3-1?
Which gcr-related packages did you upgrade in the transaction that
triggered these crashes? For example, did you upgrade gcr or libgcr-ui-3-1
from experimental?
Which version of gnome-keyring did you have when this crash existed?
Presumably you already had gnome-settings-daemon 3.34.x from experimental
in order to satisfy gnome-shell's dependencies?
Are you able to get a backtrace from this crash? (If you install packages
from experimental, I would suggest installing systemd-coredump, or
corekeeper if you don't use systemd, so that you can get post-mortem
backtraces.)
Thanks,
smcv
More information about the pkg-gnupg-maint
mailing list