You are not logged in.
EDIT: I was using Wayland, not Xorg, the whole time - I've switched to Xorg, which fixed the issue.
When resizing Chromium, or moving the window around, I see rendering errors similar to below (but inconsistent; sometimes there are just large black patches):
https://i.imgur.com/Ge6SfBc.png
It always happens while dragging the corner of the window or moving the window, and often persists after the window is released.
This only occurs when using the Intel graphics (I have HD Graphics 530 on this laptop, and xf86-video-intel installed); if I use "optirun chromium" to use the Nvidia graphics instead, it works fine.
I'm using GNOME; I also have a config file at /etc/X11/xorg.conf.d/20-intel.conf :
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
EndSectionI set the AccelMethod to uxa as recommended in the "Intel graphics" wiki page.
Anyone else experiencing the same thing?
Mod edit: Replaced image with url link -- V1del
EDIT: I have uninstalled xf86-video-intel and removed the conf file (so I am now using the modesetting driver), but the problem persists.
Last edited by Archimaredes (2018-05-31 15:30:24)
Offline
Modern intel graphics do often have issues with older assumptions of xf86-video-intel, that driver is in a perpetual limbo not really updated but also not completely abandoned yet. On a modern intel like yours it is often recommended to remove xf86-video-intel (and that configuration file) and instead relying on the built in modesetting driver for xorg. Note the blue box the hint regarding a potential issue often only really applies if you are running without a compositor, which you are not as you are on gnome
Last edited by V1del (2018-05-31 14:19:44)
Offline
Modern intel graphics do often have issues with older assumptions of xf86-video-intel, that driver is in a perpetual limbo not really updated but also not completely abandoned yet. On a modern intel like yours it is often recommended to remove xf86-video-intel (and that configuration file) and instead relying on the built in modesetting driver for xorg. Note the blue box the hint regarding a potential issue often only really applies if you are running without a compositor, which you are not as you are on gnome
That was the setup I initially had - I've removed xf86-video-intel (and the conf file) again to check, and the problem remains. In fact, it seems more pronounced.
It's probably worth mentioning that I see no issues when using Firefox. Chromium appears to be the only affected application so far.
Offline
Can you post a xorg log from such a run? Also you are sure that you run GNOME on Xorg and not Wayland?
Offline
Can you post a xorg log from such a run? Also you are sure that you run GNOME on Xorg and not Wayland?
Ah, damn, I was using Wayland the whole time... under actual Xorg, it's fine.
I see no reason why I should be using Wayland (as an end user) so I suppose this is resolved, but - is there any particular reason this error would occur only on Wayland? Is it an issue with the XWayland layer?
Offline
Yes likely an issue with the GPU workarounds chromium applies that no longer hold true for the new version of XWayland, see the following thread for additional pointers in that regard: https://bbs.archlinux.org/viewtopic.php?id=237383
Last edited by V1del (2018-05-31 16:04:37)
Offline