#x11 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #x11, aggregated by home.social.
-
Препарируем графическую подсистему Windows. Протокол SPICE в современном графическом стеке, часть 2
Мы продолжаем увлекательное путешествие по миру удалённого доступа . В предыдущей части заглядывали под капот протокола доставки рабочего стола SPICE , а сейчас на операционный стол попала великая и ужасная ОС Windows - точнее, её графическая подсистема. Заглянем в её недры и окунёмся в её философию и историю развития. И заодно найдём интересные параллели в Linux . Это вторая часть цикла про протокол SPICE и то, как он вынужден работать в современных условиях. Наша конечная цель - создать пилот стримингового агента для виртуальной машины на ОС Windows . Приглашаю под кат всех, кто работает или сталкивается с системами виртуализации, с протоколом SPICE, с виртуальными машинами в принципе; кто интересуется такими темами как удалённый доступ и компьютерная графика; да и вообще всех любознательных! В бездну виндового угнетения
-
Even in the era where all major desktop environments are going Wayland-only, web browsers will ensure we never get rid of X11's traumatic memory, huh? 🫠 https://bugzilla.mozilla.org/show_bug.cgi?id=2027556
Par for the course for the ecosystem where everybody pretends to be everybody because the web is a never-ending collection of hacks…
-
Uuurgh... why does everything run like crap on #wayland? Or rather #kde on #wayland.
I never had any major performance problems on #xfce and #x11. Here kwin_wayland keeps using at least 20% or often 40% CPU. Chromium even hogs all the CPU time it can get when open.
Firefox only runs well through XWayland.
Who said wayland is stable? #archlinux #ThinkPadX260
(Also.. suggestions are appreciated. I already tried looking up my sympoms online) -
So, testing plugins on occasion, I found out that my #Linux #UbuntuStudio 24.04 does not run #WindowsVST any more.
It just doesn't work no more. I mean, the VSTs do run, but the GUIs are all not useable.
This might be due to a switch to #Nvidia graphics, which I had hoped to solve a problem with #Lightworks, which it didn't.
So basically, I can't do audio production any more, because I need #Voxengo #Elephant and #Fabfilter.
There is no mouse pointer in Windows #VST gui windows. Some windows are just plain black. Of plugins I have been using literally for over a decade.
Other #Wine applications do run with GUI. I'm using #LinVST, which used to work well for years. (And still on #X11, no #Wayland)
I'm screwed. Either I will be able to solve this somehow, or I can't accept production jobs.
This wouldn't have happened on macOS, I must say… as a person doing recording on Linux for 20 years now, including a couple of full-blown album releases.
#LinuxAudio #LinuxProAudio #Recording
EDIT: Solution see 🧵
-
CW: re: Hot take
I am all for making it a permission though.
"Allow this app to use #x11"?
-
The Sonic Desktop Environment
We aim to preserve and improve the X11-specific aspects of KDE since they announced they are going Wayland-only in KDE Plasma 6.8. SonicDE currently consists of the customized KWin/X11 sonic-win window manager and compositor, Plasma Workspace components, the Silver theme, an SDDM theme, and some support libraries.
-
-
Being able to finally fully remove the remaining Xorg packages from my computers after upgrading to Fedora 44's Wayland-only GNOME is such a satisfying moment, after decades of carrying this cruft around!
The command I used:
dnf remove xorg-x11-server-XorgI guess the drivers really are in the kernel / Mesa nowadays, because my computers are still working fine after a reboot.
-
Neste vídeo, eu mostro #batman Arkham Asylum rodando em #FullHD, com qualidade no Alto, na #RX550 de 4 GB, comparando o desempenho entre #Debian13 e #LinuxMint 22.3, lado a lado.
O teste foi feito usando o mesmo hardware e as mesmas configurações dentro do jogo.
No #Debian, o jogo roda em #Wayland, enquanto no Linux Mint o teste foi feito em #X11.
-
Ubuntu 26.04 LTS “Resolute Raccoon” is released with GNOME 50, Linux 7.0 kernel, full Wayland shift, and updated core apps replacing legacy tools. 🦝
The five-year supported release advances platform changes but drops X11 sessions, reinforcing modern stacks while raising compatibility and user choice considerations. 🔐🔗 https://fossforce.com/2026/04/ubuntu-26-04-released-the-raccoon-is-out-of-the-bag-with-screenshots/
#TechNews #Ubuntu #Linux #Canonical #OpenSource #FOSS #GNOME #Wayland #LTS #Privacy #Security #Software #Desktop #Release #Computing #X11
-
Debian from x11 to Xlibre conversion. I just ran a conversion of my Debian-Test dwm install from x11 to Xlibre. I published the following on the Debian (Test) Forum.
#x11 #Xlibre #Debian #Ubuntu #Linux #News #Technology #dwm #suckless #eirenicon
-
Still getting used to Cinnamon as a desktop but already liking it well enough over gnome.
Main selling point - KiCad works properly again.
Completely fed up with all the weirdness wayland is causing. KiCad has a really good, and perfectly reasonable, write-up about why they aren't fixing wayland issues - most aren't in their control, nor are they writing distro specific workarounds as each distro implments different wayland feature sets.
still on fedora, and was planning a clean install for 44 (years and upgraded release cruft building up - most self-inflicted) and know which spin I'm going for
-
Heute erscheint Ubuntu 26.04 LTS - und die GNOME-Xorg-Session ist endgültig weg. Kein Fallback, kein `WaylandEnable=false` Workaround, nichts.
Ich finde den Schritt richtig. Auch wenn er bei AnyDesk, NVIDIA und altem Scripting weh tut.
Eine ehrliche Einordnung: warum der Schmerz real ist, warum der Weg trotzdem stimmt - und was man jetzt tun kann.
https://rueegger.me/ubuntu-26-04-ohne-x11-warum-der-weg-richtig-ist-auch-wenn-er-weh-tut/
#Ubuntu #Linux #Wayland #X11 #GNOME #LinuxDesktop #OpenSource
-
The Sonic Desktop Environment
We aim to preserve and improve the X11-specific aspects of KDE since they announced they are going Wayland-only in KDE Plasma 6.8. SonicDE currently consists of the customized KWin/X11 sonic-win window manager and compositor, Plasma Workspace components, the Silver theme, an SDDM theme, and some support libraries.
-
Linux Mint : Pourquoi le bleu tourne au violet ?
Bonjour,
Dernièrement, on m’a fait remarquer que mes captures d’écran où vidéos avaient une tendance à ne pas afficher la bonne couleur. En soi, c’est surtout le bleu qui tournait violet.
Vu que les premières remarques ont eu lieu sur Discord, j’ai alors pensé (à tort) qu’il y avait une compression / conversion lors de l’upload générant ainsi cet effet mais le souci c’est également présenté rapidement sur Element…
J’ai pu constater le souci sous Chromium également. En effet, en ouvrant la même capture d’écran se trouvant en local sur mon pc avec Firefox et Chromium, on avait l’impression de voir deux images différentes (confirmé avec deux autres pc sous Linux Mint et LMDE) :
J’étais donc content car j’avais une piste ! En effet, Discord et Element utilisent Chromium (au travers d’Electron) pour leurs applications et donc si Chromium a un souci, il n’est pas déconnant que des applications basées dessus soient également impactées !
En recherchant sur internet, je trouve deux sujets (un chez Ubuntu et un chez Google) concernant des soucis de bleu virant au violet sous Chromium et Chrome. Bingo ! Et une solution est donnée pour corriger ça, il suffit d’aller dans
chrome://flags/et de forcer la valeur « sRGB » et c’est bon !En rouvrant l’image que j’avais en local, j’avais donc maintenant le même résultat entre Firefox et Chromium et je pensais donc avoir résolu le problème. Il ne manquait plus qu’à trouver comment ajouter ce paramètre dans les apps utilisant Electron.
Cependant, on va me dire que la capture de base n’est pas bonne. Celle-ci a été faite avec Firefox directement (sans autre modification derrière) mais je n’avais pas forcément prêté attention aux fait qu’elle n’avait pas les couleurs attendues… Pour bien comprendre le problème, vous pouvez faire un comparatif entre les deux images ci-dessous :
La différence est notamment visible au niveau du logo « GLF OS »… Le problème n’est donc pas lié qu’à Chromium, même si celui-ci réapplique le traitement sur les images qu’ils ouvrent, ce qui ne semble pas le cas de Firefox.
Sur le coup, je suis dépité et ne vois pas d’où vient le problème. Puis en laissant un peu de temps passer, une idée m’est venue en regardant les paramètres. Il y a une option « Couleur » dans les paramètres de Linux Mint dans la catégorie « Matériel » :
Lorsque l’on ouvre celle-ci, on a normalement un profil par défaut qui a été créé et qui correspond à la machine utilisée (les deux premières lignes dans mon cas) :
J’ai donc ajouté un profil et choisi « Artiflex Software sRGB ICC Profile » et le bleu est revenu ! A noter qu’il faut fermer et relancer les applications pour que cela prenne en compte le profil correctement. Je conseille donc de redémarrer pour être sûr que toutes les applications prennent bien le nouveau profil de couleur.
A noter qu’il y a le ticket #12637 ouvert chez Linux Mint concernant des problèmes de couleurs saturées. Dans les commentaires, on peut également lire le même constat sur le bleu qui vire vers le violet et voir la solution ci-dessus mentionnée.
Le problème semble lié à ce bon vieux X11 qui est encore là sous Linux Mint et potentiellement à un bug au niveau du profil de couleur par défaut. La bonne nouvelle, c’est qu’en me connectant sous Wayland avec le profil de couleur par défaut, je n’ai pas cette déformation sur le bleu. En revanche, en très peu de temps, j’ai pu constater d’autres bugs qui sont déjà listés ici.
Actuellement, Wayland sur Cinnamon est marqué comme expérimental et ça se voit vite. Ce n’est pas encore prêt, même si en soi, le système restait utilisable. Peut-être que pour Noël avec la version 23 de Linux Mint annoncée hier, Waylant sera prêt et ce problème du passé ?
L’avenir nous le dira ! En attendant, vous avez une solution si jamais vous constatez ce problème sur votre Linux Mint 😉
#Cinnamon #LinuxMint #LMDE #Mint #Wayland #X11 -
https://itsfoss.com/news/kde-plasma-per-screen-virtual-desktops/
I'm not a fan of the phrasing of this article Title. In truth, the "bug" was more of a feature request.
The following is my (limited) understanding of the issue
To have a different Virtual Desktop displayed on Each monitor. Something that couldn't be done, because of an X11 limitation. It is possible to do on Wayland, but no one actually sat down & did it until now.
-
Solution in #nixos #flake for machine ThinkPad #x230 seems to be:
services.xserver.enable = true;
services.displayManager.gdm.enable = true;
services.desktopManager.gnome.enable = true;
services.desktopManager.gnome.flashback.enableMetacity = true;
# At the GDM login screen, click the gear # icon to choose between:
# - "GNOME" (Wayland)
# - "GNOME Flashback (Metacity)" #X11
and
nixos-rebuild boot + reboot is required (not switch) when jumping across major nixpkgs versions -
Solution in #nixos #flake for machine ThinkPad #x230 seems to be:
services.xserver.enable = true;
services.displayManager.gdm.enable = true;
services.desktopManager.gnome.enable = true;
services.desktopManager.gnome.flashback.enableMetacity = true;
# At the GDM login screen, click the gear # icon to choose between:
# - "GNOME" (Wayland)
# - "GNOME Flashback (Metacity)" #X11
and
nixos-rebuild boot + reboot is required (not switch) when jumping across major nixpkgs versions -
Solution in #nixos #flake for machine ThinkPad #x230 seems to be:
services.xserver.enable = true;
services.displayManager.gdm.enable = true;
services.desktopManager.gnome.enable = true;
services.desktopManager.gnome.flashback.enableMetacity = true;
# At the GDM login screen, click the gear # icon to choose between:
# - "GNOME" (Wayland)
# - "GNOME Flashback (Metacity)" #X11
and
nixos-rebuild boot + reboot is required (not switch) when jumping across major nixpkgs versions -
Solution in #nixos #flake for machine ThinkPad #x230 seems to be:
services.xserver.enable = true;
services.displayManager.gdm.enable = true;
services.desktopManager.gnome.enable = true;
services.desktopManager.gnome.flashback.enableMetacity = true;
# At the GDM login screen, click the gear # icon to choose between:
# - "GNOME" (Wayland)
# - "GNOME Flashback (Metacity)" #X11
and
nixos-rebuild boot + reboot is required (not switch) when jumping across major nixpkgs versions -
Solution in #nixos #flake for machine ThinkPad #x230 seems to be:
services.xserver.enable = true;
services.displayManager.gdm.enable = true;
services.desktopManager.gnome.enable = true;
services.desktopManager.gnome.flashback.enableMetacity = true;
# At the GDM login screen, click the gear # icon to choose between:
# - "GNOME" (Wayland)
# - "GNOME Flashback (Metacity)" #X11
and
nixos-rebuild boot + reboot is required (not switch) when jumping across major nixpkgs versions -
I am trying to update my #nixos flake and discover that #x11 is not supported by the latest #gnome but I also know that some of my hardware (#HPelitedesk800 , VM machines running xrdp and x11spice) fails to show correct windows under #wayland so this is very un-linuxy and I feel like a sort of macos hardware obsolescence vibe ... Or is #Xfce the new way forward here for the good old tech? Thinkpad #x230 once failed with fifo underrun on pipe B when running wayland
-
I am trying to update my #nixos flake and discover that #x11 is not supported by the latest #gnome but I also know that some of my hardware (#HPelitedesk800 , VM machines running xrdp and x11spice) fails to show correct windows under #wayland so this is very un-linuxy and I feel like a sort of macos hardware obsolescence vibe ... Or is #Xfce the new way forward here for the good old tech? Thinkpad #x230 once failed with fifo underrun on pipe B when running wayland
-
I am trying to update my #nixos flake and discover that #x11 is not supported by the latest #gnome but I also know that some of my hardware (#HPelitedesk800 , VM machines running xrdp and x11spice) fails to show correct windows under #wayland so this is very un-linuxy and I feel like a sort of macos hardware obsolescence vibe ... Or is #Xfce the new way forward here for the good old tech? Thinkpad #x230 once failed with fifo underrun on pipe B when running wayland
-
I am trying to update my #nixos flake and discover that #x11 is not supported by the latest #gnome but I also know that some of my hardware (#HPelitedesk800 , VM machines running xrdp and x11spice) fails to show correct windows under #wayland so this is very un-linuxy and I feel like a sort of macos hardware obsolescence vibe ... Or is #Xfce the new way forward here for the good old tech? Thinkpad #x230 once failed with fifo underrun on pipe B when running wayland
-
I am trying to update my #nixos flake and discover that #x11 is not supported by the latest #gnome but I also know that some of my hardware (#HPelitedesk800 , VM machines running xrdp and x11spice) fails to show correct windows under #wayland so this is very un-linuxy and I feel like a sort of macos hardware obsolescence vibe ... Or is #Xfce the new way forward here for the good old tech? Thinkpad #x230 once failed with fifo underrun on pipe B when running wayland
-
Neste vídeo, eu mostro #MortalKombatX rodando em #FullHD, travado em #30FPS, na #RX550 de 4 GB, comparando o #desempenho entre #Debian13 e #LinuxMint223, lado a lado.
O teste foi feito usando o mesmo hardware e as mesmas configurações dentro do jogo.
No #Debian, o jogo roda em #Wayland, enquanto no #LinuxMint o teste foi feito em #X11.
-
Neste vídeo, eu mostro #MortalKombatX rodando em #FullHD, travado em #30FPS, na #RX550 de 4 GB, comparando o #desempenho entre #Debian13 e #LinuxMint223, lado a lado.
O teste foi feito usando o mesmo hardware e as mesmas configurações dentro do jogo.
No #Debian, o jogo roda em #Wayland, enquanto no #LinuxMint o teste foi feito em #X11.
-
The xlibre devs (or at least the people who made the website, https://x11libre.net/#about) are against DEI (see second-to-last sentence of fourth paragraph of what I linked). Do what you will with that information. Alpine and Chimera Linux have rejected XLibre for the same reason.
See also https://forum.artixlinux.org/index.php/topic,9343.msg56762.html#msg56762.
#x11 #linux #xlibre #artixlinux #artix_linux #uspol #uspolitics #dei -
Generally speaking, #Xwayland should be avoided for gaming where possible (which still isn't always possible, especially until Steam fix their overlay). The high latency people experience after switching from #X11 to #Wayland does not come from Wayland itself, but the indirection of this legacy compatibility layer. Don't take my word for it, this was measured in detail by David Justo this year:
-
Generally speaking, #Xwayland should be avoided for gaming where possible (which still isn't always possible, especially until Steam fix their overlay). The high latency people experience after switching from #X11 to #Wayland does not come from Wayland itself, but the indirection of this legacy compatibility layer. Don't take my word for it, this was measured in detail by David Justo this year:
-
Generally speaking, #Xwayland should be avoided for gaming where possible (which still isn't always possible, especially until Steam fix their overlay). The high latency people experience after switching from #X11 to #Wayland does not come from Wayland itself, but the indirection of this legacy compatibility layer. Don't take my word for it, this was measured in detail by David Justo this year:
-
Generally speaking, #Xwayland should be avoided for gaming where possible (which still isn't always possible, especially until Steam fix their overlay). The high latency people experience after switching from #X11 to #Wayland does not come from Wayland itself, but the indirection of this legacy compatibility layer. Don't take my word for it, this was measured in detail by David Justo this year:
-
Generally speaking, #Xwayland should be avoided for gaming where possible (which still isn't always possible, especially until Steam fix their overlay). The high latency people experience after switching from #X11 to #Wayland does not come from Wayland itself, but the indirection of this legacy compatibility layer. Don't take my word for it, this was measured in detail by David Justo this year:
-
John Bradley, the author of xv, has died. The program was one of the early versatile image viewers for X11 on UNIX like systems, and no Linux distro in the 1990s was complete without it.
If you want to try it out, it compiles very easily on modern Linux systems if you use this patched source:
https://github.com/ingowald/updated-xv
#x11 #xv #linux -
John Bradley, the author of xv, has died. The program was one of the early versatile image viewers for X11 on UNIX like systems, and no Linux distro in the 1990s was complete without it.
If you want to try it out, it compiles very easily on modern Linux systems if you use this patched source:
https://github.com/ingowald/updated-xv
#x11 #xv #linux -
John Bradley, the author of xv, has died. The program was one of the early versatile image viewers for X11 on UNIX like systems, and no Linux distro in the 1990s was complete without it.
If you want to try it out, it compiles very easily on modern Linux systems if you use this patched source:
https://github.com/ingowald/updated-xv
#x11 #xv #linux
