Xorg upgrade broke Shutter on Intel graphics

PhotonX · 2022-12-28 09:30:04

Hi guys,

I have the following problem: After one of the recent Xorg updates (more details later) Shutter does not update the screen state after taking the first screenshot, so the second screenshot will show an outdated screen state. The problem appears with Intel graphics only (a wide range of generations: HD graphics from Haswell CPUs, UHD graphics, Xe graphics). It appears, when xf86-video-intel is installed and when it is not.

It has been first spotted on Manjaro and we can pinpoint the exact update which triggered it. But as I know that it's a shame asking for support for another distro, I also reproduced it on my Arch machine. It is easier for me to pinpoint the update for Manjaro, because there we have a date when the update happened and also a list of packages which have been updated. I have a list of packages which are related to Xorg in some way and have been updated on this particular date:

[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)

As far as I understand, all these packages are pulled by Manjaro directly from Arch repos.

The bug has been reported against Shutter: https://github.com/shutter-project/shutter/issues/523 But since it first appeared after a Xorg update, I'd like to find out more on the Xorg side.

I was thinking about downgrading the Xorg packages from above list, but I am afraid of breaking everything. Is it safe to downgrade them one by one or should some subset of packages be only downgraded simultaneously?

If there are better ways to diagnose the problem than downgrading Xorg packages, I'm open to suggestions as well!

Wish you a happy new year in advance!
PotonX

seth · 2022-12-28 09:46:58

Probably wrong sub, but also: desktop/wm/compositor?
I'd guess the problem is the mesa update. libx11 and libxcb are just rebuilds.

Also see https://bbs.archlinux.org/viewtopic.php?id=282295

PhotonX · 2022-12-28 09:52:01

Oh yeah, that other issue looks exactly like it!

The DE is Xfce in my case as well (cannot rule out that other DEs are affected though). I tried with Compiz and XFWM (with and without integrated compositing).

Is it safe to only downgrade mesa and leave everything else as is?

seth · 2022-12-28 10:10:06

It's "safe" in that you'll still be able to boot the multi-user.target or a live distro and revert the downgrade

libx11 isn't a mere rebuild, though.
https://bugs.archlinux.org/task/76860
The patch messes w/ X11 event handling, so that could be the cause as well

PhotonX · 2022-12-28 10:24:36

Ok, so it's unsafe. Can I downgrade further packages so X11 works again? I'd like to pinpoint it to some specific package and version to be able to further research it or report it at Xorg.

libx11 isn't a mere rebuild, though.
https://bugs.archlinux.org/task/76860
The patch messes w/ X11 event handling, so that could be the cause as well sad

I have 1.8.3-3 installed on my Arch machine which displays the bug. So whatever has been fixed in this version is something else...

seth · 2022-12-28 10:42:38

The point was that the libx11 or libxcb updates could actually be the culprits because of the patches trying to fix the FF bug.

PhotonX · 2022-12-28 11:00:07

Ah, I see, sorry for the confusion!

So how could I go about finding out what happened?

seth · 2022-12-28 13:14:32

Try to downgrade mesa and libx11/xcb individually and measure the impact.

Partial up/downgrades are generally not supported but your system won't explode and iff you afterwards fail to boot the graphical.target (what is not guaranteed either way) you can easily undo the downgrade.

PhotonX · 2022-12-28 13:17:30

Thinking a bit further: libx11 only got a revision bump from 1.8.2-1 to 1.8.2-2 in the update in question, where the debug option has been set in the PKGBUILD: https://github.com/archlinux/svntogit-p … 601accf602 I actually tried to rebuild 1.8.3-3 without the debug option and it didn't solve the issue, so, not surprisingly, this was not the problem.

I don't think that mesa is involved as it only deals with OpenGL and the problem occurs even with deactivated compositing.

But then what could it be?

edit: Sorry, I posted without having noticed your last answer.

Now the problem I am having is that the older versions in question aren't available in my package cache any more. Any hints, how I can get them?

edit 2: Never mind, downgrade doesn't work properly on Manjaro, so I am just doing it on my Arch machine now.

Last edited by PhotonX (2022-12-28 13:36:16)

seth · 2022-12-28 13:31:58

Ah, my bad - was 1.8.2, not 1.8.3 (so this is going on over a month?)

