remote desktop /session bus woes...(was Re: problem with opengl (glxgears) running on cygwin ....)
Yaakov (Cygwin/X) wrote: On 2014-03-25 09:05, Jon TURNEY wrote: On 20/03/2014 08:41, Linda Walsh wrote: When I try to run glxgears locally, it displays the initial gears, but now they are just frozen. It doesn't work remotely, either, which was what I tried initially. It *used* to work -- remotely at 20-30 frames/second (as measured by fraps). Interestingly enough, I get a glx window, -- fraps will display 30 (the right number for my screen refresh rate), in the right corner of the glxgears window... but the gears don't move. Thanks for pointing out this issue. I think that currently glxgears doesn't work very well with the combination of indirect rendering and vsync-limited buffer swapping, so you are getting 30 fps, but they aren't useful frames. This should be fixed in mesa-demos-8.1.0-2. FWIW, I tried another X server...VcXsrv?... Same with that program. I tried several, got some that worked, most didn't. Of the few that worked 'well' remotely, they were variations on the glgears... got about 400-500 FPS -- and about low 300's MB/s in bandwidth consumed... that sounds about right... but I think there are other problem in trying to get a remote desktop to work now... everything wants to connect to the session bus -- and many progs won't start if they can't. So if I can't figure out a way to get that to work, remote usage is left at a fairly primitive level despite the high frame rates on a 3x4 window... ;-) One of the demo progs said it required opengl 2.1 .. my card has V4.something. well above 2.1, so that seems like another latent problem. Will look for the fixed version ... thanks for the news... -- 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: Graphical glitch in all but multiwindow mode over remote desktop
On 04/10/2012 09:00, Erik Fonnesbeck wrote: This is on Windows Server 2008 R2 with desktop composition enabled over remote desktop and using Cygwin/X 1.12.4 (though I have not seen any release notes mentioning a fix for it, so I'm guessing it is still relevant in the current version). Windows 7 should be relevant for testing this bug as well. I do not recall testing without desktop composition enabled for the remote desktop session, and I do not know whether the issue is specific to Windows 7/Server 2008 R2. Multiwindow mode works fine, but all other modes draw on the taskbar instead of in the Cygwin/X window. I have tried various combinations of settings for the X server, but the behavior is the same in all cases. Did you try adding '-engine 1' option to the X server command line? All modes apart from multiwindow use DirectX drawing by default, and there have been reports that doesn't work correctly over RDP. (From my brief research, this may be related to the DirectX version which Xwin uses. DirectX over RDP, rendering on the host, is supposed to work since Vista, but only for DX9 or later clients, and XWin uses an older DX interface) -- 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: Graphical glitch in all but multiwindow mode over remote desktop
On Mon, Oct 8, 2012 at 7:36 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 04/10/2012 09:00, Erik Fonnesbeck wrote: This is on Windows Server 2008 R2 with desktop composition enabled over remote desktop and using Cygwin/X 1.12.4 (though I have not seen any release notes mentioning a fix for it, so I'm guessing it is still relevant in the current version). Windows 7 should be relevant for testing this bug as well. I do not recall testing without desktop composition enabled for the remote desktop session, and I do not know whether the issue is specific to Windows 7/Server 2008 R2. Multiwindow mode works fine, but all other modes draw on the taskbar instead of in the Cygwin/X window. I have tried various combinations of settings for the X server, but the behavior is the same in all cases. Did you try adding '-engine 1' option to the X server command line? All modes apart from multiwindow use DirectX drawing by default, and there have been reports that doesn't work correctly over RDP. (From my brief research, this may be related to the DirectX version which Xwin uses. DirectX over RDP, rendering on the host, is supposed to work since Vista, but only for DX9 or later clients, and XWin uses an older DX interface) I was unable to reproduce this on my Windows 7 desktop, with desktop composition enabled or disabled over remote desktop (same version of Cygwin/X). It does seem to be specific to desktop composition, as it seemed to behave fine when I disabled it on the remote desktop connection to my Windows Server 2008 R2 system (which is a VM with no 3d capabilities, if that's relevant). Since it isn't used as a server, after you mentioned DirectX I decided to try installing the missing DirectX 9 files in case it would have any effect (it didn't). Adding the '-engine 1' option did make it display properly. -- 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: Refresh needed after Remote Desktop Connection
On 10/06/2011 04:30, Trollope, David wrote: I've been encountering a new behaviour recently which I'm hoping someone can shed some light on or suggest some tweak that will help. When you say this is 'new behavior', when did it start? When you upgraded the cygwin X server? or something else was changed? I regularly remote desktop to a machine running cygwin with an X server running - it is a Window 7 Enterprise box. The act of connecting through RDP resizes the screen. Normally the machine runs with two screens. After connecting with RDP (and while connected) the X windows do not refresh. I typically have open multiple xterm's but nothing refreshes. Until I move a window, it will not refresh. as soon as I move a window, it becomes usable again. I.E. xterm's do not display what is typed until the window is moved. This seems to affect all X windows. Any ideas? So if I'm understanding you correctly, the contents of the windows are drawn correctly after the display resizes, but then do not update? What about the root window, does that have the correct contents? If you run a simple X client such as 'ico' or 'xeyes' does that continue to draw correctly after the resize, or not? This is quite possibly a bug of some kind in the resize handling in the X server, although I don't have any particular insight at the moment as to what that bug might be :-) -- 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: Problems using XWin with remote desktop with latest version
On 20/09/2010 19:52, Jay Goldman wrote: I have the following batch file to start xwin: @echo off SET CYGWIN_ROOT= SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin SET PATH=.;%CYGWIN_ROOT%\bin;%PATH% SET XAPPLRESDIR= SET XCMSDB= SET XKEYSYMDB= SET XNLSPATH= %RUN% XWin -multiwindow -clipboard -silent-dup-error IF EXIST %CYGWIN_ROOT%\bin\urxvtd-X.exe %RUN% %CYGWIN_ROOT%\bin\urxvtd-X.exe This works fine (and has been for a whileyear). Occasionally, I have to connect to my machine via windows remote desktop. I've also been doing this for a while. With the latest version of x-windows; however, when I do so XWin.exe seg faults. I then kill the urxvtd-X.exe process, re-run my batch script, and all is well within the remote desktop session. Then I close the remote desktop session, and when I get back to my machine the x-windows-based command windows are no longer functional. I close down Xwin.exe (and urxvtd-X.exe), restart them, and I'm ok again. Any ideas as to what has changed to cause these new issues, (a) XWin.exe seg fault due to remote desktop connection (sorry, I don't have the seg fault info) (b) X-windows based command windows, (i.e., windows started with: urxvtc -g 80x42 -e /bin/bash -l -i) no longer display correctly when I disconnect the remote desktop session - I have to 're-start' xwin.exe (and urxvtd-X.exe) processes. This is pretty likely to be a known problem with the resize support added in Xserver 1.8.2-1, see [1] Unfortunately, due to a mistake on my part, there is no way to disable resize support in multiwindow mode in that version, so your options for a workaround are limited to: a) Downgrade to the previous Xserver version b) Use the test build provided by me in that thread c) Avoid RDP sessions which change the colour depth of your display (e.g by setting your display to use 16-bit colour, assuming the RDP sessions choose 16-bit for some reason) If your problems persist with the that test build, I'd very much like to hear about it. [1] http://cygwin.com/ml/cygwin-xfree/2010-08/msg00080.html -- 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/
Problems using XWin with remote desktop with latest version
I have the following batch file to start xwin: @echo off SET CYGWIN_ROOT= SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin SET PATH=.;%CYGWIN_ROOT%\bin;%PATH% SET XAPPLRESDIR= SET XCMSDB= SET XKEYSYMDB= SET XNLSPATH= %RUN% XWin -multiwindow -clipboard -silent-dup-error IF EXIST %CYGWIN_ROOT%\bin\urxvtd-X.exe %RUN% %CYGWIN_ROOT%\bin\urxvtd-X.exe This works fine (and has been for a while year). Occasionally, I have to connect to my machine via windows remote desktop. I've also been doing this for a while. With the latest version of x-windows; however, when I do so XWin.exe seg faults. I then kill the urxvtd-X.exe process, re-run my batch script, and all is well within the remote desktop session. Then I close the remote desktop session, and when I get back to my machine the x-windows-based command windows are no longer functional. I close down Xwin.exe (and urxvtd-X.exe), restart them, and I'm ok again. Any ideas as to what has changed to cause these new issues, (a) XWin.exe seg fault due to remote desktop connection (sorry, I don't have the seg fault info) (b) X-windows based command windows, (i.e., windows started with: urxvtc -g 80x42 -e /bin/bash -l -i) no longer display correctly when I disconnect the remote desktop session - I have to 're-start' xwin.exe (and urxvtd-X.exe) processes. -- 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/
remote desktop
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 case an error where it said: winProcEstablishConnection - Xdmcp, waiting to start clipboard client until 4th call... winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winGetDisplay: DISPLAY=:0.0 winClipboardProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winProcQueryTree - Hello winProcQueryTree - Clipboard client already launched, returning. winClipboardIOErrorHandler! winClipboardProc - setjmp returned for IO Error Handler. winDeinitMultiWindowWM - Noting shutdown in progress --- Is there something I'm missing or need to setup on my remote clients? They are various levels of suse boxen, and claim to have 'xdm' enabled via their chkconfig -- but I don't know if they are configured properly. Think was, is that I tried this before, and it just worked, but after some recent updates, it stopped working. I guess I just got lucky with it working before? It may be there's too little to go on here, and I just need to start from scratch, and try to figure out how XDM works from the man page, but it's odd that it was setup to 'work', but just seems to have randomly broke as I wasn't trying to change any configuration related to xdm on the remote machines...*sigh*. thanks if anyone sees any overt problems or knows any common ones w/suse... linda -- 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: remote desktop
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 case an error where it said: winProcEstablishConnection - Xdmcp, waiting to start clipboard client until 4th call... winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winGetDisplay: DISPLAY=:0.0 winClipboardProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winProcQueryTree - Hello winProcQueryTree - Clipboard client already launched, returning. winClipboardIOErrorHandler! winClipboardProc - setjmp returned for IO Error Handler. winDeinitMultiWindowWM - Noting shutdown in progress --- Is there something I'm missing or need to setup on my remote clients? They are various levels of suse boxen, and claim to have 'xdm' enabled via their chkconfig -- but I don't know if they are configured properly. Think was, is that I tried this before, and it just worked, but after some recent updates, it stopped working. I guess I just got lucky with it working before? It may be there's too little to go on here, and I just need to start from scratch, and try to figure out how XDM works from the man page, but it's odd that it was setup to 'work', but just seems to have randomly broke as I wasn't trying to change any configuration related to xdm on the remote machines...*sigh*. thanks if anyone sees any overt problems or knows any common ones w/suse... linda -- 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/ -- 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: Trouble with the xwin and ms remote desktop
Ok, just verified that the xserver running on the desktop crashes with the following scenario: Xserver on a dual display desktop (windows xp, cygwin), running wmaker as the window manager. I connect remotely to the desktop from a laptop(xp, cisco vpn) mstsc.exe to the desktop. I can see the program in the taskbar at the bottom of the screen, but I cant switch to it. I disconnect from the desktop's remote connection. When I get back to my desktop, the xserver has already died. This means that all my setup is gone, and I have to re-start all my sessions. Very annoying. If someone has a workaround for this, please let me know. I guess the immediate solution might be is to use the same screen size/resolution that I have at work. However my company will not allow that. A laptop with the vpn software is mandated. Any suggestions will be appreciated, Thanks, Sunil -Original Message- From: Matta, Sunil Sent: Friday, July 31, 2009 3:54 PM To: 'cygwin-xfree@cygwin.com' Subject: RE: Trouble with the xwin and ms remote desktop Forgot to include the stackdump, if this helps. Exception: STATUS_ACCESS_VIOLATION at eip=00410C8C eax= ebx=005F ecx=0022CA90 edx=0084BAF0 esi=01C3 edi=0084E5D8 ebp=0022CAC8 esp=0022CA50 program=C:\cygwin\bin\XWin.exe, pid 5012, thread main cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args 0022CAC8 00410C8C (0084C008, 0084E5A0, , 005D05A8) 0022CAE8 004D2EE0 (0084C008, 0022CB54, 005D05A8, 005D05A8) 0022CB18 004E147E (0022CB54, 005D05A8, 0001, 0022CB90) 0022CBF8 0053544C (00906B40, , , 01A00023) 0022CC48 00500E7B (00843360, 0002, , 004DCCC9) 0022CC98 004DD08B (0003, 008424D0, 00840090, 61166990) 0022CD98 61006148 (, 0022CDD0, 610054C0, 0022CDD0) 610054C0 61004416 (009C, A02404C7, E8611001, FF48) 2089677 [main] XWin 5012 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 2092567 [main] XWin 5012 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Thanks, Sunil -Original Message- Jon: thanks for the response. And yes, Xwin definitely crashes. On a desktop running Windows xp, started Xwin on a two monitor screen with wmaker as the window manager. Go home, connect to the desktop via a small laptop running xp as well. I am connecting using xp's remote desktop facility : mstsc.exe. Upon connection to the desktop screen, I see the xwin icon on the taskbar, and then xserver immediately crashes. Although, I just realized that the xwin root window is on screen 1, which the laptop cant even see. Maybe that's why xwin crashes ??? I will try again after I move the xwin to screen 0 and let you know. Also as a side, I have tried to use fvwm, but I don't see the usual virtual desktops on the screen ??? Which is why I am using wmaker as the window manager. Sunil -Original Message- From: Jon TURNEY [mailto:jon.tur...@dronecode.org.uk] Sent: Wednesday, July 29, 2009 1:52 PM To: cygwin-xfree@cygwin.com Cc: Matta, Sunil Subject: Re: Trouble with the xwin and ms remote desktop On 29/07/2009 14:45, Matta, Sunil wrote: I have been running Xwin on xp pro for a week along with xterms and emacs on my desktop. I then tried to remote connect (ms remote desktop: mstsc.exe) to the desktop from a laptop across the internet. 1) As soon as I had connected to my desktop (which was running xwin), the xserver crashed. I could see the rest of the ms xp apps on the remote screen though. The laptop has a 14 screen whereas the desktop has twin 19 screens. I then re-started the xserver from the remote laptop while connecting to the desktop, which seemed to be working fine as long as I stayed on the laptop. 2) When I got back to my desktop, the xserver still thought that the laptop's screen was in use, and wouldnt display correctly past the top two thirds of screen 0. I guess this makes sense since the xserver knew of the smaller screen size when it was started during the remote session. Consequently, anything on the bottom of the screen would not draw at all, or refresh properly. i.e. if I had an xterm on the lower end of the monitor, it would not accept any key strokes until I moved the xterm to the top two-thirds of the screen. Is there any way to request Xwin.exe to dynamically resize itself rather than bouncing the xserver a specific size/resolution profile ?? Otherwise, I might have to bounce the xserver every time i alternate between the desktop and the laptop. This is a known limitation. The only workaround is to restart the Xserver when the display resolution changes. Having used the Xserver
RE: Trouble with the xwin and ms remote desktop
Forgot to include the stackdump, if this helps. Exception: STATUS_ACCESS_VIOLATION at eip=00410C8C eax= ebx=005F ecx=0022CA90 edx=0084BAF0 esi=01C3 edi=0084E5D8 ebp=0022CAC8 esp=0022CA50 program=C:\cygwin\bin\XWin.exe, pid 5012, thread main cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args 0022CAC8 00410C8C (0084C008, 0084E5A0, , 005D05A8) 0022CAE8 004D2EE0 (0084C008, 0022CB54, 005D05A8, 005D05A8) 0022CB18 004E147E (0022CB54, 005D05A8, 0001, 0022CB90) 0022CBF8 0053544C (00906B40, , , 01A00023) 0022CC48 00500E7B (00843360, 0002, , 004DCCC9) 0022CC98 004DD08B (0003, 008424D0, 00840090, 61166990) 0022CD98 61006148 (, 0022CDD0, 610054C0, 0022CDD0) 610054C0 61004416 (009C, A02404C7, E8611001, FF48) 2089677 [main] XWin 5012 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 2092567 [main] XWin 5012 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Thanks, Sunil -Original Message- Jon: thanks for the response. And yes, Xwin definitely crashes. On a desktop running Windows xp, started Xwin on a two monitor screen with wmaker as the window manager. Go home, connect to the desktop via a small laptop running xp as well. I am connecting using xp's remote desktop facility : mstsc.exe. Upon connection to the desktop screen, I see the xwin icon on the taskbar, and then xserver immediately crashes. Although, I just realized that the xwin root window is on screen 1, which the laptop cant even see. Maybe that's why xwin crashes ??? I will try again after I move the xwin to screen 0 and let you know. Also as a side, I have tried to use fvwm, but I don't see the usual virtual desktops on the screen ??? Which is why I am using wmaker as the window manager. Sunil -Original Message- From: Jon TURNEY [mailto:jon.tur...@dronecode.org.uk] Sent: Wednesday, July 29, 2009 1:52 PM To: cygwin-xfree@cygwin.com Cc: Matta, Sunil Subject: Re: Trouble with the xwin and ms remote desktop On 29/07/2009 14:45, Matta, Sunil wrote: I have been running Xwin on xp pro for a week along with xterms and emacs on my desktop. I then tried to remote connect (ms remote desktop: mstsc.exe) to the desktop from a laptop across the internet. 1) As soon as I had connected to my desktop (which was running xwin), the xserver crashed. I could see the rest of the ms xp apps on the remote screen though. The laptop has a 14 screen whereas the desktop has twin 19 screens. I then re-started the xserver from the remote laptop while connecting to the desktop, which seemed to be working fine as long as I stayed on the laptop. 2) When I got back to my desktop, the xserver still thought that the laptop's screen was in use, and wouldnt display correctly past the top two thirds of screen 0. I guess this makes sense since the xserver knew of the smaller screen size when it was started during the remote session. Consequently, anything on the bottom of the screen would not draw at all, or refresh properly. i.e. if I had an xterm on the lower end of the monitor, it would not accept any key strokes until I moved the xterm to the top two-thirds of the screen. Is there any way to request Xwin.exe to dynamically resize itself rather than bouncing the xserver a specific size/resolution profile ?? Otherwise, I might have to bounce the xserver every time i alternate between the desktop and the laptop. This is a known limitation. The only workaround is to restart the Xserver when the display resolution changes. Having used the Xserver in a similar way, I do know how irritating that is :-) This is the Windows display size/Monitor count/position changes while running. item on the todo list at [1], as connecting via RDP with a different desktop size effectively changes the display size However, this shouldn't be causing a crash, so if you could provide the /var/log/Xwin.0.log for a session when that happens, that would be useful. [1] http://x.cygwin.com/devel/todo.html -- 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/
Trouble with the xwin and ms remote desktop
I have been running Xwin on xp pro for a week along with xterms and emacs on my desktop. I then tried to remote connect (ms remote desktop: mstsc.exe) to the desktop from a laptop across the internet. 1) As soon as I had connected to my desktop (which was running xwin), the xserver crashed. I could see the rest of the ms xp apps on the remote screen though. The laptop has a 14 screen whereas the desktop has twin 19 screens. I then re-started the xserver from the remote laptop while connecting to the desktop, which seemed to be working fine as long as I stayed on the laptop. 2) When I got back to my desktop, the xserver still thought that the laptop's screen was in use, and wouldnt display correctly past the top two thirds of screen 0. I guess this makes sense since the xserver knew of the smaller screen size when it was started during the remote session. Consequently, anything on the bottom of the screen would not draw at all, or refresh properly. i.e. if I had an xterm on the lower end of the monitor, it would not accept any key strokes until I moved the xterm to the top two-thirds of the screen. Is there any way to request Xwin.exe to dynamically resize itself rather than bouncing the xserver a specific size/resolution profile ?? Otherwise, I might have to bounce the xserver every time i alternate between the desktop and the laptop. Thanks, Sunil Matta -- 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: Trouble with the xwin and ms remote desktop
On 29/07/2009 14:45, Matta, Sunil wrote: I have been running Xwin on xp pro for a week along with xterms and emacs on my desktop. I then tried to remote connect (ms remote desktop: mstsc.exe) to the desktop from a laptop across the internet. 1) As soon as I had connected to my desktop (which was running xwin), the xserver crashed. I could see the rest of the ms xp apps on the remote screen though. The laptop has a 14 screen whereas the desktop has twin 19 screens. I then re-started the xserver from the remote laptop while connecting to the desktop, which seemed to be working fine as long as I stayed on the laptop. 2) When I got back to my desktop, the xserver still thought that the laptop's screen was in use, and wouldnt display correctly past the top two thirds of screen 0. I guess this makes sense since the xserver knew of the smaller screen size when it was started during the remote session. Consequently, anything on the bottom of the screen would not draw at all, or refresh properly. i.e. if I had an xterm on the lower end of the monitor, it would not accept any key strokes until I moved the xterm to the top two-thirds of the screen. Is there any way to request Xwin.exe to dynamically resize itself rather than bouncing the xserver a specific size/resolution profile ?? Otherwise, I might have to bounce the xserver every time i alternate between the desktop and the laptop. This is a known limitation. The only workaround is to restart the Xserver when the display resolution changes. Having used the Xserver in a similar way, I do know how irritating that is :-) This is the Windows display size/Monitor count/position changes while running. item on the todo list at [1], as connecting via RDP with a different desktop size effectively changes the display size However, this shouldn't be causing a crash, so if you could provide the /var/log/Xwin.0.log for a session when that happens, that would be useful. [1] http://x.cygwin.com/devel/todo.html -- 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: Trouble with the xwin and ms remote desktop
Jon: Thanks for the response. I have been running Xwin on xp pro for a week along with xterms and emacs on my desktop. I then tried to remote connect (ms remote desktop: mstsc.exe) to the desktop from a laptop across the internet. 1) As soon as I had connected to my desktop (which was running xwin), the xserver crashed. I could see the rest of the ms xp apps on the remote screen though. The laptop has a 14 screen whereas the desktop has twin 19 screens. I then re-started the xserver from the remote laptop while connecting to the desktop, which seemed to be working fine as long as I stayed on the laptop. 2) When I got back to my desktop, the xserver still thought that the laptop's screen was in use, and wouldnt display correctly past the top two thirds of screen 0. I guess this makes sense since the xserver knew of the smaller screen size when it was started during the remote session. Consequently, anything on the bottom of the screen would not draw at all, or refresh properly. i.e. if I had an xterm on the lower end of the monitor, it would not accept any key strokes until I moved the xterm to the top two-thirds of the screen. Is there any way to request Xwin.exe to dynamically resize itself rather than bouncing the xserver a specific size/resolution profile ?? Otherwise, I might have to bounce the xserver every time i alternate between the desktop and the laptop. This is a known limitation. The only workaround is to restart the Xserver when the display resolution changes. Having used the Xserver in a similar way, I do know how irritating that is :-) I was hoping there would be a xserver.resize() function that could be called from the xroot menu, but I guess not. This would definitely save a lot of headaches, when switching between different display sizes and resolutions. This is the Windows display size/Monitor count/position changes while running. item on the todo list at [1], as connecting via RDP with a different desktop size effectively changes the display size However, this shouldn't be causing a crash, so if you could provide the /var/log/Xwin.0.log for a session when that happens, that would be useful. The xserver on the desktop definitely crashed the first time I connected from a laptop which had never been used before. I will have to observe if this happens again. Thanks again. [1] http://x.cygwin.com/devel/todo.html -- 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/
Cygwin/X remote desktop
Hello, I am new bee here. I am using Cygwin/X from my windows XP box to connect to my development linux system via SSH X-port-forwarding. When I remote desktop to windows XP, all the X windows slow down heavily. How do I fix this issue? Thanks, Jeeva -- 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: Disruptive screen resolution change when using remote desktop
Was there any reply to this mail? I too face this issue and am eager to know the solution... On 5/18/07, Burvil [EMAIL PROTECTED] wrote: So, does anyone have any thoughts on this post from a couple days ago? --- Burvil [EMAIL PROTECTED] wrote: Hi all, I have my Cygwin/X set up with a root window running the fluxbox window manager on my desktop. It works quite well if I'm logged in to the system itself, i.e. I'm physically at the computer. However, if I login to my system via remote desktop, as I often need to do, the screen resolution is usually lower than that of the desktop, and so I get the following eror message: Disruptive screen resolution change Restore previous resolution to use Cygwin/X Clicking on 'Dismiss' does nothing - it apparently tries to correct itself, but fails, and the error message persists until I kill the X server. I looked at the following messages, after which I tried changing startxwin.bat to enable scrollbars and making sure color depth was the same on the OS of the remote and local systems as well as in cygwin/X itself. http://sourceware.org/ml/cygwin-xfree/2002-07/msg00508.html http://sourceware.org/ml/cygwin-xfree/2002-07/msg00480.html I also tried setting the root window resolution to 1024x768, which is a lot more common than the 1680x1050 on my desktop. Even when the screen resolution of the remote system, i.e. where the system I'm using remote desktop on, is, say, 1152x864, I still get the same error message. Is there a way to get around this other than getting a monitor that's the same resolution as my desktop? - Burvil * http://www.burvil.org * You snooze, you lose. Get messages ASAP with AutoCheck in the all-new Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_html.html -- 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/ - Burvil * http://www.burvil.org * It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/ -- 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/ -- 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: Disruptive screen resolution change when using remote desktop
Mansoorali Kudsi schrieb: Was there any reply to this mail? I too face this issue and am eager to know the solution... No there wasn't. And as far as i know there is no real solution for this problem, because the screen depth (amount of colors) changes when using the remote desktop (reduces to 16 Bit). Maybe setting the desktop to 16 Bit and using the same resolution will help, but i haven't tried. --- Burvil [EMAIL PROTECTED] wrote: Hi all, I have my Cygwin/X set up with a root window running the fluxbox window manager on my desktop. It works quite well if I'm logged in to the system itself, i.e. I'm physically at the computer. However, if I login to my system via remote desktop, as I often need to do, the screen resolution is usually lower than that of the desktop, and so I get the following eror message: Disruptive screen resolution change Restore previous resolution to use Cygwin/X Clicking on 'Dismiss' does nothing - it apparently tries to correct itself, but fails, and the error message persists until I kill the X server. I looked at the following messages, after which I tried changing startxwin.bat to enable scrollbars and making sure color depth was the same on the OS of the remote and local systems as well as in cygwin/X itself. http://sourceware.org/ml/cygwin-xfree/2002-07/msg00508.html http://sourceware.org/ml/cygwin-xfree/2002-07/msg00480.html I also tried setting the root window resolution to 1024x768, which is a lot more common than the 1680x1050 on my desktop. Even when the screen resolution of the remote system, i.e. where the system I'm using remote desktop on, is, say, 1152x864, I still get the same error message. Is there a way to get around this other than getting a monitor that's the same resolution as my desktop? -- 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/
Disruptive screen resolution change when using remote desktop
Hi all, I have my Cygwin/X set up with a root window running the fluxbox window manager on my desktop. It works quite well if I'm logged in to the system itself, i.e. I'm physically at the computer. However, if I login to my system via remote desktop, as I often need to do, the screen resolution is usually lower than that of the desktop, and so I get the following eror message: Disruptive screen resolution change Restore previous resolution to use Cygwin/X Clicking on 'Dismiss' does nothing - it apparently tries to correct itself, but fails, and the error message persists until I kill the X server. I looked at the following messages, after which I tried changing startxwin.bat to enable scrollbars and making sure color depth was the same on the OS of the remote and local systems as well as in cygwin/X itself. http://sourceware.org/ml/cygwin-xfree/2002-07/msg00508.html http://sourceware.org/ml/cygwin-xfree/2002-07/msg00480.html I also tried setting the root window resolution to 1024x768, which is a lot more common than the 1680x1050 on my desktop. Even when the screen resolution of the remote system, i.e. where the system I'm using remote desktop on, is, say, 1152x864, I still get the same error message. Is there a way to get around this other than getting a monitor that's the same resolution as my desktop? - Burvil * http://www.burvil.org * You snooze, you lose. Get messages ASAP with AutoCheck in the all-new Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_html.html -- 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/
display depth changing when using remote desktop and -multiwindow option, unable to set depth manually with -multiwindow
Hello. I use Cygwin/X on my office computer to run a program called Cadence (using 24-bit display), but have limited Cygwin functionality when I use remote desktop to work from home. Displays are set to 32-bit on both computers, and the Windows XP remote-desktop protocol (RDP) version I am using on both supports 32-bit displays. If I start Cygwin at the office and then use RDP to connect from home, everything continues working perfectly. However, if I log in remotely and then start a new Cygwin session, I get the following: *ERROR* Failed to find either 24-bit TrueColor or 8-bit PseudoColor Visual. *WARNING* Failed to find either 24-bit TrueColor or 8-pbit PseudoColor Visual. And my application will not start. I am using the following to start cygwin: run XWin -multiwindow -clipboard -silent-dup-error run xterm -e /usr/bin/bash -l I believe that Cygwin is detecting the optimal display settings on startup and determining it to be less than 32-bit when initiated through remote desktop. I would use the -depth command line option to manually set the depth to 32 bits, but this does not work with multiwindow enabled. Is there another way that I can manually set the display depth? Or somehow ensure that Cygwin determines that 32-bits are optimal when started through a remote desktop session? I have tried modifying the .inputrc file for 8-bit mode as follows, but had the same problem. set meta-flag on set convert-meta off set output-meta on Many thanks, Jason cygcheck_original.out 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/
Re: display depth changing when using remote desktop and -multiwindow option, unable to set depth manually with -multiwindow
Jason May schrieb: I believe that Cygwin is detecting the optimal display settings on startup and determining it to be less than 32-bit when initiated through remote desktop. I would use the -depth command line option to manually set the depth to 32 bits, but this does not work with multiwindow enabled. Is there another way that I can manually set the display depth? You can't set Xwins display depth larger than the Desktop it is running on. Usually that would be 16 Bit with rdp sessions. Did you ever check on the rdp Windows Desktop that you really get 32 Bit in Windows? Because i get 16 Bit even if i request 24 Bit. I have tried modifying the .inputrc file for 8-bit mode as follows, but had the same problem. That has no influence on Xwin. A possible solution would be a ssh connection and tunneling X11 through it. Cygwin provides a ssh daemon for windows. -- 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: display depth changing when using remote desktop and -multiwindow option, unable to set depth manually with -multiwindow
Thanks Holger for the response. - You can't set Xwins display depth larger than the Desktop it is running on. Usually that would be 16 Bit with rdp sessions. Did you ever check on the rdp Windows Desktop that you really get 32 Bit in Windows? Because i get 16 Bit even if i request 24 Bit. - I'm using a new beta version of microsoft's RDP which should support 32-bit displays (http://support.microsoft.com/kb/925876), but I will have to check whether it is actually working as advertised. - A possible solution would be a ssh connection and tunneling X11 through it. Cygwin provides a ssh daemon for windows. I am currently using SSH (putty) with tunneling to connect from the office PC to a linux server. The network administrators have not opened any ports on the linux server for outside access, I believe I can only enter the network via RDP on my office computer. I will see if they will allow me to open another port on my computer for SSH port forwarding, it should indeed solve the problem if I can bypass the office computer directly. Jason -- 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: XWin 100% CPU usage (Remote Desktop)
I worked on this for a long time since trying vista and here's my solution CYGWIN=title server itty binmode glob tty I believe that some arrangement of CYGWIN args cause troubles, but I can't verify which, and I also believe I had ntsec in there before. It would run for a while, althouhg process explorer would show 9-10 thousand context switches per second for XWin.exe, then eventually it would go to XWin.exe running full blast an unresponsive until I killed it. Hope it helps, dkr -- 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: XWin 100% CPU usage (Remote Desktop)
David Raila wrote: I worked on this for a long time since trying vista and here's my solution CYGWIN=title server itty binmode glob tty I believe that some arrangement of CYGWIN args cause troubles, but I can't verify which, and I also believe I had ntsec in there before. It would run for a while, althouhg process explorer would show 9-10 thousand context switches per second for XWin.exe, then eventually it would go to XWin.exe running full blast an unresponsive until I killed it. 'binmode' and 'glob' are on by default so you don't need to set these. The same is true for 'ntsec'. There is no 'itty' option for CYGWIN. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- 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: XWin 100% CPU usage (Remote Desktop)
Hi! The problem returned. I am using cygwin1-20060614.dll Now I downloaded cygwin1-20060802.dll and hope it will be better. Regards, David - http://noepatents.eu.org/ Innovation, not litigation ! --- David Balazic mailto:[EMAIL PROTECTED] HERMES Softlab http://www.hermes-softlab.com Zagrebska cesta 104Phone: +386 2 450 8846 SI-2000 Maribor Slovenija - Be excellent to each other. - Bill S. Preston, Esq. Ted Theodore Logan - -- 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: XWin 100% CPU usage (Remote Desktop)
David Balazic wrote : Hi! The problem returned. I am using cygwin1-20060614.dll Now I downloaded cygwin1-20060802.dll and hope it will be better. More info : I connected with Remote Desktop to the session that is running X. I saw two X icons in systray, one obviously dead. I moved the mouse pointer over them and one disappeared. The CPU usage dropped to 50%. After a while, CPU usage climbed back to 100% (remember, this is a 2 CPU SMP system). Sysinternals Process Explorer shows the following : - XWin.exe process memory usage (Private Bytes) jumps between 176 and 340 megabytes (every second or two) - XWin.exe CPU usage is split half-half in two threads : - xwin.exe+0x1000 (start address) - cygwin1.dll!_getreent+0x2fa0 There are 4 other threads using little to none CPU all running cygwin1.dll!toascii+0x15d0 Regards, David -- 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: XWin 100% CPU usage (Remote Desktop)
Hi! I tried cygwin1-20060614.dll and the problem is gone ! At least I can't reproduce it. Just in case, here are steps to repriduce it (with older cywwin1.dll) : 1.) - connect to remote Windows system using Remote Desktop - there start the cygwin bash shell (using the start menu entry) - in bash start startxwin.bat - close the new xterm by typing ctrl-D in it - right click the X icon in systray and select Exit - CPU goes to 50% (one entire CPU, my system has two of them) or 2.) - connect to remote Windows system using Remote Desktop - there start the cygwin bash shell (using the start menu entry) - in bash type xwin :0 -query some.unix.system.com -clipboard -scrollbars - close Remote Desktop (the session keeps running in background) - start remote Desktop, reduce it's windows size (Options / Display / Remore Desktop Size), let's say from original 1024x768 to 800x600 - reconnect to the same sessione on the remote system - result : X windows dead, consuming all CPU (50% on a 2-way SMP) As I said , the new snapshot DLL fixes both scenarios. Thanks for your assistance ! Regards, David PS: CC me on replies if you want proper replies from me, as I am not subscribed. Or lobby for a proper reply button on the web archives ;-) - http://noepatents.eu.org/ Innovation, not litigation ! --- David Balazic mailto:[EMAIL PROTECTED] HERMES Softlab http://www.hermes-softlab.com Zagrebska cesta 104Phone: +386 2 450 8846 SI-2000 Maribor Slovenija - Be excellent to each other. - Bill S. Preston, Esq. Ted Theodore Logan - -- 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: XWin 100% CPU usage (Remote Desktop)
More info. Maybe it is related to the trayicon. What happened : - XWin.exe using 100% CPU (those are 2 CPUs, both used to max) - I close a window or two in the X session - I notice there are two X icons in systray - I move the mouse over them, one disappears (this is normal when a dead icon is left in the systray) - CPU usage drops to 50% Unfortunately, I did more steps, so I can not say that the problem is really in the systray icons, but hopefully this is a step towards the solution for this annoying problem. Regards, David -Original Message- From: David Balazic Sent: Monday, May 29, 2006 10:32 AM To: 'cygwin-xfree@cygwin.com' Subject: RE: XWin 100% CPU usage (Remote Desktop) Hi! More : The system has 2 CPUs. Sometimes the XWin.exe process consumes both to 100% :-( The OS is Windows Server 2003 Standard Edition, SP1. Regards, David -Original Message- From: David Balazic Sent: Thursday, May 18, 2006 10:56 AM To: 'cygwin-xfree@cygwin.com' Subject: XWin 100% CPU usage (Remote Desktop) Hi! I have XWIN 6.8.2.0-4 and see it using 100% CPU all the time. Maybe relevant : I use MS Remote Desktop from another PC to access the system that actually runs XWin.exe. Is there anything I can do to reduce CPU usage ? Regards, David - http://noepatents.eu.org/ Innovation, not litigation ! --- David Balazic mailto:[EMAIL PROTECTED] HERMES Softlab http://www.hermes-softlab.com Zagrebska cesta 104Phone: +386 2 450 8846 SI-2000 Maribor Slovenija - Be excellent to each other. - Bill S. Preston, Esq. Ted Theodore Logan - -- 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: XWin 100% CPU usage (Remote Desktop)
David Balazic wrote: More info. Maybe it is related to the trayicon. What happened : - XWin.exe using 100% CPU (those are 2 CPUs, both used to max) - I close a window or two in the X session - I notice there are two X icons in systray - I move the mouse over them, one disappears (this is normal when a dead icon is left in the systray) - CPU usage drops to 50% Unfortunately, I did more steps, so I can not say that the problem is really in the systray icons, but hopefully this is a step towards the solution for this annoying problem. Did you try a recent snapshot? http://cygwin.com/snapshots/ -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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: XWin 100% CPU usage (Remote Desktop)
Larry Hall (Cygwin X) wrote : Did you try a recent snapshot? http://cygwin.com/snapshots/ Of cygwin1.dll ? Well, the answer is : no ;-) Can I just replace the file ? -Original Message- From: David Balazic Sent: Thursday, June 22, 2006 10:10 AM To: David Balazic; cygwin-xfree@cygwin.com Subject: RE: XWin 100% CPU usage (Remote Desktop) More info. Maybe it is related to the trayicon. What happened : - XWin.exe using 100% CPU (those are 2 CPUs, both used to max) - I close a window or two in the X session - I notice there are two X icons in systray - I move the mouse over them, one disappears (this is normal when a dead icon is left in the systray) - CPU usage drops to 50% Unfortunately, I did more steps, so I can not say that the problem is really in the systray icons, but hopefully this is a step towards the solution for this annoying problem. Regards, David -Original Message- From: David Balazic Sent: Monday, May 29, 2006 10:32 AM To: 'cygwin-xfree@cygwin.com' Subject: RE: XWin 100% CPU usage (Remote Desktop) Hi! More : The system has 2 CPUs. Sometimes the XWin.exe process consumes both to 100% :-( The OS is Windows Server 2003 Standard Edition, SP1. Regards, David -Original Message- From: David Balazic Sent: Thursday, May 18, 2006 10:56 AM To: 'cygwin-xfree@cygwin.com' Subject: XWin 100% CPU usage (Remote Desktop) Hi! I have XWIN 6.8.2.0-4 and see it using 100% CPU all the time. Maybe relevant : I use MS Remote Desktop from another PC to access the system that actually runs XWin.exe. Is there anything I can do to reduce CPU usage ? Regards, David - http://noepatents.eu.org/ Innovation, not litigation ! --- David Balazic mailto:[EMAIL PROTECTED] HERMES Softlab http://www.hermes-softlab.com Zagrebska cesta 104Phone: +386 2 450 8846 SI-2000 Maribor Slovenija - Be excellent to each other. - Bill S. Preston, Esq. Ted Theodore Logan - -- 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: XWin 100% CPU usage (Remote Desktop)
Hi! More : The system has 2 CPUs. Sometimes the XWin.exe process consumes both to 100% :-( The OS is Windows Server 2003 Standard Edition, SP1. Regards, David -Original Message- From: David Balazic Sent: Thursday, May 18, 2006 10:56 AM To: 'cygwin-xfree@cygwin.com' Subject: XWin 100% CPU usage (Remote Desktop) Hi! I have XWIN 6.8.2.0-4 and see it using 100% CPU all the time. Maybe relevant : I use MS Remote Desktop from another PC to access the system that actually runs XWin.exe. Is there anything I can do to reduce CPU usage ? Regards, David - http://noepatents.eu.org/ Innovation, not litigation ! --- David Balazic mailto:[EMAIL PROTECTED] HERMES Softlab http://www.hermes-softlab.com Zagrebska cesta 104Phone: +386 2 450 8846 SI-2000 Maribor Slovenija - Be excellent to each other. - Bill S. Preston, Esq. Ted Theodore Logan - -- 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: Using MS Remote Desktop causes screen disruption error
Good news! That did the trick. Thank you! R -- View this message in context: http://www.nabble.com/Re%3A-Using-MS-Remote-Desktop-causes-screen-disruption-error-t1549562.html#a4209248 Sent from the cygwin-xfree forum at Nabble.com. -- 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/
Using MS Remote Desktop causes screen disruption error
Hi, When connecting from home to my work computer using Microsoft's Remote Desktop, I find that I cannot use my already opened Cygwin X window because I get a 'destructive screen configuration' change error. Is there a workable way around this dilemma without drastically changing how I have X configured. For what it's worth, my window manager is XFCE and I start X this way: exec $prog /etc/xdg/xfce4/xinitrc $* -- /usr/X11R6/bin/XWin :0 -noreset -ac -nowinkill -clipboard -scrollbars #-multiwindow I added the -scrollbars option in the hopes it would let me in, but that didn't work. Any suggestions will be greatly appreciated! Thank you, R -- View this message in context: http://www.nabble.com/Using-MS-Remote-Desktop-causes-screen-disruption-error-t1536321.html#a4173817 Sent from the cygwin-xfree forum at Nabble.com. -- 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/
Using MS Remote Desktop causes screen disruption error
Hi, When connecting from home to my work computer using Microsoft's Remote Desktop, I find that I cannot use my already opened Cygwin X window because I get a 'destructive screen configuration' change error. Is there a workable way around this dilemma without drastically changing how I have X configured. For what it's worth, my window manager is XFCE and I start X this way: exec $prog /etc/xdg/xfce4/xinitrc $* -- /usr/X11R6/bin/XWin :0 -noreset -ac -nowinkill -clipboard -scrollbars #-multiwindow I added the -scrollbars option in the hopes it would let me in, but that didn't work. Any suggestions will be greatly appreciated! Thank you, R -- View this message in context: http://www.nabble.com/Using-MS-Remote-Desktop-causes-screen-disruption-error-t1536324.html#a4173820 Sent from the cygwin-xfree forum at Nabble.com. -- 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: Using MS Remote Desktop causes screen disruption error
R. Lewis wrote: When connecting from home to my work computer using Microsoft's Remote Desktop, I find that I cannot use my already opened Cygwin X window because I get a 'destructive screen configuration' change error. Is there a workable way around this dilemma without drastically changing how I have X configured. For what it's worth, my window manager is XFCE and I start X this way: exec $prog /etc/xdg/xfce4/xinitrc $* -- /usr/X11R6/bin/XWin :0 -noreset -ac -nowinkill -clipboard -scrollbars #-multiwindow Hello R, I had the same problem due to a screensaver that resets my display resolution and depth. This is what worked for me: I've added an -engine 1 option to my startsx command line. In your case this would be something like: exec $prog /etc/xdg/xfce4/xinitrc $* -- /usr/X11R6/bin/XWin :0 -engine 1 -noreset -ac -nowinkill -clipboard -scrollbars #-multiwindow It's an underdocumented* parameter but the point is that it allows you to select a different engine for the screen output, and in this particular case the -engine 1 selects an output engine that is not susceptible to changes in screen depth and/or resolution. As I said, it works for me, but YMMV. Bye, Erik * see http://x.cygwin.com/docs/ug/configure-cygwin-x-options.html -- 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/
Extraneous key autorepeat w/ remote desktop
Hi folks, Very nice product. It's going up against Reflection/X on my desktop and is for the most part wining. But there one annoying problem. When I remote desktop to a remote Windows system and run Cygwin/X from the remote system, any communication delays while typing over the remote desktop network are interpreted as one long keypress. Which in turn triggers the keystroke auto repeat and feeds a bunch of extra keystrokes into my input stream. I've tried playing with the autorepeat settings. Turning it off altogether fixes the problem, but isn't very convenient when I want to enter a lot of the same keystroke, for example when moving the text cursor around. Setting up a long initial delay helps some, but communication delays can sometimes last for 5-10 seconds, far longer than I am willing to wait for autorepeat to trigger in normal use. I've also tried running Cygwin/X on the local system and talking to an X client on remote systems. This works, but has some unacceptable delays and problems with the VPN I have to run through. Right now it's kind of a tossup whether it is more annoying to put up with the delays with a local X server, or deal with the extra keystroke with a remote X server. I not sure what, if anything, can be done to detect and avoid remote desktop communication delays. But Reflection/X never has this problem, so there must be some way to do it. Thanks for listening, -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: X server window resizes after remote desktop, and can't resize back
Here is another example of the problem where remote desktop causes the X server window to resize but on logging in locally it doesn't get restored to its former size. If the bug is tricky to fix, a possible workaround would be to let the user manually override the size of the X server window, for example by enabling the Maximize button. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-12 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin -clipboard -engine 1 -br ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1200 h 1600 winInitializeDefaultScreens - Returning winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winSetEngine - Using user's preference: 1 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1194 height: 1547 depth: 32 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 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 (--) Setting autorepeat to delay=250, rate=31 (--) winConfigKeyboard - Layout: 0809 (0809) (--) Using preset keyboard for English (United Kingdom) (809), type 4 Rules = xorg Model = pc105 Layout = gb Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 597 773 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 8 winWindowProc - WM_DISPLAYCHANGE - new width: 1024 new height: 720 winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 8, new bpp: 32 winWindowProc - WM_DISPLAYCHANGE - new width: 1200 new height: 1600 winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. winDeinitMultiWindowWM - Noting shutdown in progress -- Ed Avis [EMAIL PROTECTED]
Re: X server window resizes after remote desktop, and can't resize back
Ed Avis [EMAIL PROTECTED] writes: I remote desktop'd into my XP machine using a smaller display size than the monitor connected locally. When I went back in front of the machine I found that the X server window had shrunk to roughly the size of the remote desktop screen, but had not grown back again when I logged in locally. Here is a second XWin.log showing the problem. I tried changing the display size from control panel back and forth a few times, but the X server window refused to grow back to its former size. Maybe there could be some logging saying 'I noticed a change in Windows display size and I am resizing the X window accordingly' or 'I noticed a change in Windows display size but will not change the X window size'. Then one could see what is the intended behaviour. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-7 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin -clipboard -engine 1 -br ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1200 h 1600 winInitializeDefaultScreens - Returning winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1200 dwHeight: 1600 winSetEngine - Using user's preference: 1 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1194 height: 1547 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1194 height: 1547 depth: 32 size image: 7388472 winAllocateFBShadowGDI - Created shadow stride: 1194 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 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 (--) Setting autorepeat to delay=250, rate=31 (--) winConfigKeyboard - Layout: 0809 (0809) (--) Using preset keyboard for English (United Kingdom) (809), type 4 Rules = xorg Model = pc105 Layout = gb Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 597 773 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard not yet started, aborting. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed
X server window resizes after remote desktop, and can't resize back
I remote desktop'd into my XP machine using a smaller display size than the monitor connected locally. When I went back in front of the machine I found that the X server window had shrunk to roughly the size of the remote desktop screen, but had not grown back again when I logged in locally. The maximize button on the window is greyed out and I can't resize the window using its borders, so there seems to be no way to restore the original size. The log (shown below) indicates that the X server did notice the change of screen size, but for whatever reason didn't resize its window. I think it is a bug that the window didn't get restored to its original size, but I'd also like to request some kind of manual resizing option (perhaps ungreying the maximize button) so the server can be fixed if the problem happens again. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-4 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin -clipboard -engine 1 -br ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1200 h 1600 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winValidateArgs - Returning. (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1200 dwHeight: 1600 winSetEngine - Using user's preference: 1 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1200 h: 1600 winCreateBoundingWindowWindowed - Current w: 1200 h: 1600 winAdjustForAutoHide - Original WorkArea: 0 0 1572 1200 winAdjustForAutoHide - Adjusted WorkArea: 0 0 1572 1200 winCreateBoundingWindowWindowed - WindowClient w 1194 h 1547 r 1194 l 0 b 1547 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1194 height: 1547 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1194 height: 1547 depth: 32 size image: 7388472 winAllocateFBShadowGDI - Created shadow stride: 1194 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winRandRInit () winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. 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 (--) Setting autorepeat to delay=250, rate=31 (--) winConfigKeyboard - Layout: 0809 (0809) (--) Using preset keyboard for English (United Kingdom) (809), type 4 Rules = xorg Model = pc105 Layout = gb Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 597 773 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning. winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard not yet started, aborting. winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 32 winWindowProc - WM_DISPLAYCHANGE - new width: 1600 new height: 1200 winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 32 winWindowProc - WM_DISPLAYCHANGE - new width: 1200 new height: 1600 winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 8 winWindowProc - WM_DISPLAYCHANGE - new width: 1152 new height: 864 winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 8, new bpp: 8 winWindowProc - WM_DISPLAYCHANGE - new width: 1200 new height: 900 winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 8, new bpp: 32 winWindowProc - WM_DISPLAYCHANGE - new width: 1200 new height: 1600 -- Ed Avis [EMAIL PROTECTED]
Remote Desktop, MultiWindow Cursors
Looks like the newer versions of XWin are having cursor problems when coming out of remote desktop (XP Pro). After a remote desktop session the cursor completely disappears in the X window client area. Here's what I'm seeing: - Run a cygwin bash shell - XWin -multiwindow -clipboard - Run xterm on a Linux box w/ PuTTY tunneling X. - Move the cursor around the xterm. Nice I-Beam. - Go to another machine, remote desktop in. - xterm is still active app but cursor is now outside the xterm window over the windows desktop but with X's X cursor. - Move cursor around. It remains the X cursor wherever you move it. Verify. - Activate a Windows app (IE) and then back to xterm. Cursor returns to I-Beam and proper behavior. - Shut down remote desktop. Return to tty. - Now when the mouse moves over any X window it completely disappears. Also, at this point, copying anything will completely crash XWin. I'm in the process of looking into it. My debug build of current sources doesn't exhibit this behavior. I'll try a non-debug build next. Hey, is there a safe, automated, way to do a full, clean build of just Xserver? Dan
Re: Crash when remote desktop changes screen resolutions
Harold L Hunt II [EMAIL PROTECTED] writes: Pass -engine 1 to XWin.exe and see what happens. Yes, with -engine 1 it doesn't crash when I rdesktop into the machine. There is a different strange symptom though: when I sit down at the machine again, the X server window is a bit too wide. I happen to have two monitors with the X server running fullscreen in the left monitor, and after I did the rdesktop stuff and went back to the local machine the X server window is wide enough to extend a little bit onto the right hand monitor. But it does so in an odd way: just inside the RH border of the X server window there are a few pixels of 'dead space' which are not redrawn. I still see this gap if I drag the window around so that it's only on the left monitor. Here's the log: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.67 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin -clipboard -engine 1 ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1280 dwHeight: 1024 winSetEngine - Using user's preference: 1 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 996 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 996 1280 winCreateBoundingWindowWindowed - WindowClient w 1274 h 971 r 1274 l 0 b 971 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1274 height: 971 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1274 height: 971 depth: 32 size image: 4948216 winAllocateFBShadowGDI - Created shadow stride: 1274 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winRandRInit () winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. 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 (--) Setting autorepeat to delay=250, rate=31 (--) winConfigKeyboard - Layout: 0809 (0809) (--) Using preset keyboard for English (United Kingdom) (809), type 4 Rules = xfree86 Model = pc105 Layout = gb Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 637 485 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify -
Re: Crash when remote desktop changes screen resolutions
Here is another example log file showing this crash: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.66 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1280 dwHeight: 1024 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 996 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 996 1280 winCreateBoundingWindowWindowed - WindowClient w 1274 h 971 r 1274 l 0 b 971 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 5096 winAllocateFBShadowDDNL - Created shadow pitch: 5096 winAllocateFBShadowDDNL - Created shadow stride: 1274 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winRandRInit () winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. 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 (--) Setting autorepeat to delay=250, rate=31 (--) winConfigKeyboard - Layout: 0809 (0809) (--) Using preset keyboard for English (United Kingdom) (809), type 4 Rules = xfree86 Model = pc105 Layout = gb Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 637 485 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning. winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard not yet started, aborting. winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt failure message maximum (10) reached. No more failure messages will be printed. winClipboardFlushXEvents - SelectionNotify - X*TextPropertyToTextList list_return is NULL. winClipboardFlushXEvents - SelectionNotify - X*TextPropertyToTextList list_return is NULL. winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 8 winWindowProc - WM_DISPLAYCHANGE - new width: 1024 new height: 720 winWindowProc - Disruptive change in depth winDisplayDepthChangeDialog - DialogBox returned: 1840476 winDisplayDepthChangeDialog - GetLastError: 6 winReleasePrimarySurfaceShadowDDNL - Hello winReleasePrimarySurfaceShadowDDNL - Detached clipper winReleasePrimarySurfaceShadowDDNL - Released primary surface winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Could not create primary surface: 8876024e winChangeDelthDlgProc - wParam == s_pScreenInfo-dwBPP winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 8, new bpp: 32 winWindowProc - WM_DISPLAYCHANGE - new width: 1280 new height: 1024 winReleasePrimarySurfaceShadowDDNL - Hello winReleasePrimarySurfaceShadowDDNL - Released primary surface winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Could not create primary surface: 8876024e --
Re: Crash when remote desktop changes screen resolutions
Pass -engine 1 to XWin.exe and see what happens. Harold Ed Avis wrote: Here is another example log file showing this crash: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.66 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1280 dwHeight: 1024 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 996 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 996 1280 winCreateBoundingWindowWindowed - WindowClient w 1274 h 971 r 1274 l 0 b 971 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 5096 winAllocateFBShadowDDNL - Created shadow pitch: 5096 winAllocateFBShadowDDNL - Created shadow stride: 1274 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winRandRInit () winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. 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 (--) Setting autorepeat to delay=250, rate=31 (--) winConfigKeyboard - Layout: 0809 (0809) (--) Using preset keyboard for English (United Kingdom) (809), type 4 Rules = xfree86 Model = pc105 Layout = gb Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 637 485 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning. winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard not yet started, aborting. winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt failure message maximum (10) reached. No more failure messages will be printed. winClipboardFlushXEvents - SelectionNotify - X*TextPropertyToTextList list_return is NULL. winClipboardFlushXEvents - SelectionNotify - X*TextPropertyToTextList list_return is NULL. winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 8 winWindowProc - WM_DISPLAYCHANGE - new width: 1024 new height: 720 winWindowProc - Disruptive change in depth winDisplayDepthChangeDialog - DialogBox returned: 1840476 winDisplayDepthChangeDialog - GetLastError: 6 winReleasePrimarySurfaceShadowDDNL - Hello winReleasePrimarySurfaceShadowDDNL - Detached clipper winReleasePrimarySurfaceShadowDDNL - Released primary surface winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Could not create primary surface: 8876024e winChangeDelthDlgProc - wParam == s_pScreenInfo-dwBPP winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 8, new bpp: 32 winWindowProc - WM_DISPLAYCHANGE - new width: 1280 new height: 1024 winReleasePrimarySurfaceShadowDDNL - Hello winReleasePrimarySurfaceShadowDDNL - Released primary surface winCreatePrimarySurfaceShadowDDNL - Creating primary surface
Crash when remote desktop changes screen resolutions
With Windows XP every PC can run the remote desktop service which you can connect to with rdesktop. The last couple of times I've tried this it has crashed XWin.exe. My machine normally has two monitors at 1280x1024, 32-bit colour, but when connecting with rdesktop I use 1024x720, and I think the colour depth is lower too since some icons look a bit funny. Here is the XWin.log from the most recent crash. It seems to show that the crash happened when I went back to the local screen and unlocked it. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.66 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1280 dwHeight: 1024 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 996 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 996 1280 winCreateBoundingWindowWindowed - WindowClient w 1274 h 971 r 1274 l 0 b 971 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 5096 winAllocateFBShadowDDNL - Created shadow pitch: 5096 winAllocateFBShadowDDNL - Created shadow stride: 1274 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winRandRInit () winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. 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 (--) Setting autorepeat to delay=250, rate=31 (--) winConfigKeyboard - Layout: 0809 (0809) (--) Using preset keyboard for English (United Kingdom) (809), type 4 Rules = xfree86 Model = pc105 Layout = gb Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 637 485 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning. winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt failure message maximum (10) reached. No more failure messages will be printed. winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1 winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 2 winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1 winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1 winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt
Re: XDMCP howto for cygwin? (or other remote-desktop solution)
Thomas, First off, I'd like to confirm that WSAD *does* run in Gnome remotely via XDMCP (Linux-Windows). Haven't tried with KDE, but I don't see any reason why it wouldn't work remotely if it works locally. More below. On Fri, 30 Jan 2004, Thomas L Roche wrote: On 2004.01.30 21:11, Thomas L Roche wrote: I'm assuming (from traffic on the list) that cygwin supports XDMCP, but I'm unclear on * How to do it on cygwin? All the howto's I've seen reference Linux, and I'm also a little unclear on what goes on which end. Did you chance upon http://x.cygwin.com/docs/ug/using-remote-session.html? Willem Riede [EMAIL PROTECTED] 01/30/2004 10:11:59 PM: It's very straightforward. Assuming you have cygwin and xfree installed on a windows box, you edit C:\cygwin\usr\X11R6\bin\startxdmcp.bat to have your windows box IP number in DISPLAY and the Linux box IP number in REMOTE_HOST. OK. BTW, does this mean that this won't work if either is on DHCP? (Fortunately, for my specific case both have static IP.) Umm, it works with DHCP, but there's a catch: the forward and reverse DNS lookups for your Windows box have to match (IOW, if your machine is named, e.g., 'cookie.raleigh.ibm.com', the reverse DNS lookup of the IP from the Linux machine also has to return 'cookie.raleigh.ibm.com', otherwise XDMCP won't work). You can see these mismatches show up in /var/log/messages. Of course, it does help to be root or sudo for this... Oh, and from your statement above, you must be entering the actual IP of the Windows box. No need -- just use 127.0.0.1 (or even localhost). REMOTE_HOST can also be the FQDN of the Linux machine, rather than IP. If you have more than one network interface (e.g., wireless and ethernet), you may need the -from parameter, too. OK, so all I need on the client ... err, server ... err, cygwin side is just to edit /usr/X11R6/bin/startxdmcp.bat: done. Then I gotta setup G|K|XDM on the ... non-cygwin side: FWIW, you don't even have to use startxdmcp.bat -- I use a standalone command, like this (I have another X server running on :0.0, hence :1.0 for display, and some other options you probably won't need as they are specific to my configuration): XWin.exe :1.0 -unixkill -scrollbars -screen 0 1280 1024 -emulate3buttons -once -query mylinuxmachine.watson.ibm.com Also make sure /etc/X11/gdm/gdm.conf contains [xdmcp] Enable=true except the box I'm targeting currently only has KDE, so it's /etc/X11/xdm/xdm-config, and I just need to comment out !DisplayManager.requestPort:0 Correct? (But first, I need root to `su` :-) You can probably get temporary sudo access for the commands you need to run -- the sysadmins are more likely to give that out than full root access. GDM has to run on linux, so you need init to go to level 5. OK. Is there anything else that needs done for KDE? Then you can run startxdmcp.bat (I have a shortcut for it on my W2K desktop) to get the login screen for your linux box. Once logged in you get the full Gnome desktop (or KDE if that's your preference). Sounds easy! Just gotta get access. Hope this works. If you want to troubleshoot this interactively, feel free to Sametime me (my internal ID is in Bluepages). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
Re: XDMCP howto for cygwin? (or other remote-desktop solution)
On 2004.01.30 23:18, Thomas L Roche wrote: OK. Is there anything else that needs done for KDE? Unfortunately I don't know that first hand, as I use Gnome. Regards, Willem Riede.
XDMCP howto for cygwin? (or other remote-desktop solution)
Is there an XDMCP howto for cygwin? Or is there another/better way to get what I want: My development group recently lost its testers (they now do bigger scenario tests) so we now need to do our own functional test, and we need to do it on several platforms. We develop on Windows (still, may change soon) so we setup some Linuxen to/from which I can forward with ssh -Xl me it (using -multiwindow -clipboard) so I know I'm setup more-or-less correctly. (Although I'm getting lotsa weirdness on the latest cygwin, but that's a separate topic. And I've gotta test if I can now run WSAD remotely using -multiwindow.) We occasionally get bug reports that are toolkit-specific, so I'd really like to be able to run an entire remote desktop from cygwin. (E.g. if a user says, I run foo from Konqueror | Nautilus, and it does bar, I'd like to be able to fire up a KDE | GNOME session.) My impression is that this is normally done using XDMCP connects, after which one can start Xwin -query it and my but I've never set this up. So I'm wondering: * is XDMCP The Way (tm) to do this? If so, I'm assuming (from traffic on the list) that cygwin supports XDMCP, but I'm unclear on * How to do it on cygwin? All the howto's I've seen reference Linux, and I'm also a little unclear on what goes on which end. Your assistance is appreciated, feel free to forward, and please CC me as well as the list if possible (I'm on the digest).
Re: XDMCP howto for cygwin? (or other remote-desktop solution)
On 2004.01.30 21:11, Thomas L Roche wrote: * is XDMCP The Way (tm) to do this? If so, I'm assuming (from traffic on the list) that cygwin supports XDMCP, but I'm unclear on * How to do it on cygwin? All the howto's I've seen reference Linux, and I'm also a little unclear on what goes on which end. It's very straightforward. Assuming you have cygwin and xfree installed on a windows box, you edit C:\cygwin\usr\X11R6\bin\startxdmcp.bat to have your windows box IP number in DISPLAY and the Linux box IP number in REMOTE_HOST. Also make sure /etc/X11/gdm/gdm.conf contains [xdmcp] Enable=true GDM has to run on linux, so you need init to go to level 5. Then you can run startxdmcp.bat (I have a shortcut for it on my W2K desktop) to get the login screen for your linux box. Once logged in you get the full Gnome desktop (or KDE if that's your preference). Success, Willem Riede.
Re: XDMCP howto for cygwin? (or other remote-desktop solution)
On 2004.01.30 21:11, Thomas L Roche wrote: I'm assuming (from traffic on the list) that cygwin supports XDMCP, but I'm unclear on * How to do it on cygwin? All the howto's I've seen reference Linux, and I'm also a little unclear on what goes on which end. Willem Riede [EMAIL PROTECTED] 01/30/2004 10:11:59 PM: It's very straightforward. Assuming you have cygwin and xfree installed on a windows box, you edit C:\cygwin\usr\X11R6\bin\startxdmcp.bat to have your windows box IP number in DISPLAY and the Linux box IP number in REMOTE_HOST. OK. BTW, does this mean that this won't work if either is on DHCP? (Fortunately, for my specific case both have static IP.) OK, so all I need on the client ... err, server ... err, cygwin side is just to edit /usr/X11R6/bin/startxdmcp.bat: done. Then I gotta setup G|K|XDM on the ... non-cygwin side: Also make sure /etc/X11/gdm/gdm.conf contains [xdmcp] Enable=true except the box I'm targeting currently only has KDE, so it's /etc/X11/xdm/xdm-config, and I just need to comment out !DisplayManager.requestPort:0 Correct? (But first, I need root to `su` :-) GDM has to run on linux, so you need init to go to level 5. OK. Is there anything else that needs done for KDE? Then you can run startxdmcp.bat (I have a shortcut for it on my W2K desktop) to get the login screen for your linux box. Once logged in you get the full Gnome desktop (or KDE if that's your preference). Sounds easy! Just gotta get access.
RE: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing (RDP)
OK, this is weird: Running with the default drawing engine - If I start XWin locally (and then run fluxbox) in -nodecoration mode on the Windows XP machine, whose screen resolution is 1024x768@32bpp and go to a Windows 2000 machine whose screen resolution is 800x600@32bpp and run RDP client to connect back to the XP box (RDP@MaxRes24bpp), I get the Cygwin screen, but it looks really gross and pixilated... Also the extent of the X screen seems to go beyond the RDP client's borders, and RDP does not permit scrolling the remote desktop Strange... I can disconnect RDP, reconnect RDP, and things don't get better or any worse... 2nd test. I start XWin (fullscreen) in query mode and connect it to a machine running Redhat 7.3. If I go to the Windows 2000 machine and connect to XP, I get XWin's Redhat view, but it looks psychedelic. If go back to the Windows XP box and take back control, I cannot see XWin's output anymore. Instead of a big white square, I get nothing at all, although from what I can tell, I am still in control of the Redhat machine. If I close XWin, go back to the Windows 2000 machine, connect to XP with RDP and start Xwin (query mode), then I get Redhat's login screen and everything is beautiful. I can log in, close the RDP connection to XP, reconnect to XP with RDP, and everything is still hunky-dory. If I go back to the XP machine and retake control by its console, the XWin window is minimized and if I restore it, it is transparent like the test before and will not draw anything even if I am still remotely controlling the Redhat computer. If I then go back to the windows 2000 machine and reconnect to XP with RDP, everything is perfect. XWin draws the Redhat view perfectly. What seems to be the problem here is that the XP machine and the Windows 2000 machine are running at different geometries. XP is 1024x768 and Windows 2000 is running 800x600. It seems like XWin cannot deal with a dynamically changing display size. This is probably a limitation in X, I would bet. So as long as the console manipulating XWin has the same geometry as the one that was in use when XWin was started, XWin is fine. Now to run the same test with XWin -engine 1 If I start XWin locally (and then run fluxbox) in -nodecoration mode on the Windows XP machine, whose screen resolution is 1024x768@32bpp and go to a Windows 2000 machine whose screen resolution is 800x600@32bpp and run RDP client to connect back to the XP box (RDP@MaxRes24bpp), I get the Cygwin screen, and it looks perfect. The extent of the X screen still seems to go beyond the RDP client's borders, and RDP still does not permit scrolling the remote desktop. I can disconnect RDP, reconnect RDP, and Xwin is unaffected and still draws perfectly. 2nd test. I start XWin (fullscreen) in query mode and connect it to a machine running Redhat 7.3. If I go to the Windows 2000 machine and connect to XP, I get XWin's Redhat view, there is a slight dithering effect apparent on the desktop wallpaper, maybe due to the view being converted from 32bpp to 24bpp by RDP. Dithering aside, visually, everything is fine, except for the fact that I cannot see the whole XWin window. If go back to the Windows XP box and take back control, I can still see XWin's output and control the Redhat machine. XWin's colors are fine, but XWin's window has gone from being fullscreen to being about 800x600 and the outer edges of the Redhat screen are now clipped out and lost. Even if I use taskmanager to send a MAXIMIZE command to XWin, there is no effect; I cannot recover the lost display area. If I close XWin, go back to the Windows 2000 machine, connect to XP with RDP and start Xwin (query mode), then I get Redhat's login screen and everything is beautiful. I can log in, close the RDP connection to XP, reconnect to XP with RDP, and everything is still hunky-dory. If I go back to the XP machine and retake control by its console, the XWin window is no longer fullscreen but it is still displaying perfectly and I can still remotely control the Redhat computer. If I then go back to the windows 2000 machine and reconnect to XP with RDP, everything is perfect. XWin is back to being fullscreen (on the smaller 800x600 display) and still draws the Redhat view perfectly. Oddly enough, there were NO dithering artifacts present during this run... Also, I seemed to notice that sometimes, the RDP client seemed to think that the XWin window was busy and would send back the BUSY cursor whenever the mouse was over XWin, but I didn't make a strict analysis of it, and its late. If there are any permutations you'd like me to try, let me know. Jean-Claude -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Harold L Hunt II Sent: Monday, September 09, 2002 12:05 PM To: [EMAIL PROTECTED] Subject: Re: Bug report: Using Cygwin-Xfree through Remote
Re: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing(RDP)
Jean-Claude, Repeat the entire scenario you described, but start XWin with the ``-engine 1'' parameter, e.g. XWin -engine 1 The default graphics engine on Windows 2000/XP will be DirectDraw 4.0; DirectDraw will probably have a problem with RDP --- I am surprised that it works at all. The ``-engine 1'' parameter will tell XWin to use GDI DIBs (Device Independent Bitamps) and regular GDI BLTs (Bit-Block Transfers) as the graphics engine; GDI will be less prone to having a problem with RDP. If RDP works with the GDI engine then I know exactly what to fix; if not, I will have to pump you for some more information. Harold Jean-Claude Gervais wrote: This is complicated, so I'll try to be clear. Let's say you have machine A, which is a Windows XP machine that has Cygwin and Cygwin-XFree installed on it. You use A to connect to B. B is a machine running Linux and X. Everything so far works. Then you use machine C (a machine running Windows 2000) to remote-control machine A with Windows XP Remote Desktop Client (RDP). Machine C can use machine A's Cygwin-XFree connection and view machine B. No problem. However, when machine C breaks its connection to machine A, machine A's Cygwin-XFree will no longer display machine B. It will instead display a white screen in Cygwin-XFree. Although I am pretty sure that A is still connected and controlling B, it can no longer see B's display. It seems like Remote Desktop Client mucks-up Cygwin-XFree. I hope that that was clear enough. Thanks.
Re: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing (RDP)
Sounds similar to this problem I reported a while back... http://www.cygwin.com/ml/cygwin-xfree/2002-06/msg00373.html What's in /tmp/XWin.log? From: Jean-Claude Gervais [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Cygwin-XFree [EMAIL PROTECTED] Subject: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing (RDP) Date: Mon, 09 Sep 2002 11:00:28 -0400 This is complicated, so I'll try to be clear. Let's say you have machine A, which is a Windows XP machine that has Cygwin and Cygwin-XFree installed on it. You use A to connect to B. B is a machine running Linux and X. Everything so far works. Then you use machine C (a machine running Windows 2000) to remote-control machine A with Windows XP Remote Desktop Client (RDP). Machine C can use machine A's Cygwin-XFree connection and view machine B. No problem. However, when machine C breaks its connection to machine A, machine A's Cygwin-XFree will no longer display machine B. It will instead display a white screen in Cygwin-XFree. Although I am pretty sure that A is still connected and controlling B, it can no longer see B's display. It seems like Remote Desktop Client mucks-up Cygwin-XFree. I hope that that was clear enough. Thanks. _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
Re: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing(RDP)
Thomas, Yes, it is similar in that it is likely that some surface is being lost and we are not restoring it. There were several places in the code where I made a decision not to look for lost surfaces because it did not seem that we could ever lose a surface at those points. However, I think that in this case we might actually be losing the offscreen surface, as opposed to the usually lost primary surface, and there is no code in place to look for or restore a lost offscreen surface. It wouldn't be hard to add such code for the DirectDraw engines. Of course, we have to identify the problem first. Harold Thomas Chadwick wrote: Sounds similar to this problem I reported a while back... http://www.cygwin.com/ml/cygwin-xfree/2002-06/msg00373.html What's in /tmp/XWin.log? From: Jean-Claude Gervais [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Cygwin-XFree [EMAIL PROTECTED] Subject: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing (RDP) Date: Mon, 09 Sep 2002 11:00:28 -0400 This is complicated, so I'll try to be clear. Let's say you have machine A, which is a Windows XP machine that has Cygwin and Cygwin-XFree installed on it. You use A to connect to B. B is a machine running Linux and X. Everything so far works. Then you use machine C (a machine running Windows 2000) to remote-control machine A with Windows XP Remote Desktop Client (RDP). Machine C can use machine A's Cygwin-XFree connection and view machine B. No problem. However, when machine C breaks its connection to machine A, machine A's Cygwin-XFree will no longer display machine B. It will instead display a white screen in Cygwin-XFree. Although I am pretty sure that A is still connected and controlling B, it can no longer see B's display. It seems like Remote Desktop Client mucks-up Cygwin-XFree. I hope that that was clear enough. Thanks. _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
RE: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing (RDP)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Thomas Chadwick Sent: Monday, September 09, 2002 12:08 PM To: [EMAIL PROTECTED] Subject: Re: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing (RDP) Sounds similar to this problem I reported a while back... http://www.cygwin.com/ml/cygwin-xfree/2002-06/msg00373.html What's in /tmp/XWin.log? This - ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winAllocateFBShadowDDNL - Not changing video mode winAllocateFBShadowDDNL - lPitch: 4096 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winScreenInit - returning winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 A lot of these deleted, but there were TONS of them. winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 ... More of these lines deleted ... winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 ... More of these lines deleted ... winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 2winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 And on and on... From: Jean-Claude Gervais [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Cygwin-XFree [EMAIL PROTECTED] Subject: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing (RDP) Date: Mon, 09 Sep 2002 11:00:28 -0400 This is complicated, so I'll try to be clear. Let's say you have machine A, which is a Windows XP machine that has Cygwin and Cygwin-XFree installed on it. You use A to connect to B. B is a machine running Linux and X. Everything so far works. Then you use machine C (a machine running Windows 2000) to remote-control machine A with Windows XP Remote Desktop Client (RDP). Machine C can use machine A's Cygwin-XFree connection and view machine B. No problem. However, when machine C breaks its connection to machine A, machine A's Cygwin-XFree will no longer display machine B. It will instead display a white screen in Cygwin-XFree. Although I am pretty sure that A is still connected and controlling B, it can no longer see B's display. It seems like Remote Desktop Client mucks-up Cygwin-XFree. I hope that that was clear enough. Thanks. _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
Re: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing(RDP)
Jean-Claude, How about with -engine 1? Harold Jean-Claude Gervais wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Thomas Chadwick Sent: Monday, September 09, 2002 12:08 PM To: [EMAIL PROTECTED] Subject: Re: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing (RDP) Sounds similar to this problem I reported a while back... http://www.cygwin.com/ml/cygwin-xfree/2002-06/msg00373.html What's in /tmp/XWin.log? This - ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winAllocateFBShadowDDNL - Not changing video mode winAllocateFBShadowDDNL - lPitch: 4096 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winScreenInit - returning winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 A lot of these deleted, but there were TONS of them. winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 ... More of these lines deleted ... winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 ... More of these lines deleted ... winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 2winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 And on and on... From: Jean-Claude Gervais [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Cygwin-XFree [EMAIL PROTECTED] Subject: Bug report: Using Cygwin-Xfree through Remote Desktop Sharing (RDP) Date: Mon, 09 Sep 2002 11:00:28 -0400 This is complicated, so I'll try to be clear. Let's say you have machine A, which is a Windows XP machine that has Cygwin and Cygwin-XFree installed on it. You use A to connect to B. B is a machine running Linux and X. Everything so far works. Then you use machine C (a machine running Windows 2000) to remote-control machine A with Windows XP Remote Desktop Client (RDP). Machine C can use machine A's Cygwin-XFree connection and view machine B. No problem. However, when machine C breaks its connection to machine A, machine A's Cygwin-XFree will no longer display machine B. It will instead display a white screen in Cygwin-XFree. Although I am pretty sure that A is still connected and controlling B, it can no longer see B's display. It seems like Remote Desktop Client mucks-up Cygwin-XFree. I hope that that was clear enough. Thanks. _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
Re: Easy command to launch remote desktop on cygwin-xfree?
This has come up a number of times recently. Look in the archives for July, 2002: http://cygwin.com/ml/cygwin-xfree/2002-07 Search for the following subjects: scripting using Xterm ssh need help scripting multiple xfree startups Your help please... From: CRAIG SETERA [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Easy command to launch remote desktop on cygwin-xfree? Date: Thu, 08 Aug 2002 14:46:49 -0400 I've already tried all of the different HOWTO's to try and get XDM going without any success. That was why I was hoping someone could give me a command or two to get it going via SSH forwarding. Thanks, Craig _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
Re: Easy command to launch remote desktop on cygwin-xfree?
CRAIG SETERA wrote:
I've already tried all of the different HOWTO's to try and get XDM going
without any success. That was why I was hoping someone could give me a
command or two to get it going via SSH forwarding.
Thanks,
Craig
just hacked this out... it isn't ideal and requires... modification of
the source...
it's based off an old x example xxterm.c, which was in the kdevelop examples
modify the machines at the beginning to your network
gcc -I/usr/X11R6/include -L/usr/X11R6/lib -o sxterm sxterm.c -lX11
./xsterm
it has 2 arguments, username and remote_command
if you want to run things w/ 2 different usernames you might fix it..
or run xsterm twice :)
oh my
command line parsing is badness, and if you want to use option 2, you
should also provide option 1
ie this works for me
xsterm matt /usr/X11R6/bin/xeyes
/***
* Purpose: To provide a tool that allows people to login to machines.
*
* Compile: Edit BUTTONS- Number of machines.
* Edit XTERM - Location of the xterm command.
* Edit 'machines' - Names of the machines.
*
* Compile command for Linux and Sun
*
* gcc xxterm.c -o xxterm -lX11
* User notes:
* This is only of use to people running UNIX boxes on a LAN.
*
* History:
*
* Rev Date Author Comments.
* --- -- -
* 1.0 30-May-95 MJLInital Release.
*/
/** Includes /
/* These are in /usr/X386 */
#include X11/Xlib.h
#include X11/Xutil.h
#include X11/Xos.h
#include X11/X.h
#include stdio.h
#include unistd.h /* setuid */
/** Defines */
#define BUTTONS 7 /* --- number of machines. */
/* V--- Location of the xterm comnd */
#define XTERM xterm -sb -e ssh
/* window background colour */
#define BACKGROUND_COLOUR light grey
#define BUTTON_COLOUR blue
#define DOWN down
#define ACTIVE active
/** Global Variables /
int has_user_name = 0;
int has_remote_command = 0;
char *user_name = matt;
char *remote_command = ;
Display *display;
int screen;
Colormap colormap;
/* Machines you want to access */
char * machines[] = {
foo,
bar,
baz,
blah,
bah,
humbug,
boo
};
char * commands[] =
{
xterm -sb -e ssh
};
/** Structures **/
/* Hold the co-ordinates of the buttons */
struct {
XPoint topleft;
XPoint topright;
XPoint botleft;
XPoint botright;
} buttons[BUTTONS+1];
struct window_info
{
Window win;
GC gc;
};
/** Functions ***/
void init_buttons(char *button_caps[]);
void draw_image (Window, GC *, char *button_caps[]);
int draw_button
(Window,
GC *gc,
char *text,/* Text to put on screen button cap */
int x, int y, /* Position of button in window */
int width, int height,
int,
char button_caps[]);
/* Change the colour in the graphics
* context.
*/
void set_colour (GC *gc, char *, Colormap);
int where_am_i (Window, GC *gc);
/* Take an action based on the
* button ID.
*/
int process_button
(Window win,
GC *gc,
char *button_caps[],
int button); /* Button ID. */
void press_button
(Window,
GC *gc,
char *button_caps[],
char *text );
struct window_info create_window
(int x, /* Window size */
int y);
/* Execute system commands */
void execute_command
(int root, /* 1 == must be run by root
* 0 == Can be run by anyone*/
char *command, /* Command */
char *machine);
//
int main(int argc, char **argv)
{
unsigned int width;
unsigned int height; /* Size of the window. */
int x=0, y=0; /* x is across, y is down! */
unsigned int border_width=4; /* Window border. */
/* Array of pointers, one for each screen
* button, they point to a string constant
* describing their status, active, down,
* inactive
*/
char *button_caps[BUTTONS+1];
struct window_info window;
Window win;
GC gc;
XEvent report;
XFontStruct *font_info;
XColor colour;
char * display_name=NULL;
Re: Easy command to launch remote desktop on cygwin-xfree?
CRAIG SETERA wrote:
I've already tried all of the different HOWTO's to try and get XDM going
without any success. That was why I was hoping someone could give me a
command or two to get it going via SSH forwarding.
Thanks,
Craig
just hacked this out... it isn't ideal and requires... modification of
the source...
it's based off an old x example xxterm.c, which was in the kdevelop
examples
modify the machines at the beginning to your network
gcc -I/usr/X11R6/include -L/usr/X11R6/lib -o xsterm xsterm.c
./xsterm
it has 2 optional arguments, username and remote_command
if you want to run things w/ 2 different usernames you might fix it..
or run xsterm twice :)
/***
* Purpose: To provide a tool that allows people to login to machines.
*
* Compile: Edit BUTTONS- Number of machines.
* Edit XTERM - Location of the xterm command.
* Edit 'machines' - Names of the machines.
*
* Compile command for Linux and Sun
*
* gcc xxterm.c -o xxterm -lX11
* User notes:
* This is only of use to people running UNIX boxes on a LAN.
*
* History:
*
* Rev Date Author Comments.
* --- -- -
* 1.0 30-May-95 MJLInital Release.
*/
/** Includes /
/* These are in /usr/X386 */
#include X11/Xlib.h
#include X11/Xutil.h
#include X11/Xos.h
#include X11/X.h
#include stdio.h
#include unistd.h /* setuid */
/** Defines */
#define BUTTONS 7 /* --- number of machines. */
/* V--- Location of the xterm comnd */
#define XTERM xterm -sb -e ssh
/* window background colour */
#define BACKGROUND_COLOUR light grey
#define BUTTON_COLOUR blue
#define DOWN down
#define ACTIVE active
/** Global Variables /
int has_user_name = 0;
int has_remote_command = 0;
char *user_name = matt;
char *remote_command = ;
Display *display;
int screen;
Colormap colormap;
/* Machines you want to access */
char * machines[] = {
foo,
bar,
baz,
blah,
bah,
humbug,
boo
};
char * commands[] =
{
xterm -sb -e ssh
};
/** Structures **/
/* Hold the co-ordinates of the buttons */
struct {
XPoint topleft;
XPoint topright;
XPoint botleft;
XPoint botright;
} buttons[BUTTONS+1];
struct window_info
{
Window win;
GC gc;
};
/** Functions ***/
void init_buttons(char *button_caps[]);
void draw_image (Window, GC *, char *button_caps[]);
int draw_button
(Window,
GC *gc,
char *text,/* Text to put on screen button cap */
int x, int y, /* Position of button in window */
int width, int height,
int,
char button_caps[]);
/* Change the colour in the graphics
* context.
*/
void set_colour (GC *gc, char *, Colormap);
int where_am_i (Window, GC *gc);
/* Take an action based on the
* button ID.
*/
int process_button
(Window win,
GC *gc,
char *button_caps[],
int button); /* Button ID. */
void press_button
(Window,
GC *gc,
char *button_caps[],
char *text );
struct window_info create_window
(int x, /* Window size */
int y);
/* Execute system commands */
void execute_command
(int root, /* 1 == must be run by root
* 0 == Can be run by anyone*/
char *command, /* Command */
char *machine);
//
int main(int argc, char **argv)
{
unsigned int width;
unsigned int height; /* Size of the window. */
int x=0, y=0; /* x is across, y is down! */
unsigned int border_width=4; /* Window border. */
/* Array of pointers, one for each screen
* button, they point to a string constant
* describing their status, active, down,
* inactive
*/
char *button_caps[BUTTONS+1];
struct window_info window;
Window win;
GC gc;
XEvent report;
XFontStruct *font_info;
XColor colour;
char * display_name=NULL;
/*
*
* Setup the window environment
*
*/
if (argc =2) {
if
