after having a bug reported, locked screen, and coming back, ubuntu-bug -w leaves a gksudo dialog for dmesg open

[Henning Sprang]

I reported two bugs today, and both times, after having finished reporting the bug, locking my screen, and logging back in, suddenly there was a dialog asking for my sudo password so it can execute dmesg.

But I could neither hit cancel nor could I enter my password, it apperaded that anything I did, especially clicks, made the window *below* the dialog react.

First time I solved it by rebooting (because I had some packages to upgrade anyway), second time by killing gnome-shell and letting it restart.

This dialog definitely did not appear in the process of reporting the bug, the first time it appeared on screen was minutes after completing the bugreports in launchpad, plus locking and unlocking the screen afterwards.

Might also be a problem with gnome-shell or gksudo(?), but it only ever happened to me when using ubuntu-bug -w.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport 2.20.11-0ubuntu50.7
ProcVersionSignature: Ubuntu 5.8.0-59.66-lowlatency 5.8.18
Uname: Linux 5.8.0-59-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
 644:1000:124:0:2021-07-08 04:45:57.713189974 +0200:2021-07-08 04:45:57.713189974 +0200:/var/crash/_usr_bin_jackd.1000.upload
 600:118:124:37:2021-07-08 04:46:00.914606508 +0200:2021-07-08 04:46:00.906605467 +0200:/var/crash/_usr_bin_jackd.1000.uploaded
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 9 01:44:39 2021
InstallationDate: Installed on 2020-04-12 (452 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to groovy on 2020-11-03 (247 days ago)

[Henning Sprang (henning)]

see screenshot - it looks like this after:

* reporting a bug with ubuntu-bug
* locking screen
* logging back in

The dialog does not react on clicks or keyboard input, all input apperas to be going to the underlying app, firefox here.

[Brian Murray (brian-murray)]

What package / application were you reporting a bug about? IIRC most apport hooks won't ask for dmesg information.

If you remove the crash files in /var/crash/ and lock your screen do you get another jackd crash in there? It could be that the crash reporting process for jackd actually is asking for dmesg information.

[Henning Sprang (henning)]

On Fri 9. Jul 2021 at 16:55, Brian Murray <email address hidden>
wrote:

> What package / application were you reporting a bug about? IIRC most
> apport hooks won't ask for dmesg information.
>

Besides automatic crash reports which i haven’t seen happening for
quite some time,
I only used it yesterday for thunderbird and this bug here…

> If you remove the crash files in /var/crash/ and lock your screen do you
> get another jackd crash in there?

Gonna try when back at the device.

It could be that the crash reporting
> process for jackd actually is asking for dmesg information.

Actually i haven’t been aware of a jackd crash recently.

but maybe i just didn’t perceive it as one, while it regularly quits when
switching off my external audio interface - which might look to apport as
unexpected but to me is expected.

I definitely don’t remember apport doing something about an jackd crash
recently , and this effect described here never appeared before having used
ubuntu-bug -w yesterday.

--
Henning Sprang
http://www.sprang.de

[Brian Murray (brian-murray)]

The reason I mentioned jackd is the bug description shows a listing of crashes in /var/crash and there is one from July 8th:

CrashReports:
 644:1000:124:0:2021-07-08 04:45:57.713189974 +0200:2021-07-08 04:45:57.713189974 +0200:/var/crash/_usr_bin_jackd.1000.upload
 600:118:124:37:2021-07-08 04:46:00.914606508 +0200:2021-07-08 04:46:00.906605467 +0200:/var/crash/_usr_bin_jackd.1000.uploaded

[Henning Sprang (henning)]

Yes I understood that, that's why I explained a bit about jack and that I never saw an apport activity or the problem with the dmesg dialog before just because of jackd.

So, I deleted the /var/crash stuff, and locked the screen and back in, as you suggested, but no problem appeared.

I could provoke a jack crash again by switching my sound device off while jack was running.
I get crash reports in /var/crash but no hanging dmesg dialog as described in the original report.

[Henning Sprang (henning)]

I tested a bit more.

I tried again with ubuntu-bug -w and selected thunderbird.

Today I directly get a visible and reacting sudo dialog when reporting a bug for thunderbird.

I am very sure that I did not get this dialog the last time, only as described the broken unresponsive one. Because I also was a bit upset about the amounts of data about my system, my devices, my username, my ip address got attached to my bug...

Anyway, not sure if this a bug in gnome/ gnome-shell rather than ubuntu-bug/apport itself...