Forum / NoMachine for Linux / Player exits suddenly when connecting on Linux Mint 20.2 (Ubuntu 20.04 LTS)
Tagged: crash
- This topic has 6 replies, 2 voices, and was last updated 3 years, 3 months ago by Britgirl.
-
AuthorPosts
-
July 23, 2021 at 09:17 #34558joshwiselyParticipant
I recently tried to get NoMachine (free) up and running between Linux 2 desktops. Simple product install. I see the port open on the remote host. The server is auto-discovered just fine. But when I actually connect to the server, the client immediately crashes.
When I look at the core file that’s generated, I see nxplayer.bin is crashing due to a segmentation fault.
How can I investigate this further? Can someone look at the core file and point me in the right direction?
I have logs gathered and the core file available.
July 26, 2021 at 08:02 #34571BritgirlKeymasterHi, can you send us the logs that you gathered to forum[at]nomachine[dot]com. Ideally, we’d also need the stackdump from the core file that you have. Put the title of the topic as the subject of your email. Thanks!
July 27, 2021 at 03:41 #34593joshwiselyParticipantSent.
July 28, 2021 at 17:16 #34650BritgirlKeymasterHi Josh, we got your email and link. Thank you.
August 3, 2021 at 15:34 #34705BritgirlKeymasterFrom the logs it appears va-api is broken and is probably causing the crash of the player. Usually such problems are inner VA-API libs/drivers problems occurring with some specific system configuration, and are not related to NoMachine code.
Try changing this key in player.cfg:
“Enable hardware accelerated decoding”
to:
“disabled” (not to “false”).
Does this help?
August 4, 2021 at 08:35 #34709joshwiselyParticipantHi Britgirl,
Yes, that worked.
Thanks for the help!
Is there documentation about what the other settings in that config file do?
Feature request: Add functionality in the GUI to edit settings like this for the player.
August 4, 2021 at 08:46 #34713BritgirlKeymasterIn a “normal” situation you would disable “Enable hardware accelerated decoding” during the connection, via the connection menu. So the user can already edit the settings like this for the player. But in your case this would not have had any effect because the crash seems to happen before the session is actually established.
You might want to take a look at the connection menu guide for explanations on what the various check boxes do. In your case, the guide for the menu panel on Linux is here https://www.nomachine.com/DT10R00167. Go to section 5.8.
Depending on your OS, they are all linked in the Configuration section here: https://www.nomachine.com/all-documents. You will find a lot of useful information there.
There is an article in our KB, linked from the Documents page, about the most common cfg settings.
The most frequently asked options for pre-configuring the client and the session behavior
https://knowledgebase.nomachine.com/DT11R00186 -
AuthorPosts
This topic was marked as solved, you can't post.