Red and Blue swapped on gnome on xorg

The colors (on every screen - also attached external monitors) are wrong. It seems to be blue and red that are swapped. This also happens when I log in with a new user. And it only happens on gnome classic and gnome shell on xorg. I tried xfce and wayland.

Not all applications have that issue but the most: e.g a screenshot of this very site on firefox and vivaldi:
image
image

I have the feeling it was the last updated but it could also be some messing around with amdgpu drivers as I had an issue with a game. But if it would be the driver it would be wrong in every app and in gdm.

When taking a screenshot with flameshot the colors are correct and also when I sign out the colors appear normal for may be two tenth of a second before I get gdm.

Versions:
xorg-server 21.1.13
gnome-shell: 46.2
gnome-desktop-4: 44.0
mutter: 46.2

You might imagine I tried a lot already: downgrading to 46.1, switchting to wayland etc… Switchting to wayland might work but other things are not working that I often use so it is not an option. I also want to know what is the reason and try getting it solved.

Hi @iRaS,

What system, not user, config files have you recently edited? Let’s get the last…say 50:

history | grep sudo | tail -n 50
1 Like

Additional thought: At least one of those screenshots is a dead-ringer for tritanopia correction in the Gnome Colorblind Filters Extension. I’m not saying that this is the cause, but is it possible that you or someone else has installed some accessibility software that may be causing the issue?

2 Likes

I’ve had something similar on GNOME + Xorg where colours appear over saturated. Never found out the reason. Everything is OK on Wayland.

ah nice extension. It was not installed before and it seems this extension would also change how chromium browsers would calculate colors. But my issue is only outside of chromium browsers. I’m just confused because vivaldi is now showing a pink manjaro logo on a purple background (even after disabling the extension).

update: this was due to a test with color profiles from the monitor… they also apply to vivaldi but it seems they are only effective after relogin and for every user…

funny - that is my complete sudo history… maybe it is not complete but this installation is not very old:

$ history | grep sudo |grep -ve useradd -e adduser| head -n 50                                        
sudo downgrade xorg-server
sudo downgrade X11
sudo pacman -S xfce4
sudo downgrade gnome-shell
sudo downgrade mutter
sudo downgrade gnome-control-center
sudo reboot
sudo downgrade gdm
sudo pacman-mirrors --geoip
echo low |sudo tee /sys/class/drm/card1/device/power_dpm_force_performance_level
echo high |sudo tee /sys/class/drm/card1/device/power_dpm_force_performance_level
sudo vi /etc/default/grub
sudo vi /etc/X11/xorg.conf.d/99-mouse-scroll.conf
sudo vi /etc/samba/smb.conf
sudo pip install material-color-utilities
sudo mount -o remount,rw /run/media/iras/ERGO2040R
sudo vi /etc/makepkg.conf
sudo vi /etc/pacman.conf
sudo rm -Rf redaktion/htdocs/rsdata/data
sudo vi /etc/hosts
sudo usermod -aG docker iras
sudo DISPLAY=:0 visudo
sudo visudo
sudo echo $EDITOR
sudo EDITOR=/usr/bin/gedit visudo
sudo gedit
sudo EDITOR=gedit visudo
sudo -i
sudo env
sudo echo $VISUAL
sudo echo $SUDO_EDITOR
ctl status|grep sudo
sudo visudo -c
sudo visudo -V
sudo visudo -v
man visudo
sudo EDITOR=vim visudo
sudo visudo --help
cat /etc/sudoers.d/*
sudo newgrp docker
sudo usermod iras -G docker
sudo screen -R circpy /dev/ttyACM0 115200
sudo screen -R circpy8 /dev/ttyACM2 115200
sudo screen -R /dev/ttyACM0 115200

I’m using fish and this is sorting the history in reverse…

What me confuses me so hard is that vivaldi is showing “normal” colors.

This :point_down:

and this:

…to me looks like the only things that could cause this. And I’m not sure.

But maybe someone else knows.

This:

Is very strange.

As far as I know, Vivaldi is a Chrome based browser, which is a GTK app, so it almost seems like GTK apps are working…

Do you perhaps have hybrid graphics? So colour correction, or whatever you want to call it is applied to the one GPU and not the other?

1 Like

yes, got it!

I think it was the mesa-git repo that caused that issue.

[2024-07-15T10:32:08+0200] [ALPM] transaction started
[2024-07-15T10:32:08+0200] [ALPM] removed mesa-git (24.2.0_devel.191427.68215332a8c.d41d8cd-1)
[2024-07-15T10:32:08+0200] [ALPM] installed mesa (1:24.1.1-1)
[2024-07-15T10:32:08+0200] [ALPM] installed mesa-vdpau (1:24.1.1-1)
[2024-07-15T10:32:08+0200] [ALPM] installed vulkan-intel (1:24.1.1-1)
[2024-07-15T10:32:08+0200] [ALPM] installed vulkan-radeon (1:24.1.1-1)
[2024-07-15T10:32:08+0200] [ALPM] transaction completed

Thaaaat might be it, yes! Very well done!