Bug#941076: debsign crashes gnome on wayland session

[Pirate Praveen]

On Wed, 25 Sep, 2019 at 10:47, Pirate Praveen 
<praveen at onenetbeyond.org> wrote:
> 
> 
> On Tue, 24 Sep, 2019 at 11:16, Simon McVittie <smcv at debian.org> wrote:
>> Control: retitle -1 [GNOME 3.34] debsign crashes gnome on wayland 
>> session
>> Control: tags -1 + experimental moreinfo
>> 
>> On Tue, 24 Sep 2019 at 15:33:05 +0530, Pirate Praveen wrote:
>>>  After updating gnome to 2.34
>> 
>> I'm fairly sure you mean 3.34. There was no GNOME 2.34 release: GNOME
>> 2.32 was in 2010, and was followed by 3.0.
>> 
> 
> That was a typo, sorry about that, it is 3.34 indeed.
> 
>> Key GNOME 3.34 components, including gnome-session and gnome-shell, 
>> are
>> currently only in experimental. You're welcome to try it, but please
>> make sure that bug reports are complete, precise and actionable.
>> 
> 
> Since this was a crash of the desktop I was not really sure which 
> component this will belong to.
> 
>>>  I'm not able to use debsign, it crashes the
>>>  desktop. I'm logged out after screen is blacked out.
>> 
>> Please send details of the package versions involved, and whatever
>> backtraces and system log entries are available.
>> 
>> For what it's worth, I have not experienced similar crashes when 
>> using
>> debsign and pinentry-gnome3 in conjunction with a smart card 
>> (Nitrokey
>> Pro) in either a GNOME 3.30 or 3.34 environment. I assume most of the
>> other people uploading GNOME 3.34 for the GNOME team are also using
>> debsign and pinentry-gnome3 in that environment.
>> 
> 
> I looked at apt list --upgradeable | grep gpg and upgraded all the 
> components listed (earlier I tried to update all gnome components 
> thinking it was an issue with gnome).
> 
> gpg-agent/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
> gpg-wks-client/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
> gpg-wks-server/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
> gpg/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
> gpgconf/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
> gpgsm/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
> gpgv/unstable 2.2.17-3 amd64 [upgradable from: 2.2.13-1]
> libgpg-error-dev/unstable 1.36-7 amd64 [upgradable from: 1.31-1]
> libgpg-error0/unstable 1.36-7 amd64 [upgradable from: 1.31-1]
> libgpgme11/unstable 1.13.1-1 amd64 [upgradable from: 1.12.0-6]
> 
> After this upgrade there is no crash. pinentry-gnome3 has 
> libgpg-error0 (>= 1.16) and I wonder if this should be bumped?
> 

Though it did not crash in the same session, it crashed again after a 
reboot.

Versions of packages pinentry-gnome3 depends on:
ii  gcr              3.28.0-1
ii  libassuan0       2.5.1-2
ii  libc6            2.29-2
ii  libgcr-base-3-1  3.28.0-1
ii  libglib2.0-0     2.62.0-1
ii  libgpg-error0    1.36-7
ii  libncursesw6     6.1+20180210-4
ii  libsecret-1-0    0.18.6-2
ii  libtinfo6        6.1+20180210-4

Versions of packages pinentry-gnome3 recommends:
ii  dbus-user-session  1.12.8-3

Versions of packages gnome-session depends on:
ii  gnome-session-bin      3.34.0-1
ii  gnome-session-common   3.34.0-1
ii  gnome-settings-daemon  3.34.0-2
ii  gnome-shell            3.34.0-1

gnome-session recommends no packages.

Versions of packages gnome-session suggests:
ii  desktop-base   10.0.3
ii  gnome-keyring  3.31.91-1

>>     smcv
>