On Fri, 2019-03-22 at 09:52 -0400, Owen Taylor wrote:
I don't think that the blocker process is suitable for this bug -
that doesn't mean that we shouldn't try to get it fixed.
Things you can do if you think a bug isn't getting enough attention:
* Make sure there's an upstream bug tracking the problem.
is similar -
it's also a BadWindow X error caused by a ChangeProperty request, but
since nobody mentions closing windows, it's probably not the same. The
debugging advice in
put GDK_SYNCHRONIZE=1 in /etc/environment is useful.)
Looking through the /var/log/messages attachments - these are extracts
from the journal around the time of the crash, libreport provides this
- about half of them have something like this right before the
Dec 16 03:03:16 red-dwarf org.gnome.Shell.desktop: libinput
error: client bug: timer event5 debounce short: offset negative (-2ms)
I'm not sure if it's significant, though.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net