I have 4 systems that are maintained with identical *.rpm complements, differing only in hostname, IP + VPN configuration, and fstab, along with systemd services and crontabs per their intended uses. Of these, 2 are perfectly fine with the new 495.46, both HPs, one of which is the HP Omen on which I’m typing (RTX 2070 MQ), the other being an old Envy used mostly for utility work (backup mgmt, VPN hub) (840M), these days not used for anything graphics except having a console session.
The other 2 are hardware-identical MSI MPG Trident3 systems, model 10SC-215US, each with RTX 2060. On both (and only) these 2 machines, the update to 495.46 via rpmfusion’s packaging results in a reproducible Xorg (1.20.14) crash during login, only when using MATE desktop (1.26). Logging in to any other desktop (GNOME [both Xorg and Wayland], KDE, ICEwm, BlackBox, even Sugar) works fine. It seems that MATE alone tickles some bug not seen with the others.
The previous 495.44 worked without problem.
dnf downgrade took them back to 470.74. (I don’t know why rpmfusion doesn’t have 495.44 still in place.) Xorg using the downgraded driver works fine, with MATE login producing no complaint.
I have attempted to upload Xorg.1.log but the composition page here keeps complaining of an unspecified “problem.” The short version is that the end of the log concludes, after noting connected and disconnected DFPs, with this:
[ 61623.460] (EE) Backtrace: [ 61623.460] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x55f5490583c9] [ 61623.460] (EE) 1: /lib64/libc.so.6 (__sigaction+0x50) [0x7f06456c2750] [ 61623.460] (EE) 2: ? (?+0x0) [0x0] [ 61623.460] (EE) 3: /usr/libexec/Xorg (miGlyphs+0x5ce1) [0x55f548fdaf91] [ 61623.461] (EE) 4: /usr/libexec/Xorg (present_event_notify+0xa18) [0x55f548fe02e8] [ 61623.461] (EE) 5: /usr/libexec/Xorg (miGlyphs+0x57d1) [0x55f548fdaa81] [ 61623.461] (EE) 6: /usr/libexec/Xorg (miPutImage+0x1570) [0x55f548ee82f7] [ 61623.461] (EE) 7: /lib64/libc.so.6 (__libc_start_call_main+0x80) [0x7f06456ad560] [ 61623.461] (EE) 8: /lib64/libc.so.6 (__libc_start_main+0x7c) [0x7f06456ad60c] [ 61623.461] (EE) 9: /usr/libexec/Xorg (_start+0x25) [0x55f548ee8695] [ 61623.461] (EE) Segmentation fault at address 0x0 Fatal server error: [ 61623.461] (EE) Caught signal 11 (Segmentation fault). Server aborting
Happens every time. The attempt to have ABRT carry out a full report was not useful, concluding with a comment about “no significant information” in what it found.
For the time being, I can continue to use these with 470.74, or I can upgrade again to 495.46 if there is some specific test worth doing – most work on these MSIs is done remotely with VNC + VGL anyhow. Any thoughts on why only MATE, and only these 2 MSIs, have problems with 495.46 would be welcome.