Re: [gentoo-user] X11 crashes anyone?

[Michael <confabulate@kintzios.com>]

[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]

On Monday, 20 December 2021 07:10:59 GMT Nikos Chantziaras wrote:
> Has anyone here noticed that x.org likes to crash sometimes as of late?
> Never happened before, going years and years back. The last month or so,
> I've got three x.org crashes:
> 
> systemd-coredump[204553]: [🡕] Process 453 (X) of user 0 dumped core.
> 
> This is x11-base/xorg-server-21.1.2-r2.
> 
> qlop -v x11-base/xorg-server says:
> 
>    2021-08-04T17:58:15 >>> x11-base/xorg-server-1.20.13-r1: 52s
>    2021-11-30T16:15:54 >>> x11-base/xorg-server-21.1.1: 28s
>    2021-12-03T18:49:22 >>> x11-base/xorg-server-21.1.1-r2: 27s
>    2021-12-16T17:08:40 >>> x11-base/xorg-server-21.1.2: 24s
>    2021-12-19T21:57:08 >>> x11-base/xorg-server-21.1.2-r2: 25s
> 
> So it seems this coincides with the upgrade from 1.20.13 to 21.1.1 about
> a month ago.
> 
> Anyone else seeing this?

I have been suffering similar symptoms[1] on a AMD Kaveri APU powered box, 
running plasma with two monitors, which worsened[2] in the last couple of 
weeks.  All other boxen work fine, so I assumed some Radeon driver issue 
specific to this machine.

[1]  For some months now the RH monitor would not acquire the correct 
resolution.  The workaround I came up with, until I have some time to 
troubleshoot it, was to go into SystemSettings/Display, disable the RH monitor 
and then re-enable it.  This process is more painful than it sounds, because 
clicking on Plasma desktop GUI menus does not update the screen.  I have to 
drop into a console and back to Alt+F7 before I can see the output of whatever 
I had clicked on.  Interestingly, Plasma-Wayland worked fine, both monitors 
came up with the correct resolution.

[2] Last week's update broke both xorg and wayland.  Plasma crashes when 
launched and partially recovers.  I glanced at the errors and it seems to be 
related to some Qt library.  Again, I haven't troubleshooted it further.

Not sure if this helps, but would be interested to try in whatever fix you may 
come up with.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]