The officially official Devuan Forum!

_mAL_4_th3_fl00r

Member

Registered: 2025-09-27

Posts: 10  

Compositor became a victim

On Refracta 13, when I do a "Select a region" with xfce4-screenshooter the entire screen goes black but I'm still able to capture the known region(shows the px during grab). One of the modifications from the last week or so till now has to be the cause.

I've found that xfconf-query -c xfwm4 -p /general/use_compositing -s false disables transparency on the terminal, but it does enable me to see the screen during the region capture. I'd like to keep transparency tho .

Last known big changes were

xserver-xorg-core  21.1.16-1.3+deb13u1devuan1 → +deb13u4devuan1
xserver-common     same jump
linux-image-amd64  6.12.86-1 → 6.12.107-1
Mesa 25.0.7-2 → 25.0.7-2+deb13u1 

and installing PCSX2(first play-thru of FFX).

Last edited by _mAL_4_th3_fl00r (2026-10-01 04:36:34)

fsmithred

Administrator

Registered: 2016-11-25

Posts: 3,019  

Re: Compositor became a victim

I can't reproduce this exactly, but it's close. When I choose to select a region in the screenshooter, the entire screen gets dark, but not black. I can still see everything. If I repeat that with compositor turned off, the screen does not go dark. That's on up-to-date excalibur with same software versions you posted.

I don't have any good suggestions for what to do with that information. Maybe increase the brightness of your screen?

FWIW I'm using nouveau driver with an old geforce 210.

_mAL_4_th3_fl00r

Member

Registered: 2025-09-27

Posts: 10  

Re: Compositor became a victim

Update.

FWIW I'm on an (Asus) NVIDIA GeForce RTX 4060 Ti, NVIDIA-SMI 615.71.10, CUDA UMD Version: 13.4 

I've defaulted to using flameshot for my area-grab needs.

tux_99

Member

Registered: 2025-06-17

Posts: 215  

Re: Compositor became a victim

I can't reproduce it either (at least not on up-to-date excalibur). The screen only gets slightly darker to highlight the selected region but after the selection has been done it goes back to normal (I assume this is intended behaviour, it seems rational to me).
I do have compositing enabled, with transparencies and shadows.

I also use the Nvidia proprietary drivers (with a GTX 1050 card), but the stable 580.x branch, not 615.x.

Maybe what you are seeing is caused by some bug in the 615.x. Nvidia driver?

Last edited by tux_99 (Yesterday 22:26:29)

---

“Either the users control the program – or the program controls the users” Richard Stallman