Gnome Resolution and Scaling broke after testing DEs

wviana · 2023-08-12 02:48:14

I had everything pretty much working. Decided to try some other DE, just as I use to do time to time and always coming back into gnome. Tested plasma, scale got wrong, fixed, didn't like. Tested XFCE, scale got really bad, changing to 2x made it worst, had to change it to custom than 0.5 to make it usable. Played around a bit, decided that gnome was just good enought. Log out, log in into gnome. Now icons look different, it is usable just in 1x scale and get really large when change to 2x that is the one I use before testing others DEs. Even the top right tools menu is all wrong sizes now.

Any tip, any way to reset all these display config to the same as when just installed plain gnome from a clean installation?
What could had gone wrong?

It shouldn't break everything like this anyway should it?

Last edited by wviana (2023-08-18 22:10:24)

seth · 2023-08-12 06:22:10

https://bbs.archlinux.org/viewtopic.php?id=57855 and http://www.catb.org/~esr/faqs/smart-questions.html
Take a look at "printenv" and generally at https://wiki.archlinux.org/title/Hidpi to see what you might have fucked up to support yoru second take on the subject.

wviana · 2023-08-12 13:44:03

Thank you for taking your time to answer.

So, by reaching the HiDPI wiki page, I've tried running the two following commands

$ gsettings set org.gnome.settings-daemon.plugins.xsettings overrides "[{'Gdk/WindowScalingFactor', <2>}]"
$ gsettings set org.gnome.desktop.interface scaling-factor 2

Everything got really huge.

This is my printenv output:

ALACRITTY_LOG=/tmp/Alacritty-2919.log
ALACRITTY_SOCKET=/run/user/1000/Alacritty-:1-2919.sock
ALACRITTY_WINDOW_ID=56623108
ANDROID_HOME=/opt/android-sdk
ANDROID_SDK_ROOT=/opt/android-sdk
CASROOT=/usr
COLORTERM=truecolor
CSF_DrawPluginDefaults=/usr/share/opencascade/resources/DrawResources
CSF_EXCEPTION_PROMPT=1
CSF_IGESDefaults=/usr/share/opencascade/resources/XSTEPResource
CSF_LANGUAGE=us
CSF_MDTVTexturesDirectory=/usr/share/opencascade/resources/Textures
CSF_MIGRATION_TYPES=/usr/share/opencascade/resources/StdResource/MigrationSheet.txt
CSF_OCCTResourcePath=/usr/share/opencascade/resources
CSF_PluginDefaults=/usr/share/opencascade/resources/StdResource
CSF_SHMessage=/usr/share/opencascade/resources/SHMessage
CSF_STEPDefaults=/usr/share/opencascade/resources/XSTEPResource
CSF_ShadersDirectory=/usr/share/opencascade/resources/Shaders
CSF_StandardDefaults=/usr/share/opencascade/resources/StdResource
CSF_StandardLiteDefaults=/usr/share/opencascade/resources/StdResource
CSF_TObjDefaults=/usr/share/opencascade/resources/StdResource
CSF_TObjMessage=/usr/share/opencascade/resources/TObj
CSF_XCAFDefaults=/usr/share/opencascade/resources/StdResource
CSF_XSMessage=/usr/share/opencascade/resources/XSMessage
CSF_XmlOcafResource=/usr/share/opencascade/resources/XmlOcafResource
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
DESKTOP_SESSION=gnome
DISPLAY=:1
DRAWDEFAULT=/usr/share/opencascade/resources/DrawResources/DrawDefault
DRAWHOME=/usr/share/opencascade/resources/DrawResources
FLUTTER_HOME=/opt/flutter
GDMSESSION=gnome
GDM_LANG=en_US.UTF-8
GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/Alacritty.desktop
GIO_LAUNCHED_DESKTOP_FILE_PID=2919
GJS_DEBUG_OUTPUT=stderr
GJS_DEBUG_TOPICS=JS ERROR;JS LOG
GRADLE_HOME=/home/wviana/.sdkman/candidates/gradle/current
GTK3_MODULES=xapp-gtk3-module
GTK_IM_MODULE=ibus
HOME=/home/wviana
INVOCATION_ID=02f2de697d5c4f95b27a719ca0fed93c
JOURNAL_STREAM=8:28671
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LOGNAME=wviana
MAIL=/var/spool/mail/wviana
MANAGERPID=1869
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@x11.service/memory.pressure
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
MMGT_CLEAR=1
MOTD_SHOWN=pam
PATH=/home/wviana/.sdkman/candidates/kotlin/current/bin:/home/wviana/.sdkman/candidates/java/current/bin:/home/wviana/.sdkman/candidates/gradle/current/bin:/opt/flutter/bin:/home/wviana/.cargo/bin:/home/wviana/.local/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/opt/android-sdk/platform-tools:/opt/android-sdk/tools:/opt/android-sdk/tools/bin:/opt/flutter/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/lib/rustup/bin:/home/wviana/.rvm/bin:/home/wviana/.rvm/bin
PWD=/home/wviana
QT_IM_MODULE=ibus
SESSION_MANAGER=local/LasVegasArch:@/tmp/.ICE-unix/2008,unix/LasVegasArch:/tmp/.ICE-unix/2008
SHELL=/usr/bin/zsh
SHLVL=1
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXGEg0ed/agent.2931
SYSTEMD_EXEC_PID=2040
TERM=alacritty
USER=wviana
USERNAME=wviana
WINDOWID=56623108
WINDOWPATH=2
XAUTHORITY=/run/user/1000/gdm/Xauthority
XDG_CURRENT_DESKTOP=GNOME
XDG_DATA_DIRS=/home/wviana/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/
XDG_MENU_PREFIX=gnome-
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=gnome
XDG_SESSION_TYPE=x11
XMODIFIERS=@im=ibus
OLDPWD=/home/wviana
SSH_AGENT_PID=2932
EDITOR=nvim
SUDO_EDITOR=nvim
KUBECONFIG=/home/wviana/.config/kubeconfig.yaml
P9K_SSH=0
_P9K_SSH_TTY=/dev/pts/0
SDKMAN_DIR=/home/wviana/.sdkman
SDKMAN_CANDIDATES_API=https://api.sdkman.io/2
SDKMAN_PLATFORM=linuxx64
SDKMAN_CANDIDATES_DIR=/home/wviana/.sdkman/candidates
JAVA_HOME=/home/wviana/.sdkman/candidates/java/current
KOTLIN_HOME=/home/wviana/.sdkman/candidates/kotlin/current
P9K_TTY=old
_P9K_TTY=/dev/pts/0
_=/usr/bin/printenv

