Forum / NoMachine for Linux / Corrupt black screen when viewing a Gnome session from Ubuntu 22.04
- This topic has 5 replies, 2 voices, and was last updated 3 years, 6 months ago by
Britgirl.
-
AuthorPosts
-
April 26, 2022 at 05:49 #38413
jigglywigglyParticipantThe server I am connecting to is running Gnome desktop and Mate desktop. It is running Ubuntu 20.04 with a GTX 3070.
From Windows, I can connect to the gnome-session and mate session just perfectly.
From my Ubuntu 22.04 machine though, when I connect to the gnome session on that server, I get a black screen with some corruption. I can see bits and piece of the screen but it won’t last.
Strangely, when I connect to the mate session, I can see everything just fine.
I am using an RX 6900 XT, Wayland session.
Not sure what else to include detail wise…
April 26, 2022 at 10:54 #38425
BritgirlKeymasterCan you submit a screenshot showing the problem? From what you describe it sounds like a rendering issue on the client side. Please try disabling hardware decoding on the Ubuntu 22.04 computer (client). You can do that by connecting to the server, opening the menu with Ctrl-Alt-0 -> Display -> Change settings -> Modify and ticking the box “Disable client side hardware decoding”. Does this help?
May 1, 2022 at 01:37 #38473
jigglywigglyParticipantActually as I try again today, I can see it just fine. I have restarted my computer since, maybe the hardware client side settings to disable them didn’t apply until I rebooted? Not sure, but it seems to work fine now.
May 2, 2022 at 08:31 #38472
jigglywigglyParticipantHi, sure it looks like this.
So the problem isn’t actually related to gnome/mate. It is the program Vivado that shows up as black. I tried disabling client side hardware acceleration but it did not help. It is very strange to me that when I open the same session on my Windows computer, I can see Vivado just clearly. Vivado is a java app.
May 2, 2022 at 08:36 #38484
BritgirlKeymasterHi Jigglywiggly, can you submit the image as an attachment?
May 4, 2022 at 15:59 #38500
BritgirlKeymastermaybe the hardware client side settings to disable them didn’t apply until I rebooted?
No, restarting the machine wouldn’t make a difference for hardware decoding, so it is very likely unrelated to hw decoding
As far as I understand, the problem appears only with one application?
Googling I found this: https://support.xilinx.com/s/question/0D52E00006hprh2SAA/vivado-20201-display-problem?language=en_US. Is this similar to your issue?
-
AuthorPosts
This topic was marked as solved, you can't post.
