Arch Linux

lonely_neutrino

Member

Registered: 2020-11-30

Posts: 5

[SOLVED] Flameshot (and other screenshot tools) use old screen buffers

Hi,

Ever since I started using arch on my new Lenovo Yoga Slim 7 I've been having this issue with all screenshot tools. I tried searching numerous times on various forums but perhaps my formulation of this problem isn't matching or I am the only one facing this issue, which I doubt. I'm on the latest everything and running KDE.

Best shown using pictures (sorry for the literal screen shots, can't do better in this situation):

Screen before launching flameshot

This is what I would expect to see (it sometimes works ok as it did here)

This is what it looks like if i esc out of flameshot and launch it again

This is what hapened after another iteration

Then it looped between the last two buffers. It is sometimes able to show a buffer from a couple of hours ago, I can't imagine where these are stored.

Honestly no idea what's causing this. The only thing that makes a difference is switching to XRender, but even then it still sometimes happens (+ I wouldn't want to use XRender long term)

Thanks in advance

Last edited by lonely_neutrino (2020-12-11 20:54:40)

lonely_neutrino

Member

Registered: 2020-11-30

Posts: 5

Re: [SOLVED] Flameshot (and other screenshot tools) use old screen buffers

Not asking for solutions, just want to narrow it down... Anybody see this?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,672

Re: [SOLVED] Flameshot (and other screenshot tools) use old screen buffers

Graphics card and driver used? If intel and you have xf86-video-intel installed, get rid of xf86-video-intel.

lonely_neutrino

Member

Registered: 2020-11-30

Posts: 5

Re: [SOLVED] Flameshot (and other screenshot tools) use old screen buffers

00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G1 (Ice Lake) (rev 07) (prog-if 00 [VGA controller])
        Subsystem: Lenovo Device 3a34
        Flags: bus master, fast devsel, latency 0, IRQ 164, IOMMU group 1
        Memory at 601e000000 (64-bit, non-prefetchable) [size=16M]
        Memory at 4000000000 (64-bit, prefetchable) [size=256M]
        I/O ports at 6000 [size=64]
        Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: i915
        Kernel modules: i915

and

30:00.0 3D controller: NVIDIA Corporation GP107M [GeForce MX350] (rev ff) (prog-if ff)
        !!! Unknown header type 7f
        Kernel modules: nouveau, nvidia_drm, nvidia

pacman says the xf86-video-intel is installed, but the output of lspci means it is not in use? I use bbswitch for the graphics cards, only really use the Intel card because of power consumption.

lonely_neutrino

Member

Registered: 2020-11-30

Posts: 5

Re: [SOLVED] Flameshot (and other screenshot tools) use old screen buffers

So after checking xorg config files I removed the package, now the system hangs at boot with

 snd_hda_codec_hdmi haudioC0D2: Monitor plugged in, Failed to power up codec ret=[-13] 

when I have a USB-C monitor connected, without it it just hangs. Desktop manager doesn't start up, even though all GUI related messages are OK

lonely_neutrino

Member

Registered: 2020-11-30

Posts: 5

Re: [SOLVED] Flameshot (and other screenshot tools) use old screen buffers

Eventually I found a config file which in fact speciffied "Intel". Everything seems to work perfectly, including the screenshots, actually I think KDE now runs much more smoothly, thank you so much!

WyekS

Member

Registered: 2021-07-23

Posts: 2

Re: [SOLVED] Flameshot (and other screenshot tools) use old screen buffers

Hi. I have exactly the same problem with my Intel Iris grapichs on a Lenovo ThinkPad T14 v2.

I had to create a file to disable vsync, but it's not a good solution

───────┬─────────────────────────────────────────────────────
       │ File: /home/user/.drirc
───────┼─────────────────────────────────────────────────────
   1   │ <device screen="0" driver="dri2">
   2   │     <application name="Default">
   3   │         <option name="vblank_mode" value="0"/>
   4   │     </application>
   5   │ </device>
───────┴─────────────────────────────────────────────────────

Could you pass that config file or the steps you have taken to fix this bug?

Thank you!

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,672

Re: [SOLVED] Flameshot (and other screenshot tools) use old screen buffers

As mentioned, they removed xf86-video-intel. Since this topic is solved and a lot can change in a year I suggest you make a new post.

Technically there's currently a regression in the mesa 20.2.x series and the iris GL driver that can lead to issues not unlike this. You could try rolling mesa to 21.1.6 or switching to the older i965 for the time being: https://wiki.archlinux.org/title/Intel_ … ver_(i965)

WyekS

Member

Registered: 2021-07-23

Posts: 2

Re: [SOLVED] Flameshot (and other screenshot tools) use old screen buffers

As mentioned, they removed xf86-video-intel. Since this topic is solved and a lot can change in a year I suggest you make a new post.

Technically there's currently a regression in the mesa 20.2.x series and the iris GL driver that can lead to issues not unlike this. You could try rolling mesa to 21.1.6 or switching to the older i965 for the time being: https://wiki.archlinux.org/title/Intel_ … ver_(i965)

Thank very much, V1del!

EDIT: I removed xf86-video-intel package and vsync configuration and all is correct now

Last edited by WyekS (2021-10-27 12:08:05)