Bug 60176 - Can't specify geometry for VNC server
Summary: Can't specify geometry for VNC server
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: vnc
Version: beta1
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: David Lawrence
: 68971 86391 97879 120511 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2002-02-21 11:33 UTC by Bernd Bartmann
Modified: 2007-04-18 16:40 UTC (History)
9 users (show)

Fixed In Version: 4.0-1.beta4.11
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2004-04-14 16:17:17 UTC

Attachments (Terms of Use)

Description Bernd Bartmann 2002-02-21 11:33:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461)

Description of problem:
There is no way to specify the geometry for a VNC server 
in /etc/sysconfig/vncservers

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. setup a new VNC server in /etc/sysconfig/vncservers
2. try to specify a different geometry setting for this server

Additional info:

Comment 1 Tim Waugh 2002-02-22 14:47:43 UTC
Do you have a suggestion for how this should work?  Is one global setting
enough, or does it need to be per-user?

Comment 2 Bernd Bartmann 2002-02-22 15:02:50 UTC
I see two options how to do this:
1. Add the geometry size for VNC server after the display and username in
/etc/sysconfig/vncservers like this:
VNCSERVER="1:bart:1400x1050 2:admin:1280x1024"
2. Don't use the VNCSERVERS variable. Instead specify all options for a VNC
server on a different line in the config file like this:
1:bart:-geometry 1400x1050 -depth 16
2:admin:-geometry 1280x1050 -depth 32

Another thing I noticed while setting up my VNC servers is that there is no good
error message if there is no .vnc/passwd file. It also would be good if
vncpasswd could create the .vnc directory if it doesn't exists. Otherwise you
can't setup a passwd entry so on has to create the .vnc directory by hand.

Comment 3 Tim Waugh 2002-03-05 12:09:26 UTC
I think the first solution is the best.  I'll look at this in the next
development cycle.

Comment 4 Ian Young 2002-04-25 09:32:08 UTC
Two comments on this issue, which I've also had to work round.

First, I would appreciate a solution where the settings can be made on a "per-
user" basis: my application involves connecting from clients with different 
screen geometries and having multiple "users" in VNCSERVERS, with different 
geometries, would make this easier for me.

Secondly, I would appreciate a solution in which more than the geometry can be 
specified.  Ideally, any VNC server option should be specifiable but in 
particular you need to be able to specify both the geometry and the colour 
depth, as otherwise the default 8-bit depth is a bit "blah" on a local network 
where you have the bandwidth to do 24-bit instead.

My current (trivial, unsophisticated) workround involves adding a VNCOPTIONS 
setting in the configuration file along with the VNCSERVERS one, and just 
substituting this into the vncserver command.  This acts as a global option and 
works for me just now, but doesn't address the multiple servers issue.  You 
could extend this idea by having VNCOPTIONS for global settings and 
VNCOPTIONS1, VNCOPTIONS2 etc for the different servers.  I'd be happy to lose 
the global VNCOPTIONS if that made things too complicated.

Comment 5 Tim Waugh 2002-07-17 09:35:26 UTC
*** Bug 68971 has been marked as a duplicate of this bug. ***

Comment 6 Tim Waugh 2003-03-21 14:55:28 UTC
*** Bug 86391 has been marked as a duplicate of this bug. ***

Comment 7 Tim Waugh 2003-06-23 17:01:03 UTC
*** Bug 97879 has been marked as a duplicate of this bug. ***

Comment 8 Bernd Bartmann 2003-07-30 16:07:00 UTC
Any news here? There still seems be no fix in Severn Beta1

Comment 12 Tim Waugh 2004-04-14 07:58:57 UTC
*** Bug 120511 has been marked as a duplicate of this bug. ***

Comment 13 Tim Waugh 2004-04-14 07:59:29 UTC
Bug #120511 has a patch which looks like a good approach.

Comment 14 Tim Waugh 2004-04-14 16:17:17 UTC
Patch applied in 4.0-1.beta4.11.

Note You need to log in before you can comment on or make changes to this bug.