Colours shifted

[Leonick]

Pretty fresh install of Fedora. Sometimes when I connect all the colours are shifted in some weird way. The standard Fedora blue turns orange while the Firefox icon turns blue.

Bizzarely the colours swatch in KolourPaint shows correctly, but pretty much everything else from icons to wallpaper is shifted.

First few times some variant of restarting the machine or signing out out and in again cleared it. But this latest time has been stubborn, I’ve restarted the server machine, server software, and client machine.

The colours are wrong both when connecting from Windows and from iPad. Colours are correct on attached screen.

Attachments:

1. 

   nomachine.jpg
   

[Britgirl]

Hi, we’ve never seen this before. Can you send the logs from the server? Please gather them using this command:

$ sudo tar -cvp --exclude 'cache*' --exclude 'images' --exclude 'temp' $HOME/.nx | gzip -c >user_nxdir.tar.gz

[Leonick]

I wasn’t allowed to upload “this file type” so here is a link instead:
user_nxdir.tar.gz

Only time I can point at for your to look at would be when I made the original post. Didn’t take note of any other times.

KolourPaint was the only thing I encountered that didn’t shift the colours when it occured. Opening an image in whatever the default viewer was, VLC, video in Firefox, all had the shifting.

I’ve ditched Fedora for the time being. No similar issues on Linux Mint (same hardware) so far.

[fra81]

Hi,

can you tell us about:

– Fedora version
– Plasma version
– Graphics card and drivers

[Leonick]

Fedora Workstation 41, KDE spin

Plasma Desktop 6.2.1

Intel Integrated (i7-12700T) with whatever drivers Fedora decided to use, I didn’t install any specific ones.

[Victor]

Have the same issue on Arch Linux with Plasma Desktop (Wayland), Radeon RX 570 GPU (but SW H.264 encoding was used).
NoMachine free v8.14.2

Operating System: Arch Linux

KDE Plasma Version: 6.2.4

KDE Frameworks Version: 6.9.0

Qt Version: 6.8.1

Kernel Version: 6.12.4-zen1-1.1-zen (64-bit)

Graphics Platform: Wayland

Graphics Processor: AMD Radeon RX 570 Series

[Britgirl]

It is a combination of 2 issues. One is documented here, https://kb.nomachine.com/TR05V11141, which causes the default capture method (EGL) to fail. The second issue occurs when using the fallback method (DRM) and it is due to an unexpected colorspace format which we’re still investigating and will keep you posted.

[Britgirl]

Hi Victor and Leonick, would you be interested in trying a test library that we have prepared? It’s not a definitive fix, but it would help us for our investigations. We will send you a download link to the library and further instructions, we would basically need to know if there are any visible changes.

[Victor]

Hi Victor and Leonick, would you be interested in trying a test library that we have prepared? It’s not a definitive fix, but it would help us for our investigations. We will send you a download link to the library and further instructions, we would basically need to know if there are any visible changes.

I would be happy to try it. You can email me at: [removed] [at] yandex [dot] com

[Victor]

Hi Victor and Leonick, would you be interested in trying a test library that we have prepared? It’s not a definitive fix, but it would help us for our investigations. We will send you a download link to the library and further instructions, we would basically need to know if there are any visible changes.

I should note that with the original NoMachine v8.14.2 (with no libnxdimi.so patched) this issue disappeared after system updating to Plasma 6.2.5. Colors is now correctly:
Operating System: Arch Linux KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.12.9-zen1-1.1-zen (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 570 Series

However, the patched libnxdimi.so which you sent me by E-mail, on the contrary, breaks colors in Plasma 6.2.5 on this machine.

[Britgirl]

Based on what you’ve told us, that updating to Plasma 6.2.5 eliminates the problem, the test library we sent you should be uninstalled, and we consider the issue solved. Update to NoMachine 8.15, if the problem comes back, we can investigate further.

[Author]

Posts