Created attachment 1240855 [details] .xsession-errors.old Description of problem: Mate crashes(along with all user processes) after certain pages loads in firefox. I don't know exactly what the page characteristics are that cause it but it doesn't happen until the page is actually displayed. If I open in a new tab the crash does not occur until I select that tab. I think this is a GTK issue as it only started happening after I pulled an update yesterday. Version-Release number of selected component (if applicable): gtk-update-icon-cache-3.22.6-2.fc25.x86_64 gtk3-3.22.6-2.fc25.x86_64 firefox-50.1.0-1.fc25.x86_64 mate-desktop-1.16.1-2.fc25.x86_64 How reproducible: Steps to Reproduce: 1. Login to mate desktop 2. Start firefox 3. Click on a link to a problem webpage Actual results: Page displayed Expected results: Mate crashes and login screen is shown Additional info: While I can't generate this on demand, when it does happen it will consistently reproduce after logging in again and restarting firefox. Opening up the page from the restore session feature and clicking the link will cause Mate to reliably crash. This shows up in .xsession-errors.old: Gdk-Message: mate-terminal: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. This only started happening after an update around 5:00pm eastern on 1/13. Attached is the list of package updates.
Created attachment 1240856 [details] Modified 'dnf history info' output from 1/13
It seems I can reproduce this behavior right here on bugzilla with this link: https://bugzilla.redhat.com/show_bug.cgi?id=1292322
I tried another Intel iGPU system with F25/Mate and there's no issue. The failing system has Intel GM45 Express Chipset.
This isn't a gtk issue. After more debugging, downgrading the following two packages fixes the issue: Upgraded xorg-x11-server-Xorg-1.19.0-3.fc25.x86_64 @updates Upgrade 1.19.1-1.fc25.x86_64 @updates Upgraded xorg-x11-server-common-1.19.0-3.fc25.x86_64 @updates Upgrade 1.19.1-1.fc25.x86_64 @updates Also it's not just firefox: * VLC can trigger the crash by opening an audio network stream. * The ABRT gui when clicking the configure button for workflows.
Can you please provide the Xorg log after the crash (~/.local/share/xorg/*), it should contain a backtrace if Xorg crashed
It looks like this has been fixed in 1.19.1-3.