and the problem occurs even with deactivated compositing

Certainly the modesetting driver uses it, regardless of any compositing.

https://wiki.archlinux.org/title/Arch_Linux_Archive

PhotonX · 2022-12-28 13:38:17

I downgraded mesa, libx11, libxcb, libxi and libxrandr and still can reproduce the issue... Trying to downgrade further packages now.

seth · 2022-12-28 13:44:58

To be sure: you did restart the X11 server after downgrading?

PhotonX · 2022-12-28 13:45:37

Of course, I even rebooted!

edit: Bummer, now I downgraded all packages from the list in the initial post besides of vulkan related stuff and lib32 packages and the issue persists...

I need to add that I am doing the troubleshooting on my Arch machine which usually runs an nVidia card. I switched to integrated graphics and can reproduce the issue, but I never used Shutter with integrated graphics on this machine, so I cannot be sure that it has ever worked. On my Manjaro laptop it for sure worked until the update in question, but there I cannot do the troubleshooting because downgrade doesn't have access to older package versions from Arch mirrors, only to the local package cache, so it basically useless...

Last edited by PhotonX (2022-12-28 13:52:39)

seth · 2022-12-28 14:02:20

Bummer, now I downgraded all packages from the list in the initial post

Yeah, suspected as much when libx11 and mesa went dry.

Is this limited to the panel widget thingy for you as well?
Did you try the behavior w/ the delayed console invocation?

PhotonX · 2022-12-28 14:05:23

I'm not sure whether I get you right, but I have a Shutter instance sitting in the panel. Then I run "shutter -f" from the terminal to get a full screen screenshot. It connects to the already running instance and shows the main window with the screenshot, which shows an outdated screen state. If I restart Shutter completely, everything is fine, so I can take one screenshot every run.

seth · 2022-12-28 14:26:26

