Forum Replies Created
-
AuthorPosts
-
Britgirl
KeymasterWe got the logs thank you and will update the topic soon 🙂
Britgirl
KeymasterAdditional details which are also asked in the other topic are require as well:
Which desktop environment and desktop manager are being used?
Is it a physical machine or a virtual?
Is Wayland being used for login window or/and desktop on the Xubuntu host?And you confirm that uncommenting ‘WaylandEnable=false’ on /etc/gdm3/custom.conf didn’t work?
Britgirl
KeymasterWhich topic is marked as solved? I thought maybe a topic that you submitted previously but you haven’t submitted any topics prior to this one. Please provide a link so we can understand what issue you are referring to.
What Linux distro are you connecting to, what version? Is Wayland running there or Xorg? You say that on NoMachine version 6.11 you didn’t have this issue, have I understood correctly?
November 19, 2020 at 09:43 in reply to: NoMachine connection fails first attempt, second attempt always successful #30446Britgirl
KeymasterWe haven’t been able to reproduce this at all. Please send us a screenshot from the Advanced Power Settings plus logs from the affected Windows server host. Please see here for instructions on where to find logs.
https://www.nomachine.com/AR10K00697
Submit everything to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!
Britgirl
KeymasterNovember 18, 2020 at 10:49 in reply to: Support for arm64e architecture on macOS 11 (Big Sur) #30428Britgirl
KeymasterThanks for taking the time to report this. Support for macOS on ARM isn’t available yet, although we are currently working on NoMachine compatibility with this architecture 😉
Britgirl
KeymasterSway desktop is not detected and as a result NoMachine can’t attach to it to display it (hence you see nothing).
A better workaround would be to put the command you are using in the node.cfg file instead. That way it would be automatic and you wouldn’t have to launch ‘vncviewer -fullscreen localhost:0’ every time you connect.
Try defining it in DefaultDesktopCommand in the NoMachine’s node configuration file.
November 17, 2020 at 13:07 in reply to: Connecting to 4k screen causes crashes and very slow reaction #30414Britgirl
KeymasterThe feature that you are referring to hasn’t been implemented yet 🙂 https://www.nomachine.com/FR09Q03870
At least I think that is what you are referring to (your topic https://forums.nomachine.com/topic/errors-with-libnxdi-dll from a few months back).
We didn’t change anything in particular that would change what you could or couldn’t do in the previous release: connecting to a computer with 4k monitor was already possible. But, your earlier post suggests you have multiple 4k monitors. Did you lower your resolution perhaps?
Britgirl
KeymasterThis is planned:
Switching between the view-only and interactive mode in session run-time
https://www.nomachine.com/FR12L02848Please sign up to the ‘notify me’ utility that you can find on the webpage linked above.
Britgirl
KeymasterI have tried with SSH connection too
Do you mean that you tried a vanilla SSH connection or a NoMachine SSH connection?
If the second, check the logs for errors. The NoMachine /var/log folder on Mac is:
/Library/Application Support/NoMachine/var/log
Britgirl
KeymasterThe excerpt you posted seems to show it is not a NoMachine problem at all.
November 16, 2020 at 13:35 in reply to: NoMachine in KDE system tray icon context menu broken #30392Britgirl
KeymasterThis topic has been closed because there was no further feedback from the author. Please let us know if you are still experiencing the issue.
November 13, 2020 at 14:53 in reply to: 5 seconds lag when running Kubuntu with built in window server #30355Britgirl
Keymaster@andro, Manjaro is Arch-based if I am not mistaken. Although running NoMachine on Arch isn’t officially supported, we are investigating multiple issues regarding this particular distro (you can search the forums if you like). We’ll update the appropriate topics with our findings.
Regarding Kubuntu, it’s headless, so this may be of interest to you.
How to solve black screen on headless machines
https://www.nomachine.com/AR03P00973Britgirl
KeymasterFirst let me clarify that NoMachine does not support connecting TO Android. The NoMachine for Android app is for connecting from Android tablets to a computer which has NoMachine installed. Steps to connect should be: 1) install on PC, note down IP addresses as per getting started guide; 2) install app on Android tablet; 3) create connection on Android tablet to connect to PC mentioned in steps 1 and 2.
Connecting to localhost essentially means connecting to yourself (so client and server are the same computer), i.e you install NM on a computer and insert its IP address for LAN that appears in Welcome screen (like you did) in the connection creation procedure. It’s a good test to see if NoMachine installed ok and is working. In your case, something is wrong with the authentication procedure.
Apologies for not including the link from our knowledge base. If you try to connect from Android to this Windows PC and you still get the same authentication issue, we will need to see the logs from the Windows host. Large attachments aren’t accepted here so any log files can be sent directly to forum[at]nomachine[dot]com making sure you insert the title of your topic in the subject. Instructions for logs are here:
Britgirl
KeymasterCan you submit screenshots of what you are seeing during the connection process?
-
AuthorPosts