On Thu, 2019-03-21 at 19:34 -0400, John Mellor wrote:
Is it possible to add fatal issue 1633365 to the list of blocker
Almost everyone running F28 and F29 Gnome desktop worldwide has
reported some variant of this very high severity evolution bug that
easily causes a full desktop crash. I believe that its time to get
this bug to block the next release.
FWIW, I run Evo on three systems, on F28, F29 and F30, and haven't ever
seen that. (Though I don't exit it very often; perhaps you could use
this as a workaround. :>)
Also note that several reporters *weren't* doing anything with Evo when
it crashed...e.g. comment #52, comment #57, #59, #44, #41, #27, #25,
Shell crashers can be release blockers if they're common enough, it
depends on several factors. This is also quite a messy one, because the
backtrace in fact just shows that GNOME crashed on an X protocol error:
Sep 26 15:10:56 paul-fedoradesktop gnome-shell: The program 'gnome-shell'
received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 34996 error_code 3 request_code 18 (core protocol) minor_code 0)
which means the trace isn't a lot of use, we need to know what caused
that error to happen. It also means some of the dupes may not actually
be the same bug at all.
I'll look into it a bit...
Anyone can propose any bug as a release blocker, there is no special
requirement for this. You do it at
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net