I’ve noticed that when I enable the ā€œForce Composition Pipelineā€ option in NVIDIA settings on my RTX 2070 running on X11, my system freezes shortly after starting any game which uses DXVK. This seems to be related to NVIDIA driver version 535 and newer.

The problem happens because DXVK 2.3 started using the VK_KHR_present_wait extension, which doesn’t work well with the composition pipeline enabled on these drivers. The freeze happens consistently and makes the desktop unresponsive within a couple of seconds after launching any game using DXVK.

I found a discussion about this issue on NVIDIA’s developer forums where it’s confirmed and reproducible.

- https://forums.developer.nvidia.com/t/complete-gpu-crash-on-x11-with-force-full-composition-pipeline-and-vk-khr-present-wait-100-reproducible/267934

They still haven't fixed this. It's been years since 2023, yet NVIDIA's drivers still treat X11 like a beta test. Who needs open source love when you can just... not fix reproducible crashes?

(Their Vulkan support? More like Vul-can't, am I right?)

#GamingOnLinux #LinuxGaming #Linux #Debian #FreeSoftware #FOSS #FLOSS #Nvidia #GPU #RTX2070 #Vulkan #X11 #DXVK

Complete GPU crash on X11 with "Force Full Composition Pipeline" and VK_KHR_present_wait! 100% reproducible!

This crash has been confirmed by Valve engineers. Steps to reproduce: NVIDIA driver 535+. I’ve tested this with RTX 2070 Super. But I assume every card is affected. Must be on X11. Enable ā€œForce Full Composition Pipelineā€ in NVIDIA Settings. Use DXVK 2.3 release, which has whitelisted the usage of VK_KHR_present_wait on NVIDIA drivers. Play any game that uses DXVK. The desktop will freeze 1-2 seconds after the game opens up and there is no way to unfreeze it. There are two discussions about ...

NVIDIA Developer Forums
I didn't expect this to be so hard: in #Ubuntu #X11 you force a simple screenblank with 'xset dpms force off' but in #Wayland, while Meta-L or xdg-screensaver can LOCK the screen, and awaiting a timeout will just BLANK the screen (like I want) there doesn't appear to be any commandline way to invoke the latter? I don't need screenlock security, I just want to turn these screens off at night so I can sleep.

Yesterday, #Gajim 2.1.1 migrated to #Debian 13 #trixie, a.k.a. #testing. Works very well for me!

However, there is an issue with #EXWM and #GTK4: Marking text and copy/paste via keyboard is broken in the text input field of Gajim. I guess, there is sth. missing in the #portals definition. It only says:

[preferred]
default=gtk

Maybe that's not enough?

#Jabber #XMPP #X11 #Emacs

I know it has its drawbacks, but the fact that you can just add a program like picom to #Xorg / #X11 and get fancy effects is just amazing. In #Wayland you need to hope for your window manager to support effects and use their specific implementation
Still running #OpenBSD on the old Dell Optiplex 3080 tower and finding little quirks / differences from what I'm used to using #FreeBSD on my #ThinkPad. But overall I have not yet been put off and persist when something doesn't work like I thought it should. Just learnt that I needed to install colorls and alias it to ls so I could get color output in the terminal when typing ls. But I then found that in the normal tty before I started X11 that I even though that alias was present it did not give me color output. After digging through the www I found a suggestion to put the following line in my .profile :

export TERM=wsvt25
Rebooted to be sure and voila I get a color listing in both the tty and a #kitty terminal under #X11 .
I'm sure that I'll learn heaps more as I plod along but it is good. #RunBSD

It's 2025. It should not be the case that I'm the first author of a terminal emulator to wonder what control sequences the "multimedia"/"office" keys on my Windows keyboard should send.

But I have just looked around at TeraTerm, XTerm, and several others; and there's nothing. Apparently it doesn't help the GUI emulator writers that "multimedia"/"office" keys are not really a thing when it comes to #X11.

It seems that I have to pioneer something.

#nosh #uservt #TerminalEmulators

The author of picom now writes a #Rust #Wayland lib. Apparently it has quite the different philosophy in comparison to smithay, so that’s interesting

Picom is what you use when you want animations in your window manager on #xorg #x11

https://github.com/yshui/runa

GitHub - yshui/runa: wayland compositor toolbox

wayland compositor toolbox. Contribute to yshui/runa development by creating an account on GitHub.

GitHub
Ok I'm interested to see how many #BSD users still use as their daily an #Xorg ( #X11 ) WM or DE and intend to continue doing so for the foreseeable. It doesn't matter which BSD you use just if you do use X or #Wayland ?

Please boost for a larger each and thank you. xoxo
#FreeBSD #OpenBSD #NetBSD #RunBSD
Yeah I use Xorg ( X11 ) and intend to continue for the fores...
55%
Nah I switched to Wayland and I'm staying put.
16.7%
I just like pressing buttons.
28.2%
Poll ended at .
Gestern hab ich mal einen "Ausflug" zu FreeBSD gemacht. Und Hey, das war bis auf die Gui, die in der VM nicht so wollte wie ich, ein gutes Erlebniss. #proxmox #unix #linux #bsd #x11
I am back on #X11 and #NvidiaDrivers on #Kubuntu #2404
I dunno, an update fixed my xcb issue. Wayland was nice, but was working best with just #nouveau #drivers. It was working but some #software would not launch.
Looking forward to Kubuntu 26.06 #LTS because I am sure that will be a great #Wayland experience.