In my mind there is not much in logs to search by, because it is not failing anyway, just misbehaving.

Please fell free to ask any other data.
Got really frustrated with this. I should have made a BTRFS snapshot before playing around. But I still think installing other DE should not break anything.

seth · 2023-08-12 13:53:08

The idea was that you look around that page to asses which of those things you might have done.

But I still think installing other DE should not break anything.

It probably didn't? More the

fixed … changing to 2x made it worst, had to change it to custom than 0.5 to make it usable. Played around a bit

part.

I should have made a BTRFS snapshot before playing around.

Being a bit more mindful of your actions would probably have done as well.

Nothing in the environment, since you're on an X11 session, you might want to check

xrdb -q | grep -i dpi
xrandr -q # shows resolution and physical dimensions which allows you to calculate the physical DPI and pot. randr scaling
xdpyinfo | grep resolution

wviana · 2023-08-12 13:57:54

Found this

Aug 12 10:49:27 LasVegasArch kgx[6606]: Unknown key gtk-modules in /home/wviana/.config/gtk-4.0/settings.ini

in journalctl.

Do you know if it is safe to delete all .config gtk related files and folders?

seth · 2023-08-12 13:59:34

It's a safe way to lose all your gtk related settings.
And I doubt that an unknown key called "gtk-modules" will have significant impact on your DPI…

wviana · 2023-08-12 14:08:50

xrdb -q | grep -i dpi
Xft.dpi:        192

