mattspod

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • mattspod
    Participant

    Further update. Did get it working for a few mins, had to full screen then unfull screen a few times, btw this can also happen on a windows host too if you don’t go full screen before connecting – sometimes. It’s looking promising, glitchy the combo of resize guest and full screen from Mac OS X, but it’s getting there, will revisit a few releases into 9.

    mattspod
    Participant

    Update. Turning off 3d acceleration for the vmware workstation guest (that’s acting as the NX host) does load up the desktop. The problem is from macOS x client with 1:1 resize guest and full screen mode it chooses some weird resolution and the cursor isn’t correlated. Connecting to a windows nx host with same resize guest and full screen mode work, which leads me to believe it’s still a KDE wayland compatibility issue.

    mattspod
    Participant

    Still a fail. Brand new fedora install. KDE latest. NoMachine installed. Wayland obviously.

     

    Error: connection reset by peer

    in reply to: Support for Fedora Asahi (Aarm64) #48138
    mattspod
    Participant

    Does the Wayland disclaimer apply if using the ARM device as the client/player only, and remoting into a amd64 KDE 6.0.4 wayland?   Fedora Asahi explicitly doesn’t support X.

    Somewhat related, is the move to the new Intel APIs still coming in the next release?

     

     

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