This low resolution is used only when you first connect, but then you can change the resolution just by resizing the client window. My server is run with no -randr setting at all and just basic -geometry 1024x768. Beware that with TigerVNC server service starts automatically, silently, in the background, which I strongly detest as a possible security threat. If you want only viewer, then download only viewer, like vncviewer64-1.12.0.exe, that is just viewer without bundled VNC server. I tested TightVNC (open source), RealVNC (free version) and UltraVNC (open source) and had no luck with any of them, they provide useless auto-scaling at the best. So far I found that only TigerVNC is capable of auto-resolutioning. Downside is it also increases network bandwidth. Auto-resolutioning keeps image sharp at any size. And that is what I talk about earlier and that is what TigetVNC client is capable, providing server has matching functionality. What users typically want is real resolution change of the remote session. It decrease image quality significantly, if you stretch a lot. It just makes pixels bigger (or smaller) by stretching the output image. It works like zoom or looking glass in popular bitmap editors. This caling is virtually useless, unless you are visually impaired. Please don't confuse auto resolution change with image stretching, alternatively called auto-scaling. The remote desktop resolution, say KDE, follows your client window resolution smoothly.Ĭheck that "Resize remote session to the local window" is set. When you first connect to your server, the resolution is set to whatever is preset on the server side but you can easily change it just by resizing the client window to any resolution, any crazy, non-standard, ad-hoc resolution you want. No need to set anything anywhere, on the client or on the server. Dragging the window to any other resolution still does not work.With TigerVNC Windows VNC client (viewer) auto resolution works out of the box. The resize finally works, but only for the resolution 2560x1378.Click the "Maximize" button on the local client again to make the window fill the entire screen.Check that the custom resolution (2560x1378 when maximized) has been added to the list of resolutions (note: I have no idea how it got into this list, I'm guessing that by clicking the "Maximize" button earlier, and opening the Display Preferences, it somehow magically got appended to the list?).(you can keep clicking the "Maximize" button forever, no resize will happen).Click the "Maximize" button on the local client again to restore the window to the original size.No resize happens (just a black border is added to fill the space between the window edges and the remote desktop resolution).Click the "Maximize" button on the local client to make the window fill the entire screen.However, if I perform the following steps, I can get the window to resize: VNCServerST: no authenticated clients - stopping desktop SMsgWriter: raw bytes equivalent 3186184, compression ratio 66.132215 ** (gnome-volume-control-applet:22329): WARNING **: Connection failed, reconnecting.Ĭonnections: closed: 10.24.217.205::49944 (read: Connection reset by peer XserverDesktop: setScreenLayout: Could not find a matching mode ** (gnome-settings-daemon:22304): WARNING **: Connection failed, reconnecting. VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888 VNCSConnST: non-shared connection - closing clients SConnection: reading client initialisation VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |