full screen resolution problem

[Henrique Martins]

If on my laptop I run vncviewer into my (zaphod heads) dual
screen computer I get the desktop of the first screen (never
found out how to get to the second one) using tigernvnc's
server-module.

The resolution of my laptop is 1600x900 (yuck, need to get a
higher vertical resolution laptop one of these days), the
remote screen is 1920x1080.

I run fvwm with multiple pages/desktops on each screen, and
hitting the edge warps me to the "next" one, over VNC that
seems to turn hyperdrive on and I end up landing in a random
desktop/page. To avoid this I press F8, enable Full Screen
mode, which enables me to send my navigation key and mouse
bindings to the remote screen and get to where I want to.

Now, if I forget to disable Full Screen mode before exiting
vncviewer and go back to the console, this one seems to be
in some strange resolution with large windows/fonts, etc,
and I can't seem to get it back to "normal".

Is there a way out of this?
All of this on Fedora 20, fully updated, latest tigervnc.

-- Henrique

[Pierre Ossman]

On Wed, 05 Nov 2014 11:33:04 -0800,
Henrique Martins wrote:

> If on my laptop I run vncviewer into my (zaphod heads) dual
> screen computer I get the desktop of the first screen (never
> found out how to get to the second one) using tigernvnc's
> server-module.
>

The second screen shows up on the next port number. So if your first
screen is at 5900, then your second will be at 5901. Note that this is
not a setup we test particularly often.

> The resolution of my laptop is 1600x900 (yuck, need to get a
> higher vertical resolution laptop one of these days), the
> remote screen is 1920x1080.
>
> I run fvwm with multiple pages/desktops on each screen, and
> hitting the edge warps me to the "next" one, over VNC that
> seems to turn hyperdrive on and I end up landing in a random
> desktop/page. To avoid this I press F8, enable Full Screen
> mode, which enables me to send my navigation key and mouse
> bindings to the remote screen and get to where I want to.
>
> Now, if I forget to disable Full Screen mode before exiting
> vncviewer and go back to the console, this one seems to be
> in some strange resolution with large windows/fonts, etc,
> and I can't seem to get it back to "normal".
>
> Is there a way out of this?

Sounds like you are simply resizing your session to the laptop's
display. So it should be a matter of opening your screen settings (or
use xrandr) and changing back to 1920x1080.

I'm afraid there's no way to turn this off from the server side, but
you can tell the client to not try to resize things by disabling
"Resize remote session to the local window".

Rgds
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600 https://plus.google.com/+CendioThinLinc

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[Henrique Martins]

>> If on my laptop I run vncviewer into my (zaphod heads) dual
>> screen computer I get the desktop of the first screen

> The second screen shows up on the next port number. So if
> your first screen is at 5900, then your second will be at
> 5901.

I don't think so. The second display, not screen shows up

on the next port number.

I do run two displays, :0 attached to my dual monitor
console, and :1, a virtual display on a vncserver, and they
do show at 5900 and 5901. However with a zaphod heads
configuration, my first display has two independent screens,
:0.0 and :0.1. I have yet to find out a way to see the
second screen on display 0, i.e. :0.1, with vnc.

> Sounds like you are simply resizing your session to the
> laptop's display. So it should be a matter of opening your
> screen settings (or use xrandr) and changing back to
> 1920x1080.

There are no "screen settings" with xdm/xinit/fvwm :-) but
yes I can use xrandr to get back to my original
resolution.

I don't think I'm explicitly resizing my session to my
desktop screen setting. Something changed in tigervnc,
sometime ago, as I used to get a viewer window with
scrollbars that allowed me to navigate the remote desktop,
and/or the windows would pan when I hit the edge, but now I
don't get the scrollbars and thus need to go full screen to
navigate.

> I'm afraid there's no way to turn this off from the server
> side, but you can tell the client to not try to resize
> things by disabling "Resize remote session to the local
> window".

I don't think I have that set, as when I connect the full
window is not there. It's only when I go "full screen" that
the resizing happens.

-- Henrique

[Pierre Ossman]

On Mon, 10 Nov 2014 17:43:04 -0800,
Henrique Martins wrote:

>
> I don't think so. The second display, not screen shows up
> on the next port number.
>
> I do run two displays, :0 attached to my dual monitor
> console, and :1, a virtual display on a vncserver, and they
> do show at 5900 and 5901. However with a zaphod heads
> configuration, my first display has two independent screens,
> :0.0 and :0.1. I have yet to find out a way to see the
> second screen on display 0, i.e. :0.1, with vnc.
>

Sorry. I misread the code. It should be at port 6900.