https://bbs.archlinux.org/viewtopic.php?id=282295 uses some "screenshooter" - is your problem maybe limitd to suhtter?
What about scrot or simply "xwd -root -out /tmp/screenshot.xwd"?
(imagemagick "display" can show xwd's)

PhotonX · 2022-12-28 14:36:41

Now I also downgraded the kernel and removed xf86-video-intel from my Arch machine, still no change.

I'm not sure how to take more than one screenshot with xfce4-screenshooter or any other app. Since the problem appears only on the second run, this is essential...

edit: The panel plugin for xfce4-screenshooter does not display the problem, also not on my laptop with up to date libs. But I think, what the plugin does is just adding a starter for xfce4-screenshooter to the panel, so I am really surprised that it could have this issue at all on the machine in this other thread, as it doesn't have a running session like Shutter does. There is no process xfce4-screenshooter running once the xfce4-screenshooter window is closed, even if there is plugin sitting in the panel.

edit 2: I just installed spectacle and cannot reproduce the issue both on my laptop and on my desktop. So it might be a Shutter specific issue eventually. But on the other hand Shutter used to work just a few weeks ago!

Last edited by PhotonX (2022-12-28 14:57:36)

seth · 2022-12-28 14:58:06

You may face a differnet or multiple problems.
Did you consider downgrading shutter?

Edit #2: yeah, that bug is even in the OP…

Last edited by seth (2022-12-28 15:01:21)

PhotonX · 2022-12-28 15:02:20

Shutter hasn't been updated for many months, so I don't suspect Shutter alone to be the root of the problem. Since I am somewhat involved in Shutter upstream, I am pretty sure that nothing involving the process of actually capturing the screen contents hasn't been touched for a very long time.

seth · 2022-12-28 15:14:48

Shutter depends on https://archlinux.org/packages/extra/x8 … op-portal/ and xdg-desktop-portal-gtk is in your update list and portal is anyones favorite nemesis anyway.
Other than that, IM and wnck are dependencies that have recently been updated and are somewhat screenshot-adjacent.

PhotonX · 2022-12-28 15:24:24

xdg-desktop-portal-gtk is only being used on Wayland, as far as I understand. But I have downgraded that as well, just to be sure, without any effect. libwnck3 had a revision bump only, but I'll try downgrading it as well. And what is IM?

edit: Ah, imagemagick, I guess. This hasn't been updated in the upgrade in question, also it is only an optional dependency for applying effects, not involved in actually capturing the screen.

edit2: libwnck3 downgrade had no effect.

Last edited by PhotonX (2022-12-28 15:27:24)

seth · 2022-12-28 15:30:50

This hasn't been updated in the upgrade in question

I guess we've established that that list is useless and does not cover the compromising change?

I downgraded all packages from the list in the initial post besides of vulkan related stuff and lib32 packages and the issue persists...

Speaking of "compromising change": try a fresh user account - maybe it's some config that got set at some point somehow.

PhotonX · 2022-12-28 15:32:42

Fair point, the list is just an excerpt from the complete list of packages being upgraded which I pasted here: https://github.com/shutter-project/shut … 1365350638

I'll try that, give me another moment!

edit: The issue persists with a fresh user.

Last edited by PhotonX (2022-12-28 15:36:00)

seth · 2022-12-28 16:28:08

[2022-12-07T20:57:33+0100] [ALPM] upgraded linux60 (6.0.8-1 -> 6.0.11-1)
[2022-12-07T20:57:13+0100] [ALPM] upgraded linux515 (5.15.78-1 -> 5.15.81-1)

Now I also downgraded the kernel and removed xf86-video-intel from my Arch machine, still no change.

From which to what version and does it happen regardless of the kernel on manjaro?

PhotonX · 2022-12-28 16:44:12

From 6.1.1 to 6.0.8 on Arch. I will test on another kernel on Manjaro and report back!

edit: Same story with a 5.15 LTS kernel on Manjaro...

Last edited by PhotonX (2022-12-28 16:47:35)

Arch Linux

#1 2022-12-28 09:30:04

Xorg upgrade broke Shutter on Intel graphics

#2 2022-12-28 09:46:58

Re: Xorg upgrade broke Shutter on Intel graphics

#3 2022-12-28 09:52:01

Re: Xorg upgrade broke Shutter on Intel graphics

#4 2022-12-28 10:10:06

Re: Xorg upgrade broke Shutter on Intel graphics

#5 2022-12-28 10:24:36

Re: Xorg upgrade broke Shutter on Intel graphics

#6 2022-12-28 10:42:38

Re: Xorg upgrade broke Shutter on Intel graphics

#7 2022-12-28 11:00:07

Re: Xorg upgrade broke Shutter on Intel graphics

#8 2022-12-28 13:14:32

Re: Xorg upgrade broke Shutter on Intel graphics

#9 2022-12-28 13:17:30

Re: Xorg upgrade broke Shutter on Intel graphics

#10 2022-12-28 13:31:58

Re: Xorg upgrade broke Shutter on Intel graphics

#11 2022-12-28 13:38:17

Re: Xorg upgrade broke Shutter on Intel graphics

#12 2022-12-28 13:44:58

Re: Xorg upgrade broke Shutter on Intel graphics

#13 2022-12-28 13:45:37

Re: Xorg upgrade broke Shutter on Intel graphics

#14 2022-12-28 14:02:20

Re: Xorg upgrade broke Shutter on Intel graphics

#15 2022-12-28 14:05:23

Re: Xorg upgrade broke Shutter on Intel graphics

#16 2022-12-28 14:26:26

Re: Xorg upgrade broke Shutter on Intel graphics

#17 2022-12-28 14:36:41

Re: Xorg upgrade broke Shutter on Intel graphics

#18 2022-12-28 14:58:06

Re: Xorg upgrade broke Shutter on Intel graphics

#19 2022-12-28 15:02:20

Re: Xorg upgrade broke Shutter on Intel graphics

#20 2022-12-28 15:14:48

Re: Xorg upgrade broke Shutter on Intel graphics

#21 2022-12-28 15:24:24

Re: Xorg upgrade broke Shutter on Intel graphics

#22 2022-12-28 15:30:50

Re: Xorg upgrade broke Shutter on Intel graphics

#23 2022-12-28 15:32:42

Re: Xorg upgrade broke Shutter on Intel graphics

#24 2022-12-28 16:28:08

Re: Xorg upgrade broke Shutter on Intel graphics

#25 2022-12-28 16:44:12

Re: Xorg upgrade broke Shutter on Intel graphics

Board footer