Tor

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 593 total)
  • Author
    Posts
  • Tor
    Participant

    I’d like to send you a library that adds some checks in the routines handling the system clipboard, but I’d need to know if you use the 32 or 64 bits version of the software (x86 or x64). Please send an e-mail to forum[at]nomachine[dot]com and use the title of this post as subject, we’ll answer by sending a link to download the library.

    Tor
    Participant

    Hi. We’ve no open issues about copy&paste causing application freezes, so I’m going to ask you some questions to better outline the problem and confirm it.
    When you have this application freeze issue:
    – Do you have more than one Player running, connected to multiple desktops?
    – Is the main Player window, showing the list of machines, freezing as well?
    – Open Task Manager and kill one NoMachine Player process at a time. Do the other Player’s start working correctly?
    – When you can manage to start a new NoMachine Player, if you shutdown temporarily the NoMachine server do you see other processes running in Task Manager? How are they called? If you kill them, can you start correctly a new NoMachine Player?

    Also, please send the file %ALLUSERSPROFILE%\NoMachine\var\log\nxtrace.log, if it does exist, to forum[at]nomachine[dot]com.
    Thanks.

    Tor
    Participant

    Happy to know it works!
    If you want to automatically run the application, you can look for an automation app in the store and configure a macro to open an NXS file with NoMachine. You can select the trigger (device boot, screen unlock, wifi state change, button presses, etc) and the action to execute (in our case “open file”).
    I’ve tried a couple of simple apps but I didn’t manage to start the application correctly after the device boots up. However I tried to run it when the screen unlocks, and it worked beautifully. Nice idea, thanks for sharing it!

    Tor
    Participant

    You can use the intent, try this:

    adb shell am start -a android.intent.action.VIEW -d file:///storage/emulated/0/Android/data/com.nomachine.nxplayer/files/NoMachine/Connection\\ name.nxs -t application/octet-stream

    Change the file “Connection name.nxs” in the example to the name you need, and remember to double escape spaces. You could also need to change the path of the NXS file, usually they are saved in the scoped storage, but you could have also a /sdcard/NoMachine directory.
    The first time you’ll do it, the system will show you a list of applications compatible with that mime type. Select NoMachine and toggle “Remember my choice”.
    When the application starts check the “Don’t show this message again” switch in the welcome panels, so the next time the connection will start immediately.

    Tor
    Participant

    Hi. In your old post you said “the remote window and the client application window are both frozen”. Do you mean that both the window showing the remote desktop, and the one listing the existing connections, are freezing?

    Tor
    Participant

    When typing in a Raspberry Pi terminal window with the Apple Magic Keyboard, we have the following problems

    Can you please tell the distribution and keyboard layout you’re using on Raspberry, and the keyboard language set on iPad? We’re preparing a release including the fix for this problem, but we’d like to be sure it addresses also the issues you’re experiencing.

    in reply to: Attempting to reconnect #43577
    Tor
    Participant

    The NXS connection files store all your preferences and they are saved by default in the Documents/NoMachine directory. I noticed my post was corrupted for some reasons and the last line was not visible. Read it again to see the option to change.

    As for the command line option, you can use it by starting the following command in a terminal:
    /usr/NX/bin/nxplayer --exit-always
    Since you’re configuring a kiosk you can edit the script /usr/NX/bin/nxplayer and add the option --exit-always to the last line:
    exec "$NX_SYSTEM/bin/nxplayer.bin" --exit-always "$@"

    in reply to: Attempting to reconnect #43568
    Tor
    Participant

    The client can be configured to ignore errors on disconnection, and that together with disabling the automatic reconnection should do what you want.

    You can test these ways:

    1. Run the player with the --exit-always command line option
    2. Edit the NXS connection file, and set the value “always” to the following key:
    <option key="Close the client application when a single session terminates" value="always" />

    in reply to: Drag and drop not working between 2 Macs? #43507
    Tor
    Participant

    Hi. Can you confirm the drop on the window correctly transfers the file to the server? If it is so, and the problem is only occurring when you drag a file out to download it, please try to use all four sides of the client window, and try also to slowly cross the window border. We’re running some tests in our labs, results of your tests would be helpful too. Thanks.

    in reply to: Duplicate cursors appear when I drag something #43381
    Tor
    Participant

    Hi. The drag operation showing the remote cursor is a feature that, on the mobile application, has a slightly different behaviour compared to desktop application. While I perfectly understand your proposal and I agree, one of our policies forces us to have the same solution on all platforms, when deciding how to deal with problems or features. In this particular case we could hide the local cursor on Android, but not on iOS… However as you said the Android cursor is not very nice, so we’re still discussing all possible pros and cons of every solution.

    I know this is not the solution you’re looking for, but you could disable the server side cursor when doing the drag operation by editing the node.cfg file on the server and by setting the following key:

    DisplayServerExtraOptions “-nocursorlock”

    Thank you for your feedback!

    in reply to: Arrow and space keys don’t work in version 8.4.2 #43237
    Tor
    Participant

    We identified the issue and rolled out a new version for an internal testing, so far everything is working as expected. We’re implementing other changes too, so I don’t expect a new version to be published before next week.


    @hpb
    can you confirm the ‘space’ works correctly with other 3rd party apps, please? Compared to other keys, the ‘space’ is received as-is and there is nothing special to do to forward it.


    @NebulaBC
    the problem is a bit more complex, caused by an internal condition clearing out a bit in a mask, and bypassing the definition of the key commands needed by the responder object. I’m sorry we didn’t notice it during our tests.

    There is a workaround you could try. The bug is not triggered if you avoid to activate input fields before the client connects to the remote desktop, so store username and password in the connection and don’t tap any input fields until you see the desktop. Let me know if this helps (on one of our devices the workaround didn’t… work around! 🙂 We’re still analyzing the reason).

    in reply to: Arrow and space keys don’t work in version 8.4.2 #43184
    Tor
    Participant

    Perfectly clear, thanks. We’re doing some checks in our labs, I’ll update this thread soon.

    in reply to: Arrow and space keys don’t work in version 8.4.2 #43168
    Tor
    Participant

    Hi! What is your iOS device model? Do you use the virtual keyboard, or an hardware keyboard connected to the device through bluetooth?

    in reply to: NoMachine icon is barely visible on light theme #42728
    Tor
    Participant

    Thank you for the report, in the next release we’ll improve the tray icon selection on Mint 21.
    You can work around the issue by executing the following commands in a Terminal window:

    cd /usr/NX/share/images
    for i in tray-dark-*; do sudo cp "$i" "$i.backup"; done
    for i in tray-light-*; do sudo cp "$i" "${i//light/dark}"; done

    If you want to restore the backed up icons, run this:

    for i in tray-dark-*.backup; do sudo mv "$i" "${i//.backup/}"; done

    in reply to: Some keys and mouse display not working on Ventura #41335
    Tor
    Participant

    Hi. Can you update your client to the new 8.2 version and try again? We’ve solved some general issues occurring on Ventura, it would be good to know if those fixes help with your issue.

Viewing 15 posts - 16 through 30 (of 593 total)