According to Pierre, some DEs restores the screen resolution at login. This might be useful on a fat workstation, so that different users can have different resolutions, but this is most likely not what a ThinLinc user want. We could consider adding some mechanism to prevent this from happening, such as renaming/deleting the settings file.
The settings file is called .config/monitors.xml. I experienced this problem on my SLED11 testing machine, after trying to use gnome-display-properties. See bug 3094. I think this bug is important to fix, moving to 3.0.1.
Also see bug 4160.
Gnome 3 seems to have added even more magic in this area. Without any configuration at all, Gnome 3 on Fedora 19 (alpha) will try to resize things to 1920x1200. Not sure where it is getting this size from. It is the largest resolution in Xvnc's default list, so it might be that. It is probably trying to be clever and use the display's "native" resolution, and using the largest one when it cannot find an EDID. There are some settings under "org.gnome.settings-daemon.plugins.xrandr" in dconf that might influence this.
Hi have a fix I use for this issue it is not the cleanest but it works with two files /opt/thinlinc/etc/sessionreconnect.d/thinlinc-res-fix #!/bin/bash g=$(echo `tl-session-param fbsize_x`x`tl-session-param fbsize_y`) if [ -n "$g" ]; then m=$(cvt $(echo $g | tr x ' ') | grep ^Modeline | cut -f 2- -d ' ' | tr -d '"') s=$(xrandr | grep connected | cut -f 1 -d ' ') n=$(echo $m | cut -f 1 -d ' ') xrandr --newmode ${m[@]} xrandr --addmode $s $n xrandr -s $n > ~/.thinlinc/xrandr-fix.log fi /etc/xdg/autostart/thinlinc-res-fix.desktop [Desktop Entry] Name=Thinlinc Resolution Fix Comment=Fix Screen Resolution Gnome3 Session Icon=system-run Exec=/opt/thinlinc/etc/sessionreconnect.d/thinlinc-res-fix Terminal=false Type=Application Categories= OnlyShowIn=GNOME; X-GNOME-Autostart-Delay=3
Unity also does this on login.
This seems to have to do with us not listing any preferred modes: https://github.com/TigerVNC/tigervnc/pull/57
There are two separate issues here. Moving the preferred mode portions to bug 5600. This bug is now about the general case and/or when the user has an explicit setting.
Reported to GNOME to see if anything long term can be done: https://gitlab.gnome.org/GNOME/mutter/issues/120
If we go the route of delegating this completely to the client then we could possibly solve this by not adding any alternative modes to the outputs in Xvnc. This would mean that using xrandr (or similar) in the session would also stop working though.
