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 - but > 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. > > (https://gitlab.gnome.org/GNOME/gnome-shell/issues/375 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 > https://gitlab.gnome.org/GNOME/gnome-shell/issues/375#note_376065 to > 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 'badwindow' error: Dec 16 03:03:16 red-dwarf org.gnome.Shell.desktop[2790]: libinput error: client bug: timer event5 debounce short: offset negative (-2ms) I'm not sure if it's significant, though. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/desktop@xxxxxxxxxxxxxxxxxxxxxxx