xrandr -q
Screen 0: minimum 320 x 200, current 2880 x 1800, maximum 16384 x 16384
eDP-1 connected primary 2880x1800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
   2880x1800     59.99*+
   2880x1620     59.96    59.97
   2560x1600     59.99    59.97
   2560x1440     59.99    59.99    59.96    59.95
   2048x1536     60.00
   1920x1440     60.00
   1856x1392     60.01
   1792x1344     60.01
   2048x1152     59.99    59.98    59.90    59.91
   1920x1200     59.95    59.88    59.95
   1920x1080     60.01    59.97    60.00    59.96    59.93
   1600x1200     60.00    59.95
   1680x1050     60.00    59.95    59.88
   1400x1050     59.98    60.00
   1600x900      59.99    59.94    59.95    59.82
   1280x1024     59.95    60.02
   1400x900      59.96    59.88
   1280x960      60.00    59.99
   1440x810      60.00    59.97
   1368x768      59.88    59.85
   1280x800      59.99    59.97    59.81    59.91
   1152x864      59.97
   1280x720      60.00    59.99    59.86    59.74
   1024x768      60.04    60.00    59.95
   960x720       60.00
   928x696       60.05
   896x672       60.01
   1024x576      59.95    59.96    59.90    59.82
   960x600       59.93    60.00
   960x540       59.96    59.99    59.63    59.82
   800x600       60.00    60.32    59.96    56.25
   840x525       60.01    59.88
   864x486       59.92    59.57
   700x525       59.98
   800x450       59.95    59.82
   640x512       60.02
   700x450       59.96    59.88
   640x480       60.00    59.94
   720x405       59.51    58.99
   684x384       59.88    59.85
   640x400       59.88    59.98
   640x360       59.86    59.83    59.84    59.32
   512x384       60.00
   512x288       60.00    59.92
   480x270       59.63    59.82
   400x300       60.32    56.34
   432x243       59.92    59.57
   320x240       60.05
   360x202       59.51    59.13
   320x180       59.84    59.32
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)

xdpyinfo | grep resolution
  resolution:    96x96 dots per inch

What about the icons? I'm pretty sure they are all changed. There was also some impact in Fonts.

wviana · 2023-08-12 14:09:52

seth wrote:

It's a safe way to lose all your gtk related settings.
And I doubt that an unknown key called "gtk-modules" will have significant impact on your DPI…

Yeah, deleting and rebooting changed just the config window background into white. Everything else still the same.

seth · 2023-08-12 14:20:21

What about what?

I'll do the math for you: the physical resolution is ~220dpi which is more than twice the logical resolution (which is why you probably used a scaling factor of 2 instead of just fixing the logical resolution)
But you also have the xft.dpi ramped up to 192 which is much closer to the physical resolution and if you scale that by 2, everything will be too big.

Your job is to boot your brain and remember what you did to cause this mess, then undo that.
My best guess is that you introduced the xrdb setting, but nobody else can possibly know what you did to get yourself into this situation.

You might want to review the hidpi wiki page on how to impact those elements.

wviana · 2023-08-12 14:27:36

seth wrote:

Your job is to boot your brain and remember what you did to cause this mess, then undo that.
My best guess is that you introduced the xrdb setting, but nobody else can possibly know what you did to get yourself into this situation.

The only thing I can think of was changing the x and y scale to 0.5 in xfce4 display settings? Because in xfce4 when changing scale to 2 it got looking even smaller.
I understand the usual "workflow" is to log into the DE, having everything smaller than it should and than adjusting the scale into 2x.

There was probably some kind of bug in xfce4 display config, as I'm assuming it should have everything small and scale up 2x.
Do you have any ideia of which files/configs does xfce4 changes?

seth · 2023-08-12 19:13:26

This is certainly NOT xfce4 specific because you're not using xfce4.

The "Xft.dpi: 192" doesn't just randomly appear there, you (or some GUI tool you used in your endeavour) probably added something to ~/.Xresources or ~/.Xdefaults or somewhere entirely else.
I doubt you'll have to "grep -ri 'xft.dpi' ~" and see what bubbles up.

wviana · 2023-08-12 19:42:51

seth wrote:

This is certainly NOT xfce4 specific because you're not using xfce4.

Yeah, but don't you think that what caused all this mess about, not only the scale, but also fonts and icons, was the xfce4 config?

seth wrote:

you (or some GUI tool you used in your endeavour) probably added something to ~/.Xresources or ~/.Xdefaults or somewhere entirely else.

I'm not using endeavour, just plain old arch linux.

I have just this to .X files in my home

$ ls .X*
.XCompose
.Xresources.bkp

