Forum / NoMachine for Linux / Black screen with mouse showing upon login
Tagged: black-screen, GDM3 not start, mouse showing, Ubuntu 22.04
- This topic has 10 replies, 4 voices, and was last updated 2 years, 3 months ago by Liftaren.
-
AuthorPosts
-
July 31, 2022 at 12:58 #39517LiftarenParticipant
Hi,
Since installing Fedora 36 I have had problems with NoMachine. Started with 7.9.x and now with 7.10.1.
Problem: black screen with mouse showing upon login.
Tested with the same problem on the following distros: Fedora 36, Ubuntu 22.04, OpenSUSE Tumbleweed (also on Gnome 42). I have tested the client in both Xorg and Wayland sessions.
Working without problems on the following distros: Linux Mint 20.3, MX Linux 21.1
(also working from other computers with Windows and iOS, so the server side seems completely fine)
Client side has an AMD 6800 XT, using mesa drivers. Have tested two different computers as servers with the same behavior.
The solution for Fedora 36 client (not sure if it is Gnome or perhaps mesa?, or something else) was to setup the server with specified hardware acceleration and not use H264 (both VP8 and MJPEG works).
NoMachine Free version, server(s) has physical display and Alma Linux 8.x (CentOS 8 Stream).
August 1, 2022 at 11:36 #39525BritgirlKeymasterIt could be related to the drivers on the client-side Linux machine you mention. You said you’ve tried connecting from Fedora 36, Ubuntu 22.04 and OpenSuse Tumbleweed. Are these distros tested from the same machine, so you are just changing the Linux distro, or are you connecting from different Linux machines?
Logs would be useful from both sides of a problematic session, so we can eliminate possible causes.
https://kb.nomachine.com/DT11R00182
https://kb.nomachine.com/DT11R00181Send them directly to forum[at]nomachine[dot]com or attach here.
August 10, 2022 at 17:08 #39651LiftarenParticipantHi,
I did not manage to produce any logs. However, what I did manage was to upgrade Mesa on Ubuntu 20.04 from the 21.x branch to the 22.x that both Fedora 36 and Ubuntu 22.04 are on.
Ubuntu 20.04 with Mesa 21.x –> works fine without any problems
Ubuntu 20.04 with Mesa 22.x –> same type of graphical issues as with Fedora 36, Tumbleweed and Ubuntu 22.04.
(I also tested Linux Mint 21 XFCE which had the same problem so this is not related to GNOME).
It seems very likely that the issue with NoMachine is related to the Mesa drivers.
August 11, 2022 at 14:29 #39674MegaSlonicParticipantHello! I have a similar problem – a black screen and a mouse cursor. I think GDM3 does not start. The problem was noticed around Jul 30. The client and the Server are both on Ubuntu 22.04. Client on the Mesa Radeon by Ubuntu community driver, and server on proprietary Nvidia v.470 driver. NoMachine v.7.10.1 deb64
Until Jul 30, the problem was not observed. It worked all before. NoMachine settings have not changed. Only updated core and video drivers.
August 12, 2022 at 16:15 #39692fra81ModeratorDisabling H.264 solved the issue for Liftaren. Is it the same for you?
And can you both try to check ‘Disable client side hardware decoding’ in the Display settings tab of the menu panel (Modify button)? Is this enough to solve the problem even when using H.264?
And as Britgirl mentioned, logs would be useful, especially client side logs:
August 17, 2022 at 09:39 #39734MegaSlonicParticipantDisabled h. 264. The problem is present. Sent logs to forum [at] nomachine [dot] com
August 17, 2022 at 12:17 #39738fra81ModeratorThere seems to be some issue with the drivers. Please try to edit the $HOME/.nx/config/player.cfg file and change the ‘Enable hardware accelerated decoding’ key to:
<option key=”Enable hardware accelerated decoding” value=”disabled” />
August 28, 2022 at 20:31 #39899MegaSlonicParticipantHello! Unfortunately this did not help. But the video drivers for Radeon came up and everything works again. Thank you for your cooperation.
August 29, 2022 at 10:57 #39912BritgirlKeymasterBut the video drivers for Radeon came up
Hi, do you mean that you’ve updated the drivers?
August 29, 2022 at 11:59 #39914MegaSlonicParticipantYes. Sorry for my bad English.
September 9, 2022 at 18:57 #40087LiftarenParticipant@ #39738
This works. I have used older Linux versions with Mesa 21.x since my last post. Today I tested a build with Mesa 22.0.5 and it did not work, but with the above suggestion of disabling hardware acceleration decoding it worked.
I set the value to “false” instead of “disabled”, but perhaps they are interchangeable. In the config file “false” was used for all other settings though.
-
AuthorPosts
This topic was marked as closed, you can't post.