Try -noclipboard.
I hit this as well.
Gertjan van Noord wrote:
after upgrading to xorg-server 1.7.1-3 starting X does no longer
work. Previous version 1.6.? worked. However, I can't seem to go
back to that version using the cygwin setup programme.
the startxwin.bat script does not complain,
For what it's worth, I tracked that down yesterday by looking at the
error log on the server - there was a complaint about clipboard - don't
recall what... seemed innocuous but figured I'd try turning off
clipboard. Viola, it worked.
One other point - as older versions of CygwinX have major
Connecting to F12 running Gnome, running python based applications
causes Xwin to segfault. For example, running virt-manager kills Xwin
immediately. Most of the F12 admin tools exhibit this behavior. I tried
-swcursor based on some old discussions on this list regarding Java
crashing Xwin
I've attached the log.
Jon TURNEY wrote:
On 19/11/2009 16:25, Michael Breuer wrote:
For what it's worth, I tracked that down yesterday by looking at the
error log on the server - there was a complaint about clipboard - don't
recall what... seemed innocuous but figured I'd try turning off
Different environment variables are set. I'd suggest in the xterm
version saving the env variables (envfile) and then see which one
causes the non-X version to stop running psexec.
Hemal Pandya wrote:
Hello,
It seems psexec (from sysinternals) does not work correctly under
cygwin-X. If I run
Fedora 12 - kdm for the greeter.
Jon TURNEY wrote:
On 20/11/2009 15:46, Michael Breuer wrote:
I've attached the log.
Thanks.
Can you also please tell me what OS the XDMCP host at 10.0.0.1 is
running?
Jon TURNEY wrote:
On 19/11/2009 16:25, Michael Breuer wrote:
For what it's worth, I
Ok - that worked. Was able to remove -noclipboard as well. Will use for
a while and make sure it stays up... so far, so good.
Jon TURNEY wrote:
On 20/11/2009 04:04, Michael Breuer wrote:
Connecting to F12 running Gnome, running python based applications
causes Xwin to segfault. For example
anyway as the proper way is to run VNC remotely, not in a
remote X session... but I figured I'd try to break it.
Michael Breuer wrote:
Ok - that worked. Was able to remove -noclipboard as well. Will use
for a while and make sure it stays up... so far, so good.
Jon TURNEY wrote:
On 20/11/2009 04
Ok - just one more FYI - after a shutdown and restart, I once again need
-noclipboard... so -extension Composite and -noclipboard are working,
-noclipboard seems to fix an intermittent problem.
Michael Breuer wrote:
Ok - just an FYI - F12+Cygwin 1.7 seems rock solid with -extension
Composite
wrote:
Michael Breuer wrote:
That was probably pushing things anyway as the proper way is to run
VNC remotely, not in a remote X session... but I figured I'd try to
break it.
---
Why is VNC more proper than X? I haven't been able to get
VNC to work, but X runs wonderfully. What am I
If you're running the beta, try adding -extension Composite -noclipboard
Linda Walsh wrote:
I'm trying to get a remote desktop to come up, but am not sure what's
required on the remote end.
Locally, I've been trying 'Xwin -query hostname
Either they come up with no login screen, or in one
Have you looked at the troubleshooting documentation? You know you can
run with verbose and log options. My guess is that the reason the
display can't be opened is made reasonable clear in your log file(s).
I'm also going to hazard a guess that your xserver doesn't have opengl
support.
Wendel
12 matches
Mail list logo
