Somewhat similar to bug 4725. If I start the client in non-fullscreen mode, convering parts of monitor 2, then maximize the client, and then switch to all-monitors fullscreen, the client will cover both monitors, but the server side session will only have 1 monitor. On this client, this happens both with client 4.0 and 4.1, and both with server 4.0 and 4.1. Occasionally, I also get errors of type: VNCSConnST: FramebufferUpdateRequest 2304x1024 at 0,0 exceeds framebuffer 1024x768
Similar problem when running a fullscreen vncviewer in a ThinLinc session: * The session is initially 1280x1024 (one screen) * tlclient requests 2 x 1600x1200 * ThinLinc session is correctly resized. * The vncviewer inside the ThinLinc session says: DesktopWindow: Requesting framebuffer resize from 1280x1024 to 1600x1200 DesktopWindow: 1 screen(s) 1681692777 (0x643c9869): 1600x1200+0+0 (flags 0x00000000) Viewport: Resizing framebuffer from 1280x1024 to 1600x1200 IOW, it will only detect a single screen.
(In reply to comment #1) > Similar problem when running a fullscreen vncviewer in a ThinLinc session: > > * The session is initially 1280x1024 (one screen) > > * tlclient requests 2 x 1600x1200 > > * ThinLinc session is correctly resized. > > * The vncviewer inside the ThinLinc session says: > > DesktopWindow: Requesting framebuffer resize from 1280x1024 to 1600x1200 > DesktopWindow: 1 screen(s) > 1681692777 (0x643c9869): 1600x1200+0+0 (flags > 0x00000000) > > Viewport: Resizing framebuffer from 1280x1024 to 1600x1200 > > > IOW, it will only detect a single screen. http://www.fltk.org/str.php?L3462
(In reply to comment #1) > Similar problem when running a fullscreen vncviewer in a ThinLinc session: > > * The session is initially 1280x1024 (one screen) > > * tlclient requests 2 x 1600x1200 > > * ThinLinc session is correctly resized. > > * The vncviewer inside the ThinLinc session says: > > DesktopWindow: Requesting framebuffer resize from 1280x1024 to 1600x1200 > DesktopWindow: 1 screen(s) > 1681692777 (0x643c9869): 1600x1200+0+0 (flags > 0x00000000) > > Viewport: Resizing framebuffer from 1280x1024 to 1600x1200 > > > IOW, it will only detect a single screen. Moved to bug 7156.
(In reply to comment #0) > Somewhat similar to bug 4725. If I start the client in non-fullscreen mode, > convering parts of monitor 2, then maximize the client, and then switch to > all-monitors fullscreen, the client will cover both monitors, but the server > side session will only have 1 monitor. On this client, this happens both with > client 4.0 and 4.1, and both with server 4.0 and 4.1. Occasionally, I also get > errors of type: > > VNCSConnST: FramebufferUpdateRequest 2304x1024 at 0,0 exceeds framebuffer > 1024x768 I cannot reproduce this problem on my workstation, not even with 4.1 server and 4.1 client. I could be that something has changed in the desktop environment. Also, I don't remember seeing this for a long time and we have no customer reports. Closing.
