Hi everyone,

Specs of my machine below.

I'm just guessing that this is an X11 issue, because when I use Wayland I don't have the same problem.

So my system is slow to open windows when I use X11. The windows eventually open, but they simply display what's already on the screen. Then they take a while to actually display what they're meant to display. Example: Nothing is open, then I click to open Office Writer. The window eventually comes up after several seconds, but within the window the desktop is displayed - i.e. the portion of the desktop that the window takes up. If I minimise then re-open, it continues to show the desktop and then eventually displays Office Writer.

Wayland is much snappier and there aren't these issues at all. However, in the past when I've used Wayland it always "seemed" good until it crashed the system. X11 seems more stable, if slower. But not normally this slow.

What troubleshooting can I do on X11 specifically?

Thanks

Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 5.15.0-56-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP Notebook
System Version: Type1ProductConfigId

I can't suggest any fixes, but you might start by looking to see if any messages are being logged.

You could check the journal

Code: Select all

journalctl --boot

, you may need to run this as root via

Code: Select all

sudo journalctl --boot

.

You could check the output of

Code: Select all

dmesg

(again might need to use sudo).

And depending on how neon does things, X11 may be logging to a text file which would likely be in

Code: Select all

/home/michael/.local/share/sddm/xorg-session.log

, or you could go looking for it

Code: Select all

find $HOME -name xorg-session.log

. Some distributions are redirecting what was going to xorg-session.log to the journald, but not all.

Finally, sddm or X11 might log some stuff to log in files in [/code]/var/log/messages/[/code].

Laptop graphics drivers are sometimes a source of issues, so it might be good to try some google searches on you specific hardware and Linux. I can't really comment much on laptops because all my machines are desktops.

On a brief glance this morning, I think I see a fair few request for help going unanswered in this forum. Distro specific forums, or Linux specific forums (linux.questions.org, linux.org), may yield more responses.

Thanks for your help. Sorry for the late reply.

mchnz wrote:I can't suggest any fixes, but you might start by looking to see if any messages are being logged.

You could check the journal

Code: Select all

journalctl --boot

, you may need to run this as root via

Code: Select all

sudo journalctl --boot

.

You could check the output of

Code: Select all

dmesg

(again might need to use sudo).

And depending on how neon does things, X11 may be logging to a text file which would likely be in

Code: Select all

/home/michael/.local/share/sddm/xorg-session.log

, or you could go looking for it

Code: Select all

find $HOME -name xorg-session.log

. Some distributions are redirecting what was going to xorg-session.log to the journald, but not all.

Finally, sddm or X11 might log some stuff to log in files in [/code]/var/log/messages/[/code].

Laptop graphics drivers are sometimes a source of issues, so it might be good to try some google searches on you specific hardware and Linux. I can't really comment much on laptops because all my machines are desktops.

On a brief glance this morning, I think I see a fair few request for help going unanswered in this forum. Distro specific forums, or Linux specific forums (linux.questions.org, linux.org), may yield more responses.