home.social

#xserver — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #xserver, aggregated by home.social.

  1. XLibre packages are available in Fedora Copr repository. Learn how to install XLibre X11 Server in Fedora, RHEL, AlmaLinux and Rocky Linux.

    Full guide here: ostechnix.com/install-xlibre-x

    #XLibre #X11 #Xserver #Fedora #RHEL #Almalinux #Rockylinux #Linux

  2. XLibre packages are available in Fedora Copr repository. Learn how to install XLibre X11 Server in Fedora, RHEL, AlmaLinux and Rocky Linux.

    Full guide here: ostechnix.com/install-xlibre-x

    #XLibre #X11 #Xserver #Fedora #RHEL #Almalinux #Rockylinux #Linux

  3. XLibre packages are available in Fedora Copr repository. Learn how to install XLibre X11 Server in Fedora, RHEL, AlmaLinux and Rocky Linux.

    Full guide here: ostechnix.com/install-xlibre-x

    #XLibre #X11 #Xserver #Fedora #RHEL #Almalinux #Rockylinux #Linux

  4. XLibre packages are available in Fedora Copr repository. Learn how to install XLibre X11 Server in Fedora, RHEL, AlmaLinux and Rocky Linux.

    Full guide here: ostechnix.com/install-xlibre-x

    #XLibre #X11 #Xserver #Fedora #RHEL #Almalinux #Rockylinux #Linux

  5. XLibre packages are available in Fedora Copr repository. Learn how to install XLibre X11 Server in Fedora, RHEL, AlmaLinux and Rocky Linux.

    Full guide here: ostechnix.com/install-xlibre-x

    #XLibre #X11 #Xserver #Fedora #RHEL #Almalinux #Rockylinux #Linux

  6. Die Entfernung des alten Codes für die #XServer-Anbindung hat zu einer signifikanten Verschlankung der Codebasis geführt – laut #Gnome-Projekt sind gut 40 Prozent Quellcode weggefallen, was dem Wartungsaufwand zugutekommt.

    Wow 40% ... das ist echt ne Menge.

    https://www.heise.de/news/Gnome-50-mach-s-gut-X-Server-11215600.html

  7. Slightly updated my blogpost about X11 (again):
    1) Add subsection about xlock to the "Screensaver" section with sample configuration involving xlock and xautolock usage.
    2) Add subsection about how to properly start xdm — according to the documentation in the FreeBSD — the /etc/ttys should be changed, not the /etc/rc.conf.
    3) In the "GTK3" subsection wrote about hack from ArchWiki to force GTK3 not to conform X server settings (I starting to think that this is impossible), but to display fonts and UI elements at least the same size like other toolkits — when the HighDPI display is in use.
    4) Remove wrong line ("XTerm.vt100.selectToClipboard: true") from xterm X resources, so the mouse selection appears in the right clipboard and can be pasted with middle-click of mouse.

    eugene-andrienko.com/it/2025/0

    #Xserver #FreeBSD

  8. Slightly updated my blogpost about X11 (again):
    1) Add subsection about xlock to the "Screensaver" section with sample configuration involving xlock and xautolock usage.
    2) Add subsection about how to properly start xdm — according to the documentation in the FreeBSD — the /etc/ttys should be changed, not the /etc/rc.conf.
    3) In the "GTK3" subsection wrote about hack from ArchWiki to force GTK3 not to conform X server settings (I starting to think that this is impossible), but to display fonts and UI elements at least the same size like other toolkits — when the HighDPI display is in use.
    4) Remove wrong line ("XTerm.vt100.selectToClipboard: true") from xterm X resources, so the mouse selection appears in the right clipboard and can be pasted with middle-click of mouse.

    eugene-andrienko.com/it/2025/0

    #Xserver #FreeBSD

  9. Slightly updated my blogpost about X11 (again):
    1) Add subsection about xlock to the "Screensaver" section with sample configuration involving xlock and xautolock usage.
    2) Add subsection about how to properly start xdm — according to the documentation in the FreeBSD — the /etc/ttys should be changed, not the /etc/rc.conf.
    3) In the "GTK3" subsection wrote about hack from ArchWiki to force GTK3 not to conform X server settings (I starting to think that this is impossible), but to display fonts and UI elements at least the same size like other toolkits — when the HighDPI display is in use.
    4) Remove wrong line ("XTerm.vt100.selectToClipboard: true") from xterm X resources, so the mouse selection appears in the right clipboard and can be pasted with middle-click of mouse.

    eugene-andrienko.com/it/2025/0

    #Xserver #FreeBSD

  10. Slightly updated my blogpost about X11 (again):
    1) Add subsection about xlock to the "Screensaver" section with sample configuration involving xlock and xautolock usage.
    2) Add subsection about how to properly start xdm — according to the documentation in the FreeBSD — the /etc/ttys should be changed, not the /etc/rc.conf.
    3) In the "GTK3" subsection wrote about hack from ArchWiki to force GTK3 not to conform X server settings (I starting to think that this is impossible), but to display fonts and UI elements at least the same size like other toolkits — when the HighDPI display is in use.
    4) Remove wrong line ("XTerm.vt100.selectToClipboard: true") from xterm X resources, so the mouse selection appears in the right clipboard and can be pasted with middle-click of mouse.

    eugene-andrienko.com/it/2025/0

    #Xserver #FreeBSD

  11. Slightly updated my blogpost about X11 (again):
    1) Add subsection about xlock to the "Screensaver" section with sample configuration involving xlock and xautolock usage.
    2) Add subsection about how to properly start xdm — according to the documentation in the FreeBSD — the /etc/ttys should be changed, not the /etc/rc.conf.
    3) In the "GTK3" subsection wrote about hack from ArchWiki to force GTK3 not to conform X server settings (I starting to think that this is impossible), but to display fonts and UI elements at least the same size like other toolkits — when the HighDPI display is in use.
    4) Remove wrong line ("XTerm.vt100.selectToClipboard: true") from xterm X resources, so the mouse selection appears in the right clipboard and can be pasted with middle-click of mouse.

    eugene-andrienko.com/it/2025/0

    #Xserver #FreeBSD

  12. Huh, looks like my today's presentation about X server setup for minimalists (based on my eugene-andrienko.com/it/2025/0 blogpost) will be kinda … controversial, lol :drgn_blush_giggle:

    Usually, announcments in this #hackspace channel have only positive emojis :drgn_cup_mlem:

    #X11 #XServer

  13. Huh, looks like my today's presentation about X server setup for minimalists (based on my eugene-andrienko.com/it/2025/0 blogpost) will be kinda … controversial, lol :drgn_blush_giggle:

    Usually, announcments in this #hackspace channel have only positive emojis :drgn_cup_mlem:

    #X11 #XServer

  14. Huh, looks like my today's presentation about X server setup for minimalists (based on my eugene-andrienko.com/it/2025/0 blogpost) will be kinda … controversial, lol :drgn_blush_giggle:

    Usually, announcments in this #hackspace channel have only positive emojis :drgn_cup_mlem:

    #X11 #XServer

  15. Huh, looks like my today's presentation about X server setup for minimalists (based on my eugene-andrienko.com/it/2025/0 blogpost) will be kinda … controversial, lol :drgn_blush_giggle:

    Usually, announcments in this #hackspace channel have only positive emojis :drgn_cup_mlem:

    #X11 #XServer

  16. Huh, looks like my today's presentation about X server setup for minimalists (based on my eugene-andrienko.com/it/2025/0 blogpost) will be kinda … controversial, lol :drgn_blush_giggle:

    Usually, announcments in this #hackspace channel have only positive emojis :drgn_cup_mlem:

    #X11 #XServer

  17. The Input Stack on Linux – An End-To-End Architecture Overview

    venam.net/blog/unix/2025/11/27

    Patrick Louis writes: ""Let’s explore and deobfuscate the input stack on #Linux. Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer:

    #Kernel-level handling: It deals with what happens in the kernel and how events are exposed to user-space
    […]
    Exposed layer (middle)
    […]
    User-space handling:
    […]
    The Widgets, #XServer, #X11 window managers, and #Wayland compositors, which rely on everything else

    We’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.""

    #LinuxKernel #evdev

  18. The Input Stack on Linux – An End-To-End Architecture Overview

    venam.net/blog/unix/2025/11/27

    Patrick Louis writes: ""Let’s explore and deobfuscate the input stack on #Linux. Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer:

    #Kernel-level handling: It deals with what happens in the kernel and how events are exposed to user-space
    […]
    Exposed layer (middle)
    […]
    User-space handling:
    […]
    The Widgets, #XServer, #X11 window managers, and #Wayland compositors, which rely on everything else

    We’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.""

    #LinuxKernel #evdev

  19. The Input Stack on Linux – An End-To-End Architecture Overview

    venam.net/blog/unix/2025/11/27

    Patrick Louis writes: ""Let’s explore and deobfuscate the input stack on . Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer:

    -level handling: It deals with what happens in the kernel and how events are exposed to user-space
    […]
    Exposed layer (middle)
    […]
    User-space handling:
    […]
    The Widgets, , window managers, and compositors, which rely on everything else

    We’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.""

  20. The Input Stack on Linux – An End-To-End Architecture Overview

    venam.net/blog/unix/2025/11/27

    Patrick Louis writes: ""Let’s explore and deobfuscate the input stack on #Linux. Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer:

    #Kernel-level handling: It deals with what happens in the kernel and how events are exposed to user-space
    […]
    Exposed layer (middle)
    […]
    User-space handling:
    […]
    The Widgets, #XServer, #X11 window managers, and #Wayland compositors, which rely on everything else

    We’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.""

    #LinuxKernel #evdev

  21. The Input Stack on Linux – An End-To-End Architecture Overview

    venam.net/blog/unix/2025/11/27

    Patrick Louis writes: ""Let’s explore and deobfuscate the input stack on #Linux. Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer:

    #Kernel-level handling: It deals with what happens in the kernel and how events are exposed to user-space
    […]
    Exposed layer (middle)
    […]
    User-space handling:
    […]
    The Widgets, #XServer, #X11 window managers, and #Wayland compositors, which rely on everything else

    We’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.""

    #LinuxKernel #evdev

  22. 🚨 Oh no! The X.Org X server has more holes than a Swiss cheese! 🧀 For the six people who still use it, the suspense of those 'multiple issues' is killing us. Who knew X could stand for 'xtra' vulnerabilities? 🤦‍♂️
    lists.x.org/archives/xorg-anno #XOrg #XServer #Vulnerabilities #SwissCheese #CyberSecurity #TechNews #VulnerabilityAlert #HackerNews #ngated

  23. 🚨 Oh no! The X.Org X server has more holes than a Swiss cheese! 🧀 For the six people who still use it, the suspense of those 'multiple issues' is killing us. Who knew X could stand for 'xtra' vulnerabilities? 🤦‍♂️
    lists.x.org/archives/xorg-anno #XOrg #XServer #Vulnerabilities #SwissCheese #CyberSecurity #TechNews #VulnerabilityAlert #HackerNews #ngated

  24. 🚨 Oh no! The X.Org X server has more holes than a Swiss cheese! 🧀 For the six people who still use it, the suspense of those 'multiple issues' is killing us. Who knew X could stand for 'xtra' vulnerabilities? 🤦‍♂️
    lists.x.org/archives/xorg-anno #XOrg #XServer #Vulnerabilities #SwissCheese #CyberSecurity #TechNews #VulnerabilityAlert #HackerNews #ngated

  25. 🚨 Oh no! The X.Org X server has more holes than a Swiss cheese! 🧀 For the six people who still use it, the suspense of those 'multiple issues' is killing us. Who knew X could stand for 'xtra' vulnerabilities? 🤦‍♂️
    lists.x.org/archives/xorg-anno #XOrg #XServer #Vulnerabilities #SwissCheese #CyberSecurity #TechNews #VulnerabilityAlert #HackerNews #ngated

  26. Ah, the #SIXEL #revolution is here! 🚀 Now you can enjoy the #retro excitement of running an X server on your #terminal, because who wouldn't want to squint at pixelated #graphics in 2023? 🤦‍♂️ Meanwhile, real developers are busy inventing #AI that writes code while you nap. 💤🔧
    github.com/saitoha/xserver-SIX #Xserver #HackerNews #ngated

  27. Ah, the #SIXEL #revolution is here! 🚀 Now you can enjoy the #retro excitement of running an X server on your #terminal, because who wouldn't want to squint at pixelated #graphics in 2023? 🤦‍♂️ Meanwhile, real developers are busy inventing #AI that writes code while you nap. 💤🔧
    github.com/saitoha/xserver-SIX #Xserver #HackerNews #ngated

  28. Ah, the #SIXEL #revolution is here! 🚀 Now you can enjoy the #retro excitement of running an X server on your #terminal, because who wouldn't want to squint at pixelated #graphics in 2023? 🤦‍♂️ Meanwhile, real developers are busy inventing #AI that writes code while you nap. 💤🔧
    github.com/saitoha/xserver-SIX #Xserver #HackerNews #ngated

  29. Ah, the #SIXEL #revolution is here! 🚀 Now you can enjoy the #retro excitement of running an X server on your #terminal, because who wouldn't want to squint at pixelated #graphics in 2023? 🤦‍♂️ Meanwhile, real developers are busy inventing #AI that writes code while you nap. 💤🔧
    github.com/saitoha/xserver-SIX #Xserver #HackerNews #ngated