>
> I don't think I'm explicitly resizing my session to my
> desktop screen setting. Something changed in tigervnc,
> sometime ago, as I used to get a viewer window with
> scrollbars that allowed me to navigate the remote desktop,
> and/or the windows would pan when I hit the edge, but now I
> don't get the scrollbars and thus need to go full screen to
> navigate.
>

The scroll bars should still be there, so that's some kind of bug.

Are you using Fedora's TigerVNC, or ours? If it's theirs, could you
test ours? Please also test the nightly build.

If that's still broken, please press F8 and click "Connection info".
What does the size line there say?

> > I'm afraid there's no way to turn this off from the server
> > side, but you can tell the client to not try to resize
> > things by disabling "Resize remote session to the local
> > window".
>
> I don't think I have that set, as when I connect the full
> window is not there. It's only when I go "full screen" that
> the resizing happens.
>

It doesn't resize on connect under the default settings. A bit
confusing and probably something we should change...

[Henrique Martins]

>> I don't think so. The second display, not screen shows up
>> on the next port number.

> Sorry. I misread the code. It should be at port 6900.

There is no vnc on port 6900. I have vnc at 5900 (:0.0) and
5901 (:1), then X11 at 6000 and 6001 (ssh X11 forwarding),
but nothing at 6900.

However, this maybe a configuration problem. My
configuration at: /etc/X11/xorg.conf.d/10-libvnc.conf
has:

Section "Module"
Load "vnc"
EndSection

Section "Screen"
Identifier "Screen0"
Option "SecurityTypes" "VeNCrypt,TLSPlain"
Option "PlainUsers" "<my-username>"
Option "pam_service" "login"
EndSection

where I believe I use the "Screen" section just to change
SecurityTypes, not to tell vnc where to run. If I add a
second section with Screen1, zaphod heads breaks and I
don't get a :0.0 and :0.1, just :0 spanning the two
monitors..

> Are you using Fedora's TigerVNC, or ours? If it's theirs,
> could you test ours? Please also test the nightly build.

I'm using latest available from Fedora
tigervnc-1.3.0-14.fc20.x86_64
Not sure if I want to go to the trouble of compiling
tigervnc just for this. I did pull binaries from bintray,
where there is a libvnc.a instead of a libvnc.so, but that
one doesn't load (maybe because I didn't override the built
in mesa dri lib with the one in bintray.)

-- Henrique

[Henrique Martins]

> Please also test the nightly build.

Oh wait :-) Are you referring to these?
http://tigervnc.sourceforge.net/tiger.nightly/
I was only looking at git.
But still there doesn't seem to be a Fedora 19+/RHEL-7
compatible build, i.e. systemd based.

-- Henrique

[Pierre Ossman]

On Wed, 12 Nov 2014 05:59:08 -0800,
Henrique Martins wrote:

> >> I don't think so. The second display, not screen shows up
> >> on the next port number.
> > Sorry. I misread the code. It should be at port 6900.
>
> There is no vnc on port 6900. I have vnc at 5900 (:0.0) and
> 5901 (:1), then X11 at 6000 and 6001 (ssh X11 forwarding),
> but nothing at 6900.
>

I'm mostly guessing based on what the code says, so I'm afraid I'm out
of ideas. As I said, zaphod isn't something that's particularly well
tested.

> > Are you using Fedora's TigerVNC, or ours? If it's theirs,
> > could you test ours? Please also test the nightly build.
>
> I'm using latest available from Fedora
> tigervnc-1.3.0-14.fc20.x86_64
> Not sure if I want to go to the trouble of compiling
> tigervnc just for this. I did pull binaries from bintray,
> where there is a libvnc.a instead of a libvnc.so, but that
> one doesn't load (maybe because I didn't override the built
> in mesa dri lib with the one in bintray.)

Sorry, I was a bit unclear. I'd like you to test the client from our
builds. You can keep the server portions from Fedora.

And we don't have any Fedora RPMs, so you'll have to use the tar.gz
ones.

Gds

[Pierre Ossman]

On Wed, 12 Nov 2014 05:59:08 -0800,
Henrique Martins wrote:

> Not sure if I want to go to the trouble of compiling
> tigervnc just for this. I did pull binaries from bintray,
> where there is a libvnc.a instead of a libvnc.so, but that
> one doesn't load (maybe because I didn't override the built
> in mesa dri lib with the one in bintray.)

Brian, there shouldn't be an libvnc.a in any package. Can you have a
look at this?

[Brian Hinz]

On Thursday, November 13, 2014, Pierre Ossman <oss...@cendio.se> wrote:

On Wed, 12 Nov 2014 05:59:08 -0800,
Henrique Martins wrote:

