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
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
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
On Fri 9. Jul 2021 at 16:55, Brian Murray <1935...@bugs.launchpad.net>
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
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
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.
** Attachment added: "Screenshot from 2021-07-09
