Description of problem: Sudden and random crashes, fairly consistently, recently at least. Using Mate DE Version-Release number of selected component: gnome-mines-3.28.0-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: gnome-mines crash_function: poll_for_event executable: /usr/bin/gnome-mines journald_cursor: s=41da4eb95bec4a51adf4594cf251f3e0;i=11e5a;b=288cc33a8f4548419084884e6bf93cf5;m=3b664f24f;t=56e89bc358bbc;x=15e0b6bb34d1bb8b kernel: 4.16.14-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001
Created attachment 1453588 [details] File: backtrace
Created attachment 1453589 [details] File: cgroup
Created attachment 1453590 [details] File: core_backtrace
Created attachment 1453591 [details] File: cpuinfo
Created attachment 1453592 [details] File: dso_list
Created attachment 1453593 [details] File: environ
Created attachment 1453594 [details] File: limits
Created attachment 1453595 [details] File: maps
Created attachment 1453596 [details] File: mountinfo
Created attachment 1453597 [details] File: open_fds
Created attachment 1453598 [details] File: proc_pid_status
Assertion is !xcb_xlib_threads_sequence_lost My first guess was that Mines was improperly using GTK+ from a secondary thread, but that does not appear to be the case from the backtrace, so let's reassign to GTK+.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.