> Not sure if I want to go to the trouble of compiling
> tigervnc just for this.  I did pull binaries from bintray,
> where there is a libvnc.a instead of a libvnc.so, but that
> one doesn't load (maybe because I didn't override the built
> in mesa dri lib with the one in bintray.)

Brian, there shouldn't be an libvnc.a in any package. Can you have a
look at this?

You're right, this came up before and removing it slipped off my to-do list.  I'll remove it tonight.

-brian 

--
Sent from Gmail Mobile

[Henrique Martins]

> Sorry, I was a bit unclear. I'd like you to test the
> client from our builds. You can keep the server portions
> from Fedora.

I think I've tried both the latest official builds and
nightlies from tigervnc (i.e. not from Fedora) and the
behavior seems to be that when coming from a windows box the
viewer gets scrollbars, when coming from a linux box, the
viewer doesn't get scrollbars.

Connection info shows:
Desktop name: x11
Host: xxxx port: 5900
Size: 1920 x 1080
Pixel format: depth 24 (32bpp) little-endian rgb888
(server default depth 24 (32bpp) little-endian rgb888
Request encoding: Tight
Last speed encoding: Tight
Line speed estimate: (variable) kbit/s
Protocol version: 3.8
Security method: TLSPlain

-- Henrique

[Pierre Ossman]

On Fri, 14 Nov 2014 11:13:27 -0800,
Henrique Martins wrote:

> > Sorry, I was a bit unclear. I'd like you to test the
> > client from our builds. You can keep the server portions
> > from Fedora.
>
> I think I've tried both the latest official builds and
> nightlies from tigervnc (i.e. not from Fedora) and the
> behavior seems to be that when coming from a windows box the
> viewer gets scrollbars, when coming from a linux box, the
> viewer doesn't get scrollbars.
>
> Connection info shows:
> Desktop name: x11
> Host: xxxx port: 5900
> Size: 1920 x 1080

You should definitely be getting scroll bars at this point.

Could you try starting the client with -Log *:stderr:100 and attach the
log output for us here?

Rgds

[Henrique Martins]

me> Connection info shows:
me> Desktop name: x11
me> Host: xxxx port: 5900
me> Size: 1920 x 1080

pierre> You should definitely be getting scroll bars at this
pierre> point.
pierre> Could you try starting the client with -Log
pierre> *:stderr:100 and attach the log output for us here?

Attaching three logs, one from the fedora latest rpm, one
from tigervnc's nightly (of a few days back) and one from a
windows machine. Note that I had to strip all the RawTLS
noise from the fedora log.

Can't really see anything there that will help you, with the
exception, maybe, that the linux versions of vncviewer are
using XImage.

-- Henrique

[Pierre Ossman]

Those logs at least tell us that there are no attempts to adjust
things, from either side.

Could you share with us your ~/.vnc/default.tigervnc and command line
so we can see what settings the client is using?

What desktop environment are you using on the client? Could it be a
simple case of the viewer window simply extending beyond your visible
screen?

[Henrique Martins]

> Could you share with us your ~/.vnc/default.tigervnc and
> command line so we can see what settings the client is
> using?

I don't have a ~/.vnc/default.tigervnc file.
Command line is simply
vncviewer machine:0
though sometimes it is
vncviewer localhost::port
when it goes over a ssh tunnel, but it behaves the same
either way.

> What desktop environment are you using on the client?

I don't have a "desktop environment", I use xdm/fvwm.

> Could it be a simple case of the viewer window simply
> extending beyond your visible screen?

They extend beyond visible screen, and I can move it around
to show what is not visible using fvwm, but it would be nice
if the scrollbars where there, or that, in full screen mode,
it would pan when hitting the edges.

When I come from the same laptop, on windows, the scrollbars
are there, and the client screen/size is the same.

-- Henrique

[Pierre Ossman]

On Wed, 03 Dec 2014 07:48:07 -0800,
Henrique Martins wrote:

> > Could it be a simple case of the viewer window simply
> > extending beyond your visible screen?
>
> They extend beyond visible screen, and I can move it around
> to show what is not visible using fvwm, but it would be nice
> if the scrollbars where there,

Well, in that case it's really a bug/feature of your window manager. We
simply request the window size we need and it's up to the window
manager if it should be reduced to the monitor size or not. I'm not
familiar with fvwm, but maximising a window usually restricts it to the
current monitor. So that might be a solution for you?

> or that, in full screen mode,
> it would pan when hitting the edges.

Oh, I thought it was just the scroll bars that were broken? Full screen
should pan around when you hit the edges. Could it be the window
manager again that doesn't resize the window properly? Does the bug
go away if you use another window manager?