Having the follow content

$cat .XCompose
 # UTF-8 (Unicode) compose sequences

 # Overrides C acute with Ccedilla:
 <dead_acute> <C> : "Ç" "Ccedilla"
 <dead_acute> <c> : "ç" "ccedilla"

and

$ cat .Xresources.bkp
*dpi: 150
Xft.dpi: 150

I assuming this sufixed with .bkp is not being used. I may move it somewhere else just to be sure.

seth wrote:

I doubt you'll have to "grep -ri 'xft.dpi' ~" and see what bubbles up.

By searching for xft.dpi in my home found just these files.

.zsh_history
.Xresources.bkp
.cargo/registry/src/github.com-1ecc6299db9ec823/x11rb-0.9.0/src/cursor/mod.rs
.cargo/registry/src/github.com-1ecc6299db9ec823/x11rb-0.9.0/src/resource_manager/mod.rs
.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.27.5/src/window.rs
.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.27.5/src/platform_impl/linux/x11/util/randr.rs
.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.27.5/src/dpi.rs
.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.27.5/CHANGELOG.md
.cargo/registry/src/github.com-1ecc6299db9ec823/x11rb-0.10.1/src/resource_manager/mod.rs
.cargo/registry/src/github.com-1ecc6299db9ec823/x11rb-0.10.1/src/cursor/mod.rs
.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.28.3/src/window.rs
.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.28.3/src/dpi.rs
.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.28.3/CHANGELOG.md
.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.28.3/src/platform_impl/linux/x11/util/randr.rs
./Repos/mastodon/postgres14: Permission denied (os error 13)
Repos/mastodon/redis/dump.rdb: Permission denied (os error 13)
.cache/clipboard-indicator@tudmotu.com/registry.txt

That just if xrdb is using the bkp sufixed file should not be related to it.

seth · 2023-08-12 19:47:20

Well, delete ~/.config/xfce4 and see whether that does anything.
Again: nobody but you has a good idea what you did there.

.Xresources.bkp (why is that there to begin with?) also would have the wrong value.

https://www.merriam-webster.com/dictionary/endeavor

Edit: since you didn't pick up on it, let me point out again that you could also just fix the DPI for good instead of resorting to specific scaling environments, https://wiki.archlinux.org/title/Xorg#D … ze_and_DPI
And you might want to start to actually quantify your displeasure with the status quo - saying it's "all wrong" is as subjective and vague as it possibly gets.

Last edited by seth (2023-08-12 20:15:07)

wviana · 2023-08-12 20:27:51

seth wrote:

Well, delete ~/.config/xfce4 and see whether that does anything.

Already done it some time ago. But as I'm using gnome no file from it should affect anyway. But it did it.

seth wrote:

Again: nobody but you has a good idea what you did there.

Yeah, I know, this is why I listed the things I've done right before getting it messy as it is right now in the post.
After figuring out how to make it back to work I'm thinking about setting up a VM and try to reproduce this by installing same DEs after having gnome working.

seth wrote:

.Xresources.bkp (why is that there to begin with?) also would have the wrong value.

https://www.merriam-webster.com/dictionary/endeavor

Probably I did way in the past. I use to rename my files into .bkp when testing, is this some kind of pattern in endeavor?

seth wrote:

Edit: since you didn't pick up on it, let me point out again that you could also just fix the DPI for good instead of resorting to specific scaling environments, https://wiki.archlinux.org/title/Xorg#D … ze_and_DPI

oh, is it already clear to you what is the problem? I don't remember setting anything manual to have my gnome nicely working.

Also just checked if there isn't any xorg configs, as the Wiki article says about some files in xorg.confg.d, but I don't have anything in there

$ ls /etc/X11/xorg.conf*
/etc/X11/xorg.conf.d

wviana · 2023-08-12 20:41:25

wviana wrote:

seth wrote:
.Xresources.bkp (why is that there to begin with?) also would have the wrong value.

https://www.merriam-webster.com/dictionary/endeavor

Probably I did way in the past. I use to rename my files into .bkp when testing, is this some kind of pattern in endeavor?

So sorry, just now I got it. didn't have this word in my vocabulary. My bad

wviana · 2023-08-12 20:50:59

