After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 359294 - vino does not respond to changes in desktop resolution
vino does not respond to changes in desktop resolution
Status: RESOLVED DUPLICATE of bug 357778
Product: vino
Classification: Applications
Component: Server
2.17.x
Other All
: Normal normal
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-10-03 14:39 UTC by madcap
Modified: 2007-02-02 14:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description madcap 2006-10-03 14:39:02 UTC
Please describe the problem:
I had vino enabled at login time. After logging into gnome, I changed my resolution from 1280x720 to 1920x1080. The next time I tried to vnc in, my desktop resolution was at 1920x1080, but the size of the vncviewer window was only 1280x720.

Steps to reproduce:
1. Enable the vino server (Preferences->Remote Desktop)
2. Log in at one resolution and then alter your desktop resolution via Preferences->Screen Resolution. 
3. From another display, load up your desktop in vncviewer.


Actual results:
The size of the vncviewer window will be as if the desktop was at the old resolution, although the displayed screen is actually at the newer resolution (not sure what happens if the new resolution is smaller than the old, but I see another bug relating to crashing when changing resolution...)

Expected results:
vino should notice that the resolution was changed and update accordingly. Note I'm not talking about live updates (like I changed the resolution while in vncviewer, although that would be nice too), but it should at least display correctly the next time a vnc connection is made.

Does this happen every time?
I believe so.

Other information:
The workaround is to disable vnc from preferences and then re-enable it.
Comment 1 Jonh Wendell 2007-01-30 15:16:30 UTC
I'm sorry, i have marked this one as confirmed, my mistake.

By the way, this one is very similar to bug 357778. My guess is that is a duplicate, but we only can confirm when we find out where the bug is :)
Comment 2 Jonh Wendell 2007-02-02 14:37:11 UTC
OK, really it's a duplicate of bug 357778, which was fixed today.

*** This bug has been marked as a duplicate of 357778 ***