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=00000000 ebx=0000005F ecx=0022CA90 edx=0084BAF0 > esi=000001C3 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=0000 > ss=0023 Stack trace: > Frame Function Args > 0022CAC8 00410C8C (0084C008, 0084E5A0, 00000000, 005D05A8) > 0022CAE8 004D2EE0 (0084C008, 0022CB54, 005D05A8, 005D05A8) > 0022CB18 004E147E (0022CB54, 005D05A8, 00000001, 0022CB90) > 0022CBF8 0053544C (00906B40, 00000000, 00000000, 01A00023) > 0022CC48 00500E7B (00843360, 00000002, 00000000, 004DCCC9) > 0022CC98 004DD08B (00000003, 008424D0, 00840090, 61166990) > 0022CD98 61006148 (00000000, 0022CDD0, 610054C0, 0022CDD0) > 610054C0 61004416 (0000009C, A02404C7, E8611001, FFFFFF48) > 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/