Started a session in Wayland instead. Still getting some windows smalls and others in the right size.

https://ibb.co/K20ZQ9Y

moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by 2ManyDogs (2023-08-18 23:01:49)

seth · 2023-08-13 13:52:52

Yeah, I know, this is why I listed the things I've done right before getting it messy as it is right now in the post.

Where?
Your OP is "i did something and then something else and then tried stuff but didn't work".

I don't remember setting anything manual to have my gnome nicely working.

The OP wrote:

it is usable just in 1x scale and get really large when change to 2x that is the one I use before testing others DEs

…

Still getting some windows smalls and others in the right size.

Those will most likely be the xwayland clients.

oh, is it already clear to you what is the problem?

I know what the *problem* is, but, as mentioned several times, not what you did.

To get back to the status quo ante, most likely get rid of the xft setting. No, I don't and cannot know how you added that. grep your $HOME for 192 and hope for the best.
The alternative approach is to set the X11 server DPI properly (and not scale gnome via its environment/config) - I think I mentioned that twice before.

wviana · 2023-08-13 20:46:05

seth wrote:

Yeah, I know, this is why I listed the things I've done right before getting it messy as it is right now in the post.
Where?
Your OP is "i did something and then something else and then tried stuff but didn't work".

wviana wrote:

I had everything pretty much working. Decided to try some other DE, just as I use to do time to time and always coming back into gnome. Tested plasma, scale got wrong, fixed, didn't like. Tested XFCE, scale got really bad, changing to 2x made it worst, had to change it to custom than 0.5 to make it usable. Played around a bit, decided that gnome was just good enought. Log out, log in into gnome. Now icons look different, it is usable just in 1x scale and get really large when change to 2x that is the one I use before testing others DEs. Even the top right tools menu is all wrong sizes now.

Isn't this listing things I've done?

Trying to make clear:
- Have Gnome on xorg working fine, max resolution for built-in display with 200% scale
- Installed plasma, started, wrong scale, fixed by changing into 2x or something in plasmas settings
- Installed XFCE4, scale really bad/small, changing into 2x made it samller and 0.5 in custom setting to about right
- Jumped back into gnome, scaling all messy. ( bunch of things we've tried after it, now I get some things right scaled and other really small, eg. my web browser Brave, as in print)

seth wrote:

I don't remember setting anything manual to have my gnome nicely working.
The OP wrote:
it is usable just in 1x scale and get really large when change to 2x that is the one I use before testing others DEs
…

It's not clear to me what wrong here. By saying "not setting anything manual" I meant xrdb or xorg config. All changes I've done was using DE settings.

seth wrote:

Still getting some windows smalls and others in the right size.
Those will most likely be the xwayland clients.

Is there somewhere to check it?
Right now I'm getting pretty much same small Brave and other apps in wrong scale in both, xorg and wayland.

seth wrote:

oh, is it already clear to you what is the problem?
I know what the *problem* is, but, as mentioned several times, not what you did.

So what are the steps to make eveyrthing looks nice in same scale?
What actions get into this state is something I may try to reproduce later.

seth wrote:

To get back to the status quo ante, most likely get rid of the xft setting. No, I don't and cannot know how you added that. grep your $HOME for 192 and hope for the best.
The alternative approach is to set the X11 server DPI properly (and not scale gnome via its environment/config) - I think I mentioned that twice before.

As we already discussed before, there isn't any manual file setting for xorg or xrdb, I did grep for those settings in home and entire root too. Didn't find anything.
So I should use manual config files instead of plain gnome settings to get it back the correct scales?

wviana · 2023-08-13 20:58:26

$ gsettings set org.gnome.settings-daemon.plugins.xsettings overrides "[{'Gdk/WindowScalingFactor', <2>}]"
$ gsettings set org.gnome.desktop.interface scaling-factor 2

Did the trick to me.

wviana · 2023-08-18 22:14:01

Me again.

After this, today was the first time I plugged in an external monitor. Now I'm getting kind of the reverse problem.
After disabling built-in display and enabling just external (FHD), had to change the scale to 100% in gnome. Now gnome bars looks good. But other windows are really really huge.

https://ibb.co/6DZ53kN

moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by 2ManyDogs (2023-08-18 23:01:25)

wviana · 2023-08-18 22:16:47

I was able to make it look fine after running same commands I ajusted in HDIP Built-in display, but using value of 1 instead of 2.
There must be something really messy. Before everything was working out of the box.

Any tip to help investigate this is welcome.

2ManyDogs · 2023-08-18 23:02:21

Please stop multiposting. If you are the last person to post in a thread, and you have something to add, please use the edit button to amend the last post.

seth · 2023-08-19 05:55:24

You most likely are now using an output with a more "normal" DPI, but still have the xft.dpi settings that blow everything up.
Hard to tell because you just really love posting "its does nots works lol" and the tip is still the same: revert the introduction of the static xft.dpi

I did grep for those settings in home and entire root too. Didn't find anything.

You grepped for what *exactly*?
If you're to literal or specific that's not gonna work if the xrdb entry is bricked together by some config process.

You could add some autostart service to remove the entry after the fact, but every client started inbetween will be affected, so that's not an ideal solution at all.

wviana · 2023-08-21 23:09:18

seth wrote:

You most likely are now using an output with a more "normal" DPI, but still have the xft.dpi settings that blow everything up.
Hard to tell because you just really love posting "its does nots works lol" and the tip is still the same: revert the introduction of the static xft.dpi
I did grep for those settings in home and entire root too. Didn't find anything.
You grepped for what *exactly*?

Any tip about what I should grep? Is there a way to be sure that it's something related to xrdb?

seth · 2023-08-22 06:01:57

Please don't post screenshots.

seth wrote:

grep your $HOME for 192 and hope for the best

Also move away that .bkp stuff to make sure you're not parsing, symlinking or touching those files in any capacity.

Arch Linux

#1 2023-08-12 02:48:14

Gnome Resolution and Scaling broke after testing DEs

#2 2023-08-12 06:22:10

Re: Gnome Resolution and Scaling broke after testing DEs

#3 2023-08-12 13:44:03

Re: Gnome Resolution and Scaling broke after testing DEs

#4 2023-08-12 13:53:08

Re: Gnome Resolution and Scaling broke after testing DEs

#5 2023-08-12 13:57:54

Re: Gnome Resolution and Scaling broke after testing DEs

#6 2023-08-12 13:59:34

Re: Gnome Resolution and Scaling broke after testing DEs

#7 2023-08-12 14:08:50

Re: Gnome Resolution and Scaling broke after testing DEs

#8 2023-08-12 14:09:52

Re: Gnome Resolution and Scaling broke after testing DEs

#9 2023-08-12 14:20:21

Re: Gnome Resolution and Scaling broke after testing DEs

#10 2023-08-12 14:27:36

Re: Gnome Resolution and Scaling broke after testing DEs

#11 2023-08-12 19:13:26

Re: Gnome Resolution and Scaling broke after testing DEs

#12 2023-08-12 19:42:51

Re: Gnome Resolution and Scaling broke after testing DEs

#13 2023-08-12 19:47:20

Re: Gnome Resolution and Scaling broke after testing DEs

#14 2023-08-12 20:27:51

Re: Gnome Resolution and Scaling broke after testing DEs

#15 2023-08-12 20:41:25

Re: Gnome Resolution and Scaling broke after testing DEs

#16 2023-08-12 20:50:59

Re: Gnome Resolution and Scaling broke after testing DEs

#17 2023-08-13 13:52:52

Re: Gnome Resolution and Scaling broke after testing DEs

#18 2023-08-13 20:46:05

Re: Gnome Resolution and Scaling broke after testing DEs

#19 2023-08-13 20:58:26

Re: Gnome Resolution and Scaling broke after testing DEs

#20 2023-08-18 22:14:01

Re: Gnome Resolution and Scaling broke after testing DEs

#21 2023-08-18 22:16:47

Re: Gnome Resolution and Scaling broke after testing DEs

#22 2023-08-18 23:02:21

Re: Gnome Resolution and Scaling broke after testing DEs

#23 2023-08-19 05:55:24

Re: Gnome Resolution and Scaling broke after testing DEs

#24 2023-08-21 23:09:18

Re: Gnome Resolution and Scaling broke after testing DEs

#25 2023-08-22 06:01:57

Re: Gnome Resolution and Scaling broke after testing DEs

Board footer