Re: 1.7.0(0.214/5/3): XWin.exe reset after remote login screen on solaris (CDE or Java desktop) WM_QUIT
On 14/10/2009 22:41, Patrick Legault wrote: I get an error while I open a Solaris remote session via XDMCP the system I am connecting work with version 1.5 of cygwin (vista x64) but not the 1.7 (vista/server 2008 x64) I included the Xorg.log file, cygcheck.out and a basic description of my system. I also included a strace log in case it could help. I logged on the system using different type of sessions. failsafe session worked. CDE: failed. XWin started to logon, I could see the desktop for a few seconds then, closed to reopen. java desktop environment: Failed. XWin started to logon, I could see the desktop for a few seconds then, closed to reopen. It's pretty likely that the CDE and JDE sessions are exiting because something they are doing during initialization is returning an error they've decided they can't ignore. The useful log in this case is almost certainly on the Solaris host. I don't know where the relevant log is, but you might start by looking in /.dt/startlog. uname -a: CYGWIN_NT-6.0-WOW64 spatlegault2 1.7.0(0.214/5/3) 2009-10-03 14:33 i686 Cygwin solaris computer I am connecting to: SunOS zolla.somedomain.com 5.10 Generic sun4u sparc SUNW,Sun-Blade-1000 if you need help or more information to debug this issue, I will be happy to help you. if you already have an idea on something I could try to fix the WM_QUIT, just reply to this message. I have a Solaris 10 Update 7 (5/09) VM, and I'm able to start CDE or JDE using XDMCP from Cygwin/X 1.6.5-1 under Cygwin 1.7 without problems. -- 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: (strange) problem with xdotool
On 14/10/2009 17:45, Ariel Burbaickij wrote: Hello all, I have compiled, after some modifications to Makefile, xdotool to work in cygwin environment but I get following on attempt to activate window (window in question is xedit and I run in rootless, i.e. without any particular window manager, environment) xdotool windowactiviate 16777265 This is not so strange a problem when you know that thinking you are running without any particular window manager is wrong. When running rootless in -multiwindow mode, the X server starts an integrated WM, which effectively acts as a proxy for the native Windows WM. This integrated WM does not support _NET_ACTIVE_WINDOW Your windowmanager claims not to support _NET_ACTIVE_WINDOW, so the attempt to activate the window was aborted. xdo_window_activate reported an error Any clues about why _NET_ACTIVE_WINDOW is not supported and what one should do about it? :-) Ideally, write a patch to add _NET_ACTIVE_WINDOW support to the integrated WM. That should be fairly straightforward as all it would need to do it register the property on the root window and update it, and handle the receiving the message and translate it to a WM_ACTIVATE for the target window) (for bonus points, look for other EWMH hints it is useful for the integrated WM to implement) Your other option is run X in rooted mode, with a WM which supports _NET_ACTIVE_WINDOW. -- 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: 3-button-mouse emulating
On 15/10/2009 06:21, Steven Woody wrote: When using XWin as X server, it has a option let me emulate 3-button-mouse, but if I don't use XWin and x and X server ( this is default when I start x window by running startx script), how do I do the same thing? Your question doesn't make much sense. If you are asking how you add options like '-emulate3buttons' when using startx, then 'man startx' tells you startx [ [ client ] options ... ] [ −− [ server ] [ display ] options ... ] so e.g. startx -- -emulate3buttons -- 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: (strange) problem with xdotool
Regarding following passage (I do not have much objections to run X Window in what you call rooted mode just that somehow no Window Manager starts when I try to run it): all it would need to do it register the property on the root window and update it, and handle the receiving the message and translate it to a WM_ACTIVATE for the target window Yes, for the matter of exercise it woyuld be interesting to try to write a patch, just what is meant with root window here in rootless environment and where the code is supposed to go, i.e. where should I look at in order to try to graft the needed addtional code there? /wbr Ariel Burbaickij On Fri, Oct 16, 2009 at 2:34 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 14/10/2009 17:45, Ariel Burbaickij wrote: Hello all, I have compiled, after some modifications to Makefile, xdotool to work in cygwin environment but I get following on attempt to activate window (window in question is xedit and I run in rootless, i.e. without any particular window manager, environment) xdotool windowactiviate 16777265 This is not so strange a problem when you know that thinking you are running without any particular window manager is wrong. When running rootless in -multiwindow mode, the X server starts an integrated WM, which effectively acts as a proxy for the native Windows WM. This integrated WM does not support _NET_ACTIVE_WINDOW Your windowmanager claims not to support _NET_ACTIVE_WINDOW, so the attempt to activate the window was aborted. xdo_window_activate reported an error Any clues about why _NET_ACTIVE_WINDOW is not supported and what one should do about it? :-) Ideally, write a patch to add _NET_ACTIVE_WINDOW support to the integrated WM. That should be fairly straightforward as all it would need to do it register the property on the root window and update it, and handle the receiving the message and translate it to a WM_ACTIVATE for the target window) (for bonus points, look for other EWMH hints it is useful for the integrated WM to implement) Your other option is run X in rooted mode, with a WM which supports _NET_ACTIVE_WINDOW. -- 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: 1.7.0(0.214/5/3): XWin.exe reset after remote login screen on solaris (CDE or Java desktop) WM_QUIT
Hello I enabled some extra session logging in my .dtprofile under solaris and I found an error. I did the test with cygwin 1.5 and 1.7 so I could see the difference. I included some log files. when I tested with cygwin 1.5, I generated theses 2 log files: startlog-cygwin1.5.log and display_cygwin1.5.log when I tested with cygwin 1.7, I generated theses 2 log files: startlog-cygwin1.7.log and display_cygwin1.7.log The session worked using cygwin 1.5 but failed with 1.7. we can clearly see the issue with the log file display_cygwin1.7.log X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 143 (XINERAMA) Minor opcode of failed request: 2 (XINERAMAGetScreenCount) Resource id in failed request: 0x0 Serial number of failed request: 248 Current serial number in output stream: 248 can I recompile xwin.exe and disable xinerama or is there a different way to do it? if so, how would I fix this? Thanks -- From: Jon TURNEY jon.tur...@dronecode.org.uk Sent: Friday, October 16, 2009 8:24 AM To: cygwin-xfree@cygwin.com Cc: patr...@patrick-isp.com Subject: Re: 1.7.0(0.214/5/3): XWin.exe reset after remote login screen on solaris (CDE or Java desktop) WM_QUIT On 14/10/2009 22:41, Patrick Legault wrote: I get an error while I open a Solaris remote session via XDMCP the system I am connecting work with version 1.5 of cygwin (vista x64) but not the 1.7 (vista/server 2008 x64) I included the Xorg.log file, cygcheck.out and a basic description of my system. I also included a strace log in case it could help. I logged on the system using different type of sessions. failsafe session worked. CDE: failed. XWin started to logon, I could see the desktop for a few seconds then, closed to reopen. java desktop environment: Failed. XWin started to logon, I could see the desktop for a few seconds then, closed to reopen. It's pretty likely that the CDE and JDE sessions are exiting because something they are doing during initialization is returning an error they've decided they can't ignore. The useful log in this case is almost certainly on the Solaris host. I don't know where the relevant log is, but you might start by looking in /.dt/startlog. uname -a: CYGWIN_NT-6.0-WOW64 spatlegault2 1.7.0(0.214/5/3) 2009-10-03 14:33 i686 Cygwin solaris computer I am connecting to: SunOS zolla.somedomain.com 5.10 Generic sun4u sparc SUNW,Sun-Blade-1000 if you need help or more information to debug this issue, I will be happy to help you. if you already have an idea on something I could try to fix the WM_QUIT, just reply to this message. I have a Solaris 10 Update 7 (5/09) VM, and I'm able to start CDE or JDE using XDMCP from Cygwin/X 1.6.5-1 under Cygwin 1.7 without problems. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer startlog-cygwin1.7.log Description: Binary data startlog-cygwin1.5.log Description: Binary data display_cygwin1.5.log Description: Binary data display_cygwin-1.7.log Description: Binary data -- 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/
startxwin.bat and checkX
I don't think the line %RUN% checkX -d %DISPLAY% -t 12 in startxwin.bat accomplishes anything, because run.exe returns immediately, and checkX runs in the background. From 'man run': run [ -p path ] command [ -wait ] arguments [...] Issuing -wait as first program argument will make run wait for program completition, otherwise it returns immediately. [Chuck: Note the typo in completition.] So I think startxwin.bat should use %RUN% checkX -wait -d %DISPLAY% -t 12 I've tested this on my system, and xterm always starts. If I omit '-wait', xterm sometimes doesn't start. Ken -- 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: (strange) problem with xdotool
On 16/10/2009 13:46, Ariel Burbaickij wrote: Regarding following passage (I do not have much objections to run X Window in what you call rooted mode just that somehow no Window Manager starts when I try to run it): If you want to start X server and clients (perhaps a window manager) with a single command you need to look at 'man startx' all it would need to do it register the property on the root window and update it, and handle the receiving the message and translate it to a WM_ACTIVATE for the target window Yes, for the matter of exercise it would be interesting to try to write a patch, just what is meant with root window here in rootless environment and where the code is supposed to go, i.e. where should I look at in order to try to graft the needed additional code there? The root window exists (it's required by the X protocol), you just can't see it normally. If you untick the Hide Root Window option on the tray menu after you've launched some clients you should be able to see what's going on. http://x.cygwin.com/docs/cg/cygwin-x-cg.html You probably want to start looking at winMultiWindowXMsgProc() in hw/xwin/winmultiwindowwm.c -- 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: (strange) problem with xdotool
yes, it works, thank you, did startxwin.sh somehow fall out of favour? /wbr Ariel Burbaickij Regarding following passage (I do not have much objections to run X Window in what you call rooted mode just that somehow no Window Manager starts when I try to run it): If you want to start X server and clients (perhaps a window manager) with a single command you need to look at 'man startx' -- 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: startxwin.bat and checkX
On 10/16/2009 10:39 AM, Ken Brown wrote: I don't think the line %RUN% checkX -d %DISPLAY% -t 12 in startxwin.bat accomplishes anything, because run.exe returns immediately, and checkX runs in the background. From 'man run': run [ -p path ] command [ -wait ] arguments [...] Issuing -wait as first program argument will make run wait for program completition, otherwise it returns immediately. [Chuck: Note the typo in completition.] So I think startxwin.bat should use %RUN% checkX -wait -d %DISPLAY% -t 12 Even better, why bother with run.exe at all? Why not just use %CYGWIN_ROOT%\bin\checkX -d %DISPLAY% -t 12 Ken -- 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/
[ANNOUNCEMENT] [1.7] New: python-xdg-0.17-1
The following package has been added to the Cygwin 1.7 distribution: * python-xdg-0.17-1 PyXDG is a python library to access freedesktop.org standards. Currently supported are: * Base Directory Specification * Menu Specification * Desktop Entry Specification * Icon Theme Specification * Recent File Specification * Shared-MIME-Database Specification Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO == If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/
