Need some help with an intractable Xorg issue

Hi guys,

I already posted about an issue I had with taking screenshots. Short version: Shutter and also other screenshot tools capture an outdated screen state, long version see Screenshot tools capture garbage with Iris Xe graphics.

Luckily, the problem magically disappeared at some point so I could use Shutter without any problems. However, one of the recent updates reintroduced the problem, so I am stuck with it again.

The problem has been reported at Shutter’s bug tracker: Second 'New Selection' gives the previous window state. · Issue #523 · shutter-project/shutter · GitHub As you can see, at least four users (including myself) are affected, at least three of them are Manjaro users.

Luckily, we could trace down the update which introduced the issue, it’s the update from 6th of December: [Stable Update] 2022-12-06 - Kernels, Mesa, Plasma, Cinnamon, Nvidia, LibreOffice, Pipewire, Virtualbox

Obviously, the update to the Xorg stack caused the issue. Also, at least two of the four affected users are using Intel graphics (I am using Iris Xe graphics, one of the other users is using Intel UHD graphics).

I intend to downgrade Xorg related packages till I can pinpoint the exact package whose update caused the problem. Are there any things I should take care of? Like, “don’t downgrade package A without downgrading package B as well, otherwise you will end up in a TTY” and this kind of stuff. :wink:

I really need to fix it during the Christmas break because I take screenshots in my job on a daily basis and restarting Shutter for each screenshot is quite an issue for me…

Thanks for any input!


So I have compiled a list of packages which are (possibly) Xorg related and have been update:

[2022-12-07T20:56:48+0100] [ALPM] upgraded xcb-proto (1.15.2-1 -> 1.15.2-2)
[2022-12-07T20:56:48+0100] [ALPM] upgraded libxdmcp (1.1.3-4 -> 1.1.4-1)
[2022-12-07T20:56:48+0100] [ALPM] upgraded libxau (1.0.10-1 -> 1.0.10-2)
[2022-12-07T20:56:48+0100] [ALPM] upgraded libxcb (1.15-1 -> 1.15-2)
[2022-12-07T20:56:49+0100] [ALPM] upgraded libx11 (1.8.2-1 -> 1.8.2-2)
[2022-12-07T20:56:49+0100] [ALPM] upgraded libxft (2.3.6-1 -> 2.3.7-1)
[2022-12-07T20:56:50+0100] [ALPM] upgraded libxi (1.8-1 -> 1.8-2)
[2022-12-07T20:56:50+0100] [ALPM] upgraded libxfixes (6.0.0-1 -> 6.0.0-2)
[2022-12-07T20:56:50+0100] [ALPM] upgraded libxdamage (1.1.5-4 -> 1.1.5-5)
[2022-12-07T20:56:51+0100] [ALPM] upgraded vulkan-icd-loader (1.3.226-1 -> 1.3.235-1)
[2022-12-07T20:56:51+0100] [ALPM] upgraded lib32-vulkan-icd-loader (1.3.226-1 -> 1.3.235-1)
[2022-12-07T20:56:51+0100] [ALPM] upgraded mesa (22.2.3-1.1 -> 22.2.4-1)
[2022-12-07T20:56:51+0100] [ALPM] upgraded libinput (1.21.0-1 -> 1.22.0-1)
[2022-12-07T20:56:51+0100] [ALPM] upgraded libxkbcommon (1.4.1-1 -> 1.4.1-2)
[2022-12-07T20:56:51+0100] [ALPM] upgraded libxkbcommon-x11 (1.4.1-1 -> 1.4.1-2)
[2022-12-07T20:56:52+0100] [ALPM] upgraded libxcursor (1.2.1-1 -> 1.2.1-3)
[2022-12-07T20:56:52+0100] [ALPM] upgraded libxrandr (1.5.2-4 -> 1.5.3-1)
[2022-12-07T20:56:58+0100] [ALPM] upgraded xdg-desktop-portal-gtk (1.14.0-1 -> 1.14.1-1)
[2022-12-07T20:57:04+0100] [ALPM] upgraded lib32-libxdmcp (1.1.3-1 -> 1.1.3-2)
[2022-12-07T20:57:04+0100] [ALPM] upgraded lib32-libxau (1.0.10-1 -> 1.0.10-3)
[2022-12-07T20:57:04+0100] [ALPM] upgraded lib32-libxcb (1.15-1 -> 1.15-2)
[2022-12-07T20:57:04+0100] [ALPM] upgraded lib32-libx11 (1.8.2-1 -> 1.8.2-2)
[2022-12-07T20:57:04+0100] [ALPM] upgraded lib32-libxfixes (6.0.0-1 -> 6.0.0-2)
[2022-12-07T20:57:04+0100] [ALPM] upgraded lib32-libxcursor (1.2.1-1 -> 1.2.1-2)
[2022-12-07T20:57:04+0100] [ALPM] upgraded lib32-libxdamage (1.1.5-2 -> 1.1.5-3)
[2022-12-07T20:57:05+0100] [ALPM] upgraded lib32-mesa (22.2.3-1 -> 22.2.4-1)
[2022-12-07T20:57:05+0100] [ALPM] upgraded lib32-libxi (1.8-1 -> 1.8-2)
[2022-12-07T20:57:05+0100] [ALPM] upgraded lib32-libxrandr (1.5.2-2 -> 1.5.2-3)
[2022-12-07T20:57:05+0100] [ALPM] upgraded lib32-libva-mesa-driver (22.2.3-1 -> 22.2.4-1)
[2022-12-07T20:57:05+0100] [ALPM] upgraded lib32-mesa-vdpau (22.2.3-1 -> 22.2.4-1)
[2022-12-07T20:57:05+0100] [ALPM] upgraded lib32-vulkan-intel (22.2.3-1 -> 22.2.4-1)
[2022-12-07T20:57:06+0100] [ALPM] upgraded lib32-vulkan-radeon (22.2.3-1 -> 22.2.4-1)
[2022-12-07T20:57:10+0100] [ALPM] upgraded libva-mesa-driver (22.2.3-1 -> 22.2.4-1)
[2022-12-07T20:57:10+0100] [ALPM] upgraded libxp (1.0.4-1 -> 1.0.4-2)
[2022-12-07T20:57:37+0100] [ALPM] upgraded mesa-vdpau (22.2.3-1 -> 22.2.4-1)
[2022-12-07T20:57:47+0100] [ALPM] upgraded vulkan-headers (1:1.3.227-1 -> 1:1.3.235-1)
[2022-12-07T20:57:53+0100] [ALPM] upgraded xapp (2.2.15-1 -> 2.4.2-1)
[2022-12-07T20:57:54+0100] [ALPM] upgraded vulkan-intel (22.2.3-1 -> 22.2.4-1)
[2022-12-07T20:57:54+0100] [ALPM] upgraded vulkan-radeon (22.2.3-1 -> 22.2.4-1)
[2022-12-07T20:57:57+0100] [ALPM] upgraded xautomation (1.09-4 -> 1.09-5)
[2022-12-07T20:57:57+0100] [ALPM] upgraded xorg-xkill (1.0.5-3 -> 1.0.6-1)

