retitle 381274 Some options like -depth 24 do not work if started from gdm.
severity 381274 normal
thanks
Hi
On Fri, Aug 11, 2006 at 08:52:41PM +0200, Christian Pernegger wrote:
> >I assume that as it works without your special configuration, I can close
> >this bug now, or?
>
> - vnc4server sti
I assume that as it works without your special configuration, I can close
this bug now, or?
- vnc4server still does not work when started with -depth 24 from gdm,
and possibly in a few other settings involving multiple instances.
This did work before xorg7, and while I have it running in 16bit n
Hi
I assume that as it works without your special configuration, I can close
this bug now, or?
I mean as gdm can add appropriate (working) options by itself, and you
add things that do not work.
Regards,
// Ola
On Fri, Aug 11, 2006 at 04:53:12PM +0200, Christian Pernegger wrote:
> Some progres
Some progress - the "-depth" parameter is at fault.
no -depth ... works
-depth 16 ... works
-depth 24 ... immediately exits
From the command line all of the above works. Re-reading the output of
"-help" I found the following:
1) -geometry WxH set screen 0's width, hei
reopen 381274
severity 381274 normal
retitle 381274 vnc4server: doesn't work from gdm anymore
thanks
Sorry, no cookies - the rgb and font errors are gone, yet the server
still won't start from gdm.
For reference, gdm is setup to start:
command=
/usr/bin/Xvnc4 -rfbwait 3 -securitytypes=none
Hi
I have found the same problem in vnc (Xrealvnc) and I hope I can get
some time to correct it (hopefully in the same way) tomorrow.
Regards,
// Ola
On Mon, Aug 07, 2006 at 11:19:50AM +0200, Christian Pernegger wrote:
> >Oh, I thought that the problem was that the options could not be
> >passe
Thanks.
I'll check as soon as I can find the time for it.
Regards,
// Ola
On Mon, Aug 07, 2006 at 11:19:50AM +0200, Christian Pernegger wrote:
> >Oh, I thought that the problem was that the options could not be
> >passed properly from gdm.
>
> AFAICT the options are passed properly ... if I'm
Oh, I thought that the problem was that the options could not be
passed properly from gdm.
AFAICT the options are passed properly ... if I'm really quick I can
see the spawned Xvnc4 in the output of 'ps aux' and it has the right
command line.
I have not started vnc from gdm before so I do not
Hi
On Sat, Aug 05, 2006 at 07:02:52PM +0200, Christian Pernegger wrote:
> >I'm aware of the problem and it has to do with the transition, and the
> >same problem exist on tightvncserver and vncserver as well.
>
> I know.
>
> >The problem is that the font path and rgb path has been changed.
>
>
I'm aware of the problem and it has to do with the transition, and the
same problem exist on tightvncserver and vncserver as well.
I know.
The problem is that the font path and rgb path has been changed.
That can't be all - setting the font and rgb path manually fixes the
problem when Xvnc4
tags 381274 + help
thanks
Hi
I'm aware of the problem and it has to do with the transition, and the
same problem exist on tightvncserver and vncserver as well.
The problem is that the font path and rgb path has been changed.
What needs to be done is to change the paths in the sources for vnc,
b
Package: vnc4server
Version: 4.1.1+X4.3.0-10
Severity: important
After three months during which my VNC-from-gdm setup has been broken
by the font path issue I decided to give it another try today, by
"hardcoding" the font path on the command line, like so: [one line,
newlines are for readability
12 matches
Mail list logo
