#xrandr — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #xrandr, aggregated by home.social.
-
Es más fuerte que yo, si un comando medianamente largo lo tengo que ejecutar más de dos veces, sale alias xD
Y lo peor, he creado un script que lo ejecuta sólo cuando inicio sesión en #lxqt, y ya no necesito ejecutar el comando 😅
Más sobre alias en la terminal de comandos? 👇
-
Es más fuerte que yo, si un comando medianamente largo lo tengo que ejecutar más de dos veces, sale alias xD
Y lo peor, he creado un script que lo ejecuta sólo cuando inicio sesión en #lxqt, y ya no necesito ejecutar el comando 😅
Más sobre alias en la terminal de comandos? 👇
-
Es más fuerte que yo, si un comando medianamente largo lo tengo que ejecutar más de dos veces, sale alias xD
Y lo peor, he creado un script que lo ejecuta sólo cuando inicio sesión en #lxqt, y ya no necesito ejecutar el comando 😅
Más sobre alias en la terminal de comandos? 👇
-
Es más fuerte que yo, si un comando medianamente largo lo tengo que ejecutar más de dos veces, sale alias xD
Y lo peor, he creado un script que lo ejecuta sólo cuando inicio sesión en #lxqt, y ya no necesito ejecutar el comando 😅
Más sobre alias en la terminal de comandos? 👇
-
RE: https://mstdn.io/@d1cor/115906601058645890
Va perfecto esto en #X11, el único tema es que, cuando suspendo el sistema, al despertarlo, tengo que ejecutar el comando xrandr de nuevo porque pierde el escalado de pantalla...
He probado varias cositas pero nada parece funcionar... habrá que actualizar y seguir buscando info 🙂
La otra, pasar mi #lxqt a #wayland, y cruzar los dedos con el driver de la #nvidia, mientras no se me joda el #minecraft, todo bien 😅
-
RE: https://mstdn.io/@d1cor/115906601058645890
Va perfecto esto en #X11, el único tema es que, cuando suspendo el sistema, al despertarlo, tengo que ejecutar el comando xrandr de nuevo porque pierde el escalado de pantalla...
He probado varias cositas pero nada parece funcionar... habrá que actualizar y seguir buscando info 🙂
La otra, pasar mi #lxqt a #wayland, y cruzar los dedos con el driver de la #nvidia, mientras no se me joda el #minecraft, todo bien 😅
-
RE: https://mstdn.io/@d1cor/115906601058645890
Va perfecto esto en #X11, el único tema es que, cuando suspendo el sistema, al despertarlo, tengo que ejecutar el comando xrandr de nuevo porque pierde el escalado de pantalla...
He probado varias cositas pero nada parece funcionar... habrá que actualizar y seguir buscando info 🙂
La otra, pasar mi #lxqt a #wayland, y cruzar los dedos con el driver de la #nvidia, mientras no se me joda el #minecraft, todo bien 😅
-
RE: https://mstdn.io/@d1cor/115906601058645890
Va perfecto esto en #X11, el único tema es que, cuando suspendo el sistema, al despertarlo, tengo que ejecutar el comando xrandr de nuevo porque pierde el escalado de pantalla...
He probado varias cositas pero nada parece funcionar... habrá que actualizar y seguir buscando info 🙂
La otra, pasar mi #lxqt a #wayland, y cruzar los dedos con el driver de la #nvidia, mientras no se me joda el #minecraft, todo bien 😅
-
RE: https://mstdn.io/@d1cor/115906601058645890
Va perfecto esto en #X11, el único tema es que, cuando suspendo el sistema, al despertarlo, tengo que ejecutar el comando xrandr de nuevo porque pierde el escalado de pantalla...
He probado varias cositas pero nada parece funcionar... habrá que actualizar y seguir buscando info 🙂
La otra, pasar mi #lxqt a #wayland, y cruzar los dedos con el driver de la #nvidia, mientras no se me joda el #minecraft, todo bien 😅
-
Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.
Covered topics:
1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
3) #Xrandr for multimonitor configuration
4) #Xserver settings for #HighDPI
5) #XDG utils and #Emacs as a system file manager
6) #XDM login windowhttps://eugene-andrienko.com/en/it/2025/07/24/x11-configuration-simple.html
-
Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.
Covered topics:
1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
3) #Xrandr for multimonitor configuration
4) #Xserver settings for #HighDPI
5) #XDG utils and #Emacs as a system file manager
6) #XDM login windowhttps://eugene-andrienko.com/en/it/2025/07/24/x11-configuration-simple.html
-
Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.
Covered topics:
1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
3) #Xrandr for multimonitor configuration
4) #Xserver settings for #HighDPI
5) #XDG utils and #Emacs as a system file manager
6) #XDM login windowhttps://eugene-andrienko.com/en/it/2025/07/24/x11-configuration-simple.html
-
Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.
Covered topics:
1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
3) #Xrandr for multimonitor configuration
4) #Xserver settings for #HighDPI
5) #XDG utils and #Emacs as a system file manager
6) #XDM login windowhttps://eugene-andrienko.com/en/it/2025/07/24/x11-configuration-simple.html
-
Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.
Covered topics:
1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
3) #Xrandr for multimonitor configuration
4) #Xserver settings for #HighDPI
5) #XDG utils and #Emacs as a system file manager
6) #XDM login windowhttps://eugene-andrienko.com/en/it/2025/07/24/x11-configuration-simple.html
-
OTT: Extreme Multihead For Gaming (on Linux PC):
https://beko.famkos.net/2021/05/31/extreme-multihead-for-gaming-on-linux-pc/All these hoops are basically obsolete with #gamescope nowadays, because this micro compositor allows to configure any virtual display size that games get to see - and handles upscaling on top.
#gamingonlinux #linux #linuxgaming #xrandr #x11 #xorg #xserver #multihead #widescreen #ultrawide #widescreen
-
OTT: Extreme Multihead For Gaming (on Linux PC):
https://beko.famkos.net/2021/05/31/extreme-multihead-for-gaming-on-linux-pc/All these hoops are basically obsolete with #gamescope nowadays, because this micro compositor allows to configure any virtual display size that games get to see - and handles upscaling on top.
#gamingonlinux #linux #linuxgaming #xrandr #x11 #xorg #xserver #multihead #widescreen #ultrawide #widescreen
-
OTT: Extreme Multihead For Gaming (on Linux PC):
https://beko.famkos.net/2021/05/31/extreme-multihead-for-gaming-on-linux-pc/All these hoops are basically obsolete with #gamescope nowadays, because this micro compositor allows to configure any virtual display size that games get to see - and handles upscaling on top.
#gamingonlinux #linux #linuxgaming #xrandr #x11 #xorg #xserver #multihead #widescreen #ultrawide #widescreen
-
OTT: Extreme Multihead For Gaming (on Linux PC):
https://beko.famkos.net/2021/05/31/extreme-multihead-for-gaming-on-linux-pc/All these hoops are basically obsolete with #gamescope nowadays, because this micro compositor allows to configure any virtual display size that games get to see - and handles upscaling on top.
#gamingonlinux #linux #linuxgaming #xrandr #x11 #xorg #xserver #multihead #widescreen #ultrawide #widescreen
-
OTT: Extreme Multihead For Gaming (on Linux PC):
https://beko.famkos.net/2021/05/31/extreme-multihead-for-gaming-on-linux-pc/All these hoops are basically obsolete with #gamescope nowadays, because this micro compositor allows to configure any virtual display size that games get to see - and handles upscaling on top.
#gamingonlinux #linux #linuxgaming #xrandr #x11 #xorg #xserver #multihead #widescreen #ultrawide #widescreen
-
This is how the Apple Cinema Display 23 responded when I tried to overclock its refresh rate. I knew it wouldn't work, but I still wanted to try using:
cvt 1920 1200 61.
I also tried 75 Hz, but the display turned off.
-
This is how the Apple Cinema Display 23 responded when I tried to overclock its refresh rate. I knew it wouldn't work, but I still wanted to try using:
cvt 1920 1200 61.
I also tried 75 Hz, but the display turned off.
-
This is how the Apple Cinema Display 23 responded when I tried to overclock its refresh rate. I knew it wouldn't work, but I still wanted to try using:
cvt 1920 1200 61.
I also tried 75 Hz, but the display turned off.
-
This is how the Apple Cinema Display 23 responded when I tried to overclock its refresh rate. I knew it wouldn't work, but I still wanted to try using:
cvt 1920 1200 61.
I also tried 75 Hz, but the display turned off.
-
This is how the Apple Cinema Display 23 responded when I tried to overclock its refresh rate. I knew it wouldn't work, but I still wanted to try using:
cvt 1920 1200 61.
I also tried 75 Hz, but the display turned off.
-
Just released new #pinxi (next #inxi ) has first draft of working monitor scaling support. The higher physical screen resolutions get, the more scaling is used. #mrmazda had off and on mentioned this as nice to have feature.
Not easy to figure out data sources but seems to work with #xrandr and wayland-info now.
I realized I could do scaling on my #xfce with #x11 which made dev a lot easier. Plus a good data file of #wayland scaled 3 monitor setup.
Updated graphics docs with new res section.
-
Just released new #pinxi (next #inxi ) has first draft of working monitor scaling support. The higher physical screen resolutions get, the more scaling is used. #mrmazda had off and on mentioned this as nice to have feature.
Not easy to figure out data sources but seems to work with #xrandr and wayland-info now.
I realized I could do scaling on my #xfce with #x11 which made dev a lot easier. Plus a good data file of #wayland scaled 3 monitor setup.
Updated graphics docs with new res section.
-
Just released new #pinxi (next #inxi ) has first draft of working monitor scaling support. The higher physical screen resolutions get, the more scaling is used. #mrmazda had off and on mentioned this as nice to have feature.
Not easy to figure out data sources but seems to work with #xrandr and wayland-info now.
I realized I could do scaling on my #xfce with #x11 which made dev a lot easier. Plus a good data file of #wayland scaled 3 monitor setup.
Updated graphics docs with new res section.
-
Just released new #pinxi (next #inxi ) has first draft of working monitor scaling support. The higher physical screen resolutions get, the more scaling is used. #mrmazda had off and on mentioned this as nice to have feature.
Not easy to figure out data sources but seems to work with #xrandr and wayland-info now.
I realized I could do scaling on my #xfce with #x11 which made dev a lot easier. Plus a good data file of #wayland scaled 3 monitor setup.
Updated graphics docs with new res section.
-
Cómo evitar que xss-lock bloquee la pantalla cuando una aplicación está a pantalla completa
xss-lock es un programa que gestiona el bloqueo de pantalla cuando el equipo está inactivo. xss-lock cumple esta tarea llamando a un bloqueador de pantalla externo, y comunicándose con el login manager que define el tiempo de inactividad antes de bloquear la pantalla y conecta con la sesión para salir del bloqueo.
Yo uso xss-lock para gestionar el bloqueo de pantalla en i3wm. xss-lock funciona estupendamente sin mucha configuración excepto cuando hay una aplicación a pantalla completa. En este caso bloquea la pantalla considerando que hay inactividad. Esto es especialmente molesto cuando estoy viendo una película: cada 5 minutos tengo que mover el ratón o se activa el bloqueo.
Para evitarlo he añadido un pequeño script de bash que monitoriza con wmctrl si hay alguna aplicación corriendo a pantalla completa. Si es así, pausa xss-lock con pkill. Cuando se sale del modo pantalla completa, el script reactiva xss-lock.
https://voragine.net/linux/xss-lock-bloqueo-aplicacion-pantalla-completa
-
#linuxTip: create alias ghist (stands for grep history). It allows you to check how you called your command (I'm mostly checking how I ran #xrandr
`alias ghist="history | grep $1"`
```
9763 history | grep xrandr
9765 xrandr --query
9786 xrandr --listmonitors
9787 xrandr --eDP1 --mode 1920x1080 --output DP1 --mode 2200x1650 --left-of eDP1
9905 xrandr-tv
9951 xrandr --auto
```You can call commands by writing `!<num-before-command>` in your terminal if you just want to repeat it.
-
#linuxTip: create alias ghist (stands for grep history). It allows you to check how you called your command (I'm mostly checking how I ran #xrandr
`alias ghist="history | grep $1"`
```
9763 history | grep xrandr
9765 xrandr --query
9786 xrandr --listmonitors
9787 xrandr --eDP1 --mode 1920x1080 --output DP1 --mode 2200x1650 --left-of eDP1
9905 xrandr-tv
9951 xrandr --auto
```You can call commands by writing `!<num-before-command>` in your terminal if you just want to repeat it.
-
#linuxTip: create alias ghist (stands for grep history). It allows you to check how you called your command (I'm mostly checking how I ran #xrandr
`alias ghist="history | grep $1"`
```
9763 history | grep xrandr
9765 xrandr --query
9786 xrandr --listmonitors
9787 xrandr --eDP1 --mode 1920x1080 --output DP1 --mode 2200x1650 --left-of eDP1
9905 xrandr-tv
9951 xrandr --auto
```You can call commands by writing `!<num-before-command>` in your terminal if you just want to repeat it.
-
#linuxTip: create alias ghist (stands for grep history). It allows you to check how you called your command (I'm mostly checking how I ran #xrandr
`alias ghist="history | grep $1"`
```
9763 history | grep xrandr
9765 xrandr --query
9786 xrandr --listmonitors
9787 xrandr --eDP1 --mode 1920x1080 --output DP1 --mode 2200x1650 --left-of eDP1
9905 xrandr-tv
9951 xrandr --auto
```You can call commands by writing `!<num-before-command>` in your terminal if you just want to repeat it.
-
#linuxTip: create alias ghist (stands for grep history). It allows you to check how you called your command (I'm mostly checking how I ran #xrandr
`alias ghist="history | grep $1"`
```
9763 history | grep xrandr
9765 xrandr --query
9786 xrandr --listmonitors
9787 xrandr --eDP1 --mode 1920x1080 --output DP1 --mode 2200x1650 --left-of eDP1
9905 xrandr-tv
9951 xrandr --auto
```You can call commands by writing `!<num-before-command>` in your terminal if you just want to repeat it.
-
So, the question is, in #icewm can I port each workspace to work independently to run each package I need to see? I've extensively read all the man pages for #icewm (I do use arch btw! 😅) but only find the typical #xrandr response. Without going thru the painstaking experimental road of which I've not enough time in this instance. For any #icewm experts out there, is it possible? Or should I just return to #i3? I love them both but found #icewm to be a tad more suitable for me.
2/2 -
So, the question is, in #icewm can I port each workspace to work independently to run each package I need to see? I've extensively read all the man pages for #icewm (I do use arch btw! 😅) but only find the typical #xrandr response. Without going thru the painstaking experimental road of which I've not enough time in this instance. For any #icewm experts out there, is it possible? Or should I just return to #i3? I love them both but found #icewm to be a tad more suitable for me.
2/2 -
So, the question is, in #icewm can I port each workspace to work independently to run each package I need to see? I've extensively read all the man pages for #icewm (I do use arch btw! 😅) but only find the typical #xrandr response. Without going thru the painstaking experimental road of which I've not enough time in this instance. For any #icewm experts out there, is it possible? Or should I just return to #i3? I love them both but found #icewm to be a tad more suitable for me.
2/2 -
my next mission id to move the giant ws for a smaller sff variant replacement - tomorrow - new box has 64gb ram - originally was going to be ids and probably still will be - making it the daily driver will help sort out and get up to speed a big quicker? machine should be a bit faster and more ram is great - also have 3 monitor option - one is just cheesy dumpster find but was still in box - it will do, more screen real estate is helpful usually, fairly confident linux will find and auto setup monitors rather than what it was like in the old days #xrandr
-
my next mission id to move the giant ws for a smaller sff variant replacement - tomorrow - new box has 64gb ram - originally was going to be ids and probably still will be - making it the daily driver will help sort out and get up to speed a big quicker? machine should be a bit faster and more ram is great - also have 3 monitor option - one is just cheesy dumpster find but was still in box - it will do, more screen real estate is helpful usually, fairly confident linux will find and auto setup monitors rather than what it was like in the old days #xrandr
-
my next mission id to move the giant ws for a smaller sff variant replacement - tomorrow - new box has 64gb ram - originally was going to be ids and probably still will be - making it the daily driver will help sort out and get up to speed a big quicker? machine should be a bit faster and more ram is great - also have 3 monitor option - one is just cheesy dumpster find but was still in box - it will do, more screen real estate is helpful usually, fairly confident linux will find and auto setup monitors rather than what it was like in the old days #xrandr
-
Finally managed. Cannot really tell what helped. I added the command to ~.config/i3/config as an exec without startup id at the very beginning.
It works there but if I type it in after the system started, I receive the same error and the screen goes dark again.
-
Finally managed. Cannot really tell what helped. I added the command to ~.config/i3/config as an exec without startup id at the very beginning.
It works there but if I type it in after the system started, I receive the same error and the screen goes dark again.
-
Finally managed. Cannot really tell what helped. I added the command to ~.config/i3/config as an exec without startup id at the very beginning.
It works there but if I type it in after the system started, I receive the same error and the screen goes dark again.
-
Finally managed. Cannot really tell what helped. I added the command to ~.config/i3/config as an exec without startup id at the very beginning.
It works there but if I type it in after the system started, I receive the same error and the screen goes dark again.
-
@fell I've never tried this myself but I believe that you could point the desktop shortcut to an app-startup script created by you, where you change the refresh with #xrandr, then launch the app and when closed, change back to native.
Something on the line as:
xrandr --rate 24
start app
xrandr --rate 60Hope this helps: https://wiki.ubuntu.com/X/Config/Resolution
-
@fell I've never tried this myself but I believe that you could point the desktop shortcut to an app-startup script created by you, where you change the refresh with #xrandr, then launch the app and when closed, change back to native.
Something on the line as:
xrandr --rate 24
start app
xrandr --rate 60Hope this helps: https://wiki.ubuntu.com/X/Config/Resolution
-
To run automatically when a change has been detected, save as `/usr/local/bin/toggle_display.sh` and create the following udev rule (eg. /etc/udev/rules.d/99-drm.rules)
ACTION=="change", SUBSYSTEM=="drm", ENV{HOTPLUG}=="1", RUN+="/usr/local/bin/toggle_display.sh"
then `sudo udevadm control --reload-rules` to apply the new rule.
-
Quick script to disable a laptop's internal panel (eDP-1) if an external monitor (HDMI-1) is plugged in (and vice-versa)
HDMI="HDMI-1"
eDP="eDP-1"
COMMAND="xrandr | grep \"$HDMI connected\" && xrandr --output $HDMI --auto --output $eDP --off || xrandr --output $eDP --auto --output $HDMI --off"
USER=$(who|grep -v root|cut -f1 -d\ |sort|uniq)
export DISPLAY=:0
export XAUTHORITY=/home/$USER/.Xauthority
su "$USER" -c "$COMMAND" -
One day I'll find a window manager that supports creating virtual monitors via #xrandr on the fly for _easy_ fullscreen usage over multiple monitors:
> xrandr --setmonitor UWU auto DisplayPort-0,HDMI-A-0,DisplayPort-2
This is a good moment to mention how awesome #gamescope is.
i.a.: I know it's not a #MST display but the same principle applies, no?