Any ideas on how to further reduce the list (41 packages so far, quite a lot)? Maybe strip down vulkan or lib32 packages?

This is why. :point_up:

Remove the package xf86-video-intel then reboot.

Make sure you don’t have any customized configuration for Intel GPU under /etc/X11/ nor its subdirectories, otherwise your system will not be able to boot.

1 Like

Thanks for the hint! Which driver will be used then?

Built-in driver in the kernel (modesetting), for both 2D and 3D.

xf86-video-intel is old and no longer being improved. It has fairly solid support, but it’s sorely outdated.

Ok, I gave it a shot, unfortunately, the issue is still there.

I take it you rebooted and you’re using Compositing? (If so, which compositor? I’m assuming you’re using Xfce defaults?)

What are the contents under /etc/X11/ (and its subfolders)?

Can you post your system info using inxi?

Yes and yes, Compiz to be more specific.

There is only one .conf file which only includes keyboard configuration stuff.


$ inxi -F
  Host: ThinkpadL13Yoga Kernel: 6.1.1-1-MANJARO arch: x86_64 bits: 64
    Desktop: Xfce v: 4.18.0 Distro: Manjaro Linux
  Type: Convertible System: LENOVO product: 20VLS01500
    v: ThinkPad L13 Yoga Gen 2 serial: <superuser required>
  Mobo: LENOVO model: 20VLS01500 serial: <superuser required> UEFI: LENOVO
    v: R1FET46W (1.20 ) date: 08/05/2022
  ID-1: BAT0 charge: 26.2 Wh (66.5%) condition: 39.4/46.0 Wh (85.7%)
    volts: 15.6 min: 15.4
  Info: quad core model: 11th Gen Intel Core i5-1135G7 bits: 64 type: MT MCP
    cache: L2: 5 MiB
  Speed (MHz): avg: 1636 min/max: 400/4200 cores: 1: 2400 2: 955 3: 1155
    4: 618 5: 760 6: 2400 7: 2400 8: 2400
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: Chicony ThinkPad T490 Webcam type: USB driver: uvcvideo
  Device-3: Acer Integrated 5M Camera type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 21.1.6 driver: X: loaded: modesetting
    dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 22.3.1 renderer: Mesa Intel Xe Graphics (TGL GT2)
  Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel
  Sound API: ALSA v: k6.1.1-1-MANJARO running: yes
  Sound Server-1: PulseAudio v: 16.1 running: yes
  Sound Server-2: PipeWire v: 0.3.63 running: yes
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi
  IF: wlp0s20f3 state: up mac: 2c:db:07:e7:59:78
  Device-2: Intel Ethernet I219-V driver: e1000e
  IF: enp0s31f6 state: down mac: 48:2a:e3:a8:52:ff
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb
  Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
  Local Storage: total: 476.94 GiB used: 164.61 GiB (34.5%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HBJQ-000L7
    size: 476.94 GiB
  ID-1: / size: 383.47 GiB used: 164.59 GiB (42.9%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 25.6 MiB (8.6%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p3
  System Temperatures: cpu: 1.0 C mobo: 1.0 C
  Fan Speeds (RPM): N/A
  Processes: 297 Uptime: 7m Memory: 15.3 GiB used: 5.81 GiB (37.9%)
  Shell: Bash inxi: 3.3.24

I might sound like such a pessimist that “doesn’t get it”. But hasn’t Compiz stopped being developed some years back? How “supported” is it these days? I guess if you want animations under Xfce you need it, since Xfwm4 doesn’t provide fancy animations?

Everything else looks fine, including the use of the modesetting driver for your Intel Iris Xe.

But now I wonder if you switch to a more recently updated/maintained compositor, such as Xfwm4, if you still have this issue?

That’s a good question. :slight_smile: It has no active development in the sense of new features but it’s not completely dead either: compiz - [no description]

Just tested, yes, they are still there with Xfwm4’s integrated compositor and even without a compositor at all.

The good thing is, it used to work and it is certain which update broke it, so I’m trying to approach this issue from this end.

Have you tried adding MODULES=(… i915 …) to mkinitcpio.conf and rebuild init?

Likely in conjunction with removing xf86-video-intel

Are all these systems also using Xfce, per chance?

Now I have (added the module to the MODULES array, reinstalled linux61 which triggered a rebuild for all kernels, rebooted), no change unfortunately.

At least one of them seems to, at least he referred to xfce4-screenshooter. No information from the other two guys.

Maybe it was, indeed, one of the Xorg-related packages from December 6th’s update. :confused:

Here’s what I’m gathering:

:warning: Issue exists with Shutter

:warning: Issue exists with Xfce4-screenshooter

:question: Seems to only affect Xfce users (unless others can chime in with KDE, Cinnamon, etc)

:warning: Issue exists with Xfwm4 and Compiz

:warning: Issue exists with modesetting and xf86-video-intel

That’s what the other guys wrote and I can also confirm.

Yes, looks good!

I’d like to try the downgrade thingy to find the particular package responsible for the breakage, but I don’t know whether it is possible to selectively downgrade Xorg related packages while leaving others. I could downgrade them all to at least make sure that it is this upgrade which caused the issue. I’m just a bit overwhelmed by the number of packages in question and would like to reduce it to some necessary minimum (if selective downgrades will break things) or go through the packages one by one (if this is possible without breaking things).

Intel Iris Xe, modesetting (xf86-video-intel removed when I first installed Manjaro), kernel 6.1, using KDE 5.24.7.

Cannot reproduce the issue with screenshots and screengrabbing.

So the issue is, with Shutter: If you take a screenshot in selection mode, the first one works fine! But then you change the screen state, say put a different window to the front, and again try to take a screenshot in selection mode, it will show you the screen state during your previous run. Did you test it this way?

I’m wayyyyyyyyyyy more “fancy” than you. Pe’shaw! :roll_eyes: :wine_glass:

I only use the finest software in KDE with Spectacle. Do not try to soil my clothing with your downtrodden tools that only plebes use. Xfce? Shutter? Dear me! :unamused:

One second, I do have a netbook with Xfce, but it’s been some months since I last updated it. I can update it to the latest Stable Update and try with that. It has an integrated Intel UHD.

Give me a moment and I’ll try it out!


Thanks, I’m excited what comes out! :smile:

Those are two different screenshot utilities. If this other user is certainly using “Xfce-screenshooter”, and still faces the issue, then it’s not really an issue exclusive to Shutter.

(Still updating here…)

Just noticed you’re using a penguin as your avatar. Real original, @Photon. :roll_eyes: