Problems from iPad to Ubuntu

Forum / NoMachine for Mobile / Problems from iPad to Ubuntu

  • This topic has 6 replies, 2 voices, and was last updated 1 week ago by gyre.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #52221
    gyre
    Participant

    When connecting from an iPad pro to Ubuntu 22.04, I’m running into 2 problems.

    Firstly, when I make changes to the display settings on the ipad client, such as resolution, they only seem to take effect until the next time I start the client.  For example, i set 1280×1024 resolution, but the next time I run the client app it has reset to 3840×2160.

    Secondly, making any changes to the configuration and now keystrokes from an apple external keyboard don’t work.  I have to kill off the client and restart it, then it accepts keystrokes.

    Has anybody seen either of those problems… and perhaps have a workaround?

    Thanks!

    — gyre —

    #52259
    Tor
    Participant

    Hey there, thank you for your reports!

    For the first problem, can you try to enable the “use custom resolution” box and set the W 1280 and H 1024 resolution? This should work around the problem while we debug the reason for the ignored resize request.

    For the second problem, we’re aware of it and we implemented a fix that will be included in the incoming release. I don’t remember if there was a method to work around it, I’ll talk with the team and let you know.

    #52261
    gyre
    Participant

    Thanks for replying.

    Both using the slider for the resolution and setting a custom resolution seem to work for the current session only.

    However, disconnecting from the server or restarting the client will reset back to the much higher resolution.

    What’s slightly odd is there seems to be some interaction between the client and the server before this happens… the screen appears very briefly to have the preferred resolution… then it flickers and goes back to the higher resolution.  I can upload a video somewhere if that helps to illustrate, but it’s bigger than the 1024k allowed by this forum.

    Of course, I can’t use the current session with the preferred resolution due to not being able to type  🙂

    Thanks again.

    #52262
    Tor
    Participant

    Hi again. When the input stops working, you can disconnect and connect again the keyboard (for example turn it off/on or detach/attach the cable, if wired) to restore its functionality.
    I confirm the fix is ready to be released, so we’ll publish it as soon as the other major changes are ready.

    #52265
    Tor
    Participant

    What’s slightly odd is there seems to be some interaction between the client and the server before this happens… the screen appears very briefly to have the preferred resolution… then it flickers and goes back to the higher resolution. I can upload a video somewhere if that helps to illustrate, but it’s bigger than the 1024k allowed by this forum.

    Oh, I see, that means the client tries to set the resolution but Ubuntu is changing it back to the previous one. Are you connecting to the Ubuntu physical desktop or creating a new virtual desktop?
    If you have the file .config/monitors.xml in your home directory, can you try to rename it, logout, login and try to check if Ubuntu keeps the custom resolution when the client connects?

    #52267
    gyre
    Participant

    Thank you for replying.

    Yes, disconnecting my keyboard and reconnecting it does allow me to type.  Thank you.

    I’ve moved ~/.config/monitors.xml elsewhere and logged in and out.  The resolution is still reset to a much larger value.

    #52268
    gyre
    Participant

    Forgot to say… this was to the physical desktop.  But I also have an xrdp session running which I can connect to too… and this also doesn’t keep my resolution settings between connections.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Please login .