Re: cygwinx 1.7 beta - crashes runing virt-manager
On 20/11/2009 04:04, Michael Breuer wrote: 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 (from 2007). Doesn't help now :( Anyone have suggestions? I can't even use XDMCP to log-in to Fedora 12 (Constantine), due to random segfaults :-( These seem to be due to a bad interaction between the damage tracking for the Composite extension and damage tracking for the shadow framebuffer. So can you try disabling the composite extension with '-extension Composite'? (note the captialization) -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: checkX problems
On 20/11/2009 19:43, Ken Brown wrote: On 11/20/2009 12:14 PM, Charles Wilson wrote: I've integrated Lothar's patch into run2/checkX (along with some other internal changes), and published a test release. Please try run-0.3.1-1 and let me know if it fixes your problems with checkX. But the new behavior of the timeout option (my problem #1) works fine, with one caveat: If I start the X server with startxwin.bat, it immediately exits and claims that a server is already running. This was also reported earlier today by Jim Reisert: http://cygwin.com/ml/cygwin-xfree/2009-11/msg00158.html Not quite: It seems that report says that the internal multiwindow-mode window manager claims another window manager is running (although it's difficult to be absolutely sure as the exact error message isn't reported :-)) Could it be that checkX is tricking XWin into thinking that a different X server is running? (I have no idea how XWin decides whether an X server is running, so this may or may not be plausible.) Strangely, the problem doesn't occur if I use startxwin.sh instead of startxwin.bat. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problem with new xinit - console window doesn't open (but bash starts)
On 20/11/2009 04:07, Jim Reisert AD1C wrote: More info: If I run startxwin.bat from a CMD.exe command line, the bash console xterm opens just fine. I only have problems starting it from the shortcut. This is typical of the current issue we have where 'run xterm' blocks when xterm tries to output 'Warning: Missing charsets in String to FontSet conversion' Any one of: - installing the CJK fonts - having 'tty' in the CYGWIN environment variable - having the LANG environment set to a non-UTF-8 locale should work around this problem Note that the environment variable will have to be set via the system applet in the Windows control panel, as only that controls the environment for the startxwin.bat started from the start menu... I do see some interesting things in the log file, however: MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel I hope these are explained by http://x.cygwin.com/docs/ug/using-shared-memory.html [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! These are expected when these font directories are empty, which is quite normal if you haven't installed all possible fonts Warning: Missing charsets in String to FontSet conversion This is xterm warning that the fontset has no fonts for CJK locales (as no CJK fonts are installed) -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problem with new xinit - console window doesn't open (but bash starts)
On Sun, 22 Nov 2009, Jon TURNEY wrote: On 20/11/2009 04:07, Jim Reisert AD1C wrote: More info: If I run startxwin.bat from a CMD.exe command line, the bash console xterm opens just fine. I only have problems starting it from the shortcut. This is typical of the current issue we have where 'run xterm' blocks when xterm tries to output 'Warning: Missing charsets in String to FontSet conversion' Any one of: - installing the CJK fonts - having 'tty' in the CYGWIN environment variable - having the LANG environment set to a non-UTF-8 locale should work around this problem ...or perhaps setting xterm's menuLocale resource to C Warning: Missing charsets in String to FontSet conversion This is xterm warning that the fontset has no fonts for CJK locales (as no CJK fonts are installed) iirc, that's from the Xaw initialization, which asks X11 (library), and _that_ falls into a hole where someone decided to load a fontset. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problem with new xinit - console window doesn't open (but bash starts)
On 20/11/2009 15:05, Jim Reisert AD1C wrote: I tried adding the missing fonts. I tried SET LANG=C Starting the X server is still unpredictable. Does this mean it sometimes works and sometimes doesn't? Or does it mean it fails in different ways each time you try? Now my log file (attached) shows: It also claims another window manage is running (and therefore shuts down), which is untrue (there is no other Xwin process running). Since I have touched 'check for another window manager' code recently, I was kind of expecting to see that I'd managed to break it in some way, but.. I'm not quite sure what to make of that log file. This is very strange. If you look for (II) xorg.conf is not supported, you'll see that it looks like that server starts again about half-way through. I did wonder if you were managing to somehow start two copies of XWin near-simultaneously, but I don't think that would produce a logfile like that (since it's not opened in append mode, you probably get the logfile from the last process to close it or something like that) An alternative explanation is that there is a really inconveniently timed server regeneration happening: just after the internal client threads have been created, but before they can connect, so they are still hanging around to be accepted by the next server generation. If we did have twice as many threads as we are supposed to, that would explain the final failure due to another WM running (as there's another WM thread, note that there are two 'winMultiWindowXMsgProc - Hello' lines) No idea why the server is regenerating though, needs more meditation :-) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: cygwinx 1.7 beta - crashes runing virt-manager
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, 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 (from 2007). Doesn't help now :( Anyone have suggestions? I can't even use XDMCP to log-in to Fedora 12 (Constantine), due to random segfaults :-( These seem to be due to a bad interaction between the damage tracking for the Composite extension and damage tracking for the shadow framebuffer. So can you try disabling the composite extension with '-extension Composite'? (note the captialization) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: cygwinx 1.7 beta - crashes runing virt-manager
Ok - just an FYI - F12+Cygwin 1.7 seems rock solid with -extension Composite. Been up for a while now, tried all sorts of stuff that was problematic earlier. The only anomaly I encountered (minor) was the cursor not tracking correctly in a Virt-viewer window. 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. 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:04, Michael Breuer wrote: 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 (from 2007). Doesn't help now :( Anyone have suggestions? I can't even use XDMCP to log-in to Fedora 12 (Constantine), due to random segfaults :-( These seem to be due to a bad interaction between the damage tracking for the Composite extension and damage tracking for the shadow framebuffer. So can you try disabling the composite extension with '-extension Composite'? (note the captialization) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: psexec does not work under cygwin-X
On 11/20/2009 04:45 AM, Hemal Pandya wrote: Hello, It seems psexec (from sysinternals) does not work correctly under cygwin-X. If I run it at the bash prompt in a command window it completes normally but from a rxvt or xterm window it stops after the first line of output from the remote process. And does it have the same problem if you set tty in your CYGWIN enviroment variable - see http://cygwin.com/cygwin-ug-net/using-cygwinenv.html? Sounds like the same old Win32-program-not-understanding-PTYs issue. Check the Cygwin archives for more. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
