Not sure why the BadMatch error is occurring, but the other error is 
from TurboVNC.  It means that the viewer you are using doesn't support 
the RFB "NewFBSize" or "ExtendedDesktopSize" messages.  Actually, to be 
more exact, it means that *one* of the connected viewers doesn't support 
those messages.  When the desktop size changes on the server, all 
connected viewers must be able to handle the desktop resize message. 
Otherwise, trying to send the message to a viewer that can't handle it 
might cause the viewer to crash, and minimally it would muck up the 
display and mouse interaction with that viewer, since the viewer would 
still think it was operating at the old resolution.  The only way to 
change the resolution when using an older viewer is to disconnect, 
change the resolution via a remote shell ('xrandr --display :1 
1920x1200', for instance), and reconnect.

NewFBSize is supported by all Windows flavors of the TightVNC and 
TurboVNC Viewer.  ExtendedDesktopSize is supported by the TurboVNC 1.2.x 
Java viewer, by both Java and native flavors of the TurboVNC 2.0 viewer, 
and by both Java and native flavors of the TigerVNC 1.2.x (and later) 
viewer.

If you are using one of those newer viewers and are still getting that 
error message, then apparently there's a bug in the TurboVNC Server.

As to why you're getting 3200x1800 as the default resolution, it might 
be related.  3200x1800 is the second resolution reported by TurboVNC to 
X RANDR, so it's possible that, for whatever reason, KDE is trying to 
use Resolution 0 (the "custom" resolution specified with -geometry), 
failing, and dropping back to Resolution 1 (3200x1800.)  I am not sure 
why that would happen, though.

-- 


On 6/18/15 1:52 PM, Craig Ruff wrote:
> ​I found messages in the vnc session log that at least shows why, under
> my KDE session, the resize attempt does not take effect:
>
> 18/06/2015 12:47:17 ERROR: Not resizing desktop because one or more
> clients doesn't support it.
> X Error: BadMatch (invalid parameter attributes) 8
>    Extension:    144 (RANDR)
>    Minor opcode: 7 (RRSetScreenSize)
>    Resource id:  0x6a
> 18/06/2015 12:47:17 ERROR: Not resizing desktop because one or more
> clients doesn't support it.
> X Error: BadValue (integer parameter out of range for operation) 2
>    Extension:    144 (RANDR)
>    Minor opcode: 7 (RRSetScreenSize)
>    Resource id:  0x0
>
> ​I still haven't had time to track down where that very large default
> resolution of ​3200x1800 comes from the first time vncserver is started.

------------------------------------------------------------------------------
_______________________________________________
TurboVNC-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/turbovnc-users

Reply via email to