Often lose window decoration when restore from standby

Often lose window decoration when restore from standby

[KARR, DAVID (ATTCINW)]

I'm using Cygwin 1.5.25 on WinXPSP2, along with Cygwin-built GNU Emacs
23.0.92.1.

I run startxwin.bat on system startup.  After it comes up, I run Emacs,
and I get a good window with normal Windows-based window decorations.
My Windows shortcut does this:

   C:\cygwin\bin\rxvt.exe -geometry 1x1 -ls -cd c:\cygwin\home\dk068x -e
/usr/bin/bash -l -c /usr/bin/emacs

I often find that after I restore from Standby, I see an odd symptom, in
that the Emacs window no longer has any window decorations.  The edge of
the Emacs menu bar is the edge of the window.  If I kill the Emacs
process and start it again from the shortcut, even that doesn't fix it.
What fixes it is killing the Xwin process, rerunning startxwin.bat, and
then rerunning Emacs.

--
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: Often lose window decoration when restore from standby

[Jon TURNEY]

On 13/07/2009 20:35, KARR, DAVID (ATTCINW) wrote:
> I'm using Cygwin 1.5.25 on WinXPSP2, along with Cygwin-built GNU Emacs
> 23.0.92.1.
>
> I run startxwin.bat on system startup.  After it comes up, I run Emacs,
> and I get a good window with normal Windows-based window decorations.
> My Windows shortcut does this:
>
>     C:\cygwin\bin\rxvt.exe -geometry 1x1 -ls -cd c:\cygwin\home\dk068x -e
> /usr/bin/bash -l -c /usr/bin/emacs
>
> I often find that after I restore from Standby, I see an odd symptom, in
> that the Emacs window no longer has any window decorations.  The edge of
> the Emacs menu bar is the edge of the window.  If I kill the Emacs
> process and start it again from the shortcut, even that doesn't fix it.
> What fixes it is killing the Xwin process, rerunning startxwin.bat, and
> then rerunning Emacs.

Very interesting, but I'm afraid I can't reproduce this problem.

Does this only affect emacs? or all X windows?

This might be caused by the internal WM thread not being able to talk to the 
server anymore after a resume, but I would have thought that would cause the 
whole process to terminate...

Can I see a /var/log/Xwin.0.log, please?

--
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: Often lose window decoration when restore from standby

[KARR, DAVID (ATTCINW)]

[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]

> -----Original Message-----
> From: Jon TURNEY [mailto:jon.turney@dronecode.org.uk]
> Sent: Wednesday, July 15, 2009 10:52 AM
> To: cygwin-xfree@cygwin.com
> Cc: KARR, DAVID (ATTCINW)
> Subject: Re: Often lose window decoration when restore from standby
> 
> On 13/07/2009 20:35, KARR, DAVID (ATTCINW) wrote:
> > I'm using Cygwin 1.5.25 on WinXPSP2, along with Cygwin-built GNU
> Emacs
> > 23.0.92.1.
> >
> > I run startxwin.bat on system startup.  After it comes up, I run
> Emacs,
> > and I get a good window with normal Windows-based window
decorations.
> > My Windows shortcut does this:
> >
> >     C:\cygwin\bin\rxvt.exe -geometry 1x1 -ls -cd
> c:\cygwin\home\dk068x -e
> > /usr/bin/bash -l -c /usr/bin/emacs
> >
> > I often find that after I restore from Standby, I see an odd
symptom,
> in
> > that the Emacs window no longer has any window decorations.  The
edge
> of
> > the Emacs menu bar is the edge of the window.  If I kill the Emacs
> > process and start it again from the shortcut, even that doesn't fix
> it.
> > What fixes it is killing the Xwin process, rerunning startxwin.bat,
> and
> > then rerunning Emacs.
> 
> Very interesting, but I'm afraid I can't reproduce this problem.
> 
> Does this only affect emacs? or all X windows?
> 
> This might be caused by the internal WM thread not being able to talk
> to the
> server anymore after a resume, but I would have thought that would
> cause the
> whole process to terminate...
> 
> Can I see a /var/log/Xwin.0.log, please?

Attached is the latest XWin.0.log, after I noticed the window
decorations gone again.  I'm not sure if it's happening with other X
apps.  This is the only one I use right now.


[-- Attachment #2: XWin.0.log --]
[-- Type: application/octet-stream, Size: 3085 bytes --]

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.5.3.0 (20090222)
Contact: cygwin-xfree@cygwin.com
XWin was started with the following command line:

/usr/bin/XWin -multiwindow -clipboard -silent-dup-error 

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1440 h 900
winInitializeDefaultScreens - Returning
(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
winPrefsLoadPreferences: /etc/X11/system.XWinrc
LoadPreferences: Done parsing the configuration file...
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
winInitNotifyIcon - Shell_NotifyIcon Failed
winAllocateFBShadowGDI - Creating DIB with width: 1440 height: 900 depth: 32
winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32
null screen fn ReparentWindow
null screen fn RestackWindow
InitQueue - Calling pthread_mutex_init
InitQueue - pthread_mutex_init returned
InitQueue - Calling pthread_cond_init
InitQueue - pthread_cond_init returned
winInitMultiWindowWM - Hello
winInitMultiWindowWM - Calling pthread_mutex_lock ()
winMultiWindowXMsgProc - Hello
Screen 0 added at XINERAMA coordinate (0,0).
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
MIT-SHM extension disabled due to lack of kernel support
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(--) 16 mouse buttons found
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000409" (00000409) 
(--) Using preset keyboard for "English (USA)" (409), type "4"
winInitMultiWindowWM - pthread_mutex_lock () returned.
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5
\fwinMultiWindowXMsgProc - Could not open display, try: 1, sleeping: 5
\fwinInitMultiWindowWM - Could not open display, try: 2, sleeping: 5
\fwinMultiWindowXMsgProc - Could not open display, try: 2, sleeping: 5
\fwinInitMultiWindowWM - Could not open display, try: 3, sleeping: 5
\fwinMultiWindowXMsgProc - Could not open display, try: 3, sleeping: 5
\fwinInitMultiWindowWM - Could not open display, try: 4, sleeping: 5
\fwinMultiWindowXMsgProc - Could not open display, try: 4, sleeping: 5
\fwinInitMultiWindowWM - Could not open display, try: 5, sleeping: 5
\fwinMultiWindowXMsgProc - Could not open display, try: 5, sleeping: 5
\fwinInitMultiWindowWM - Failed opening the display.  Exiting.
winMultiWindowXMsgProc - Failed opening the display.  Exiting.
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.

[-- Attachment #3: Type: text/plain, Size: 223 bytes --]

--
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: Often lose window decoration when restore from standby

[Jon TURNEY]

>> On 13/07/2009 20:35, KARR, DAVID (ATTCINW) wrote:
>>> I often find that after I restore from Standby, I see an odd symptom,
>>> in that the Emacs window no longer has any window decorations. The edge
>>> of the Emacs menu bar is the edge of the window. If I kill the Emacs
>>> process and start it again from the shortcut, even that doesn't fix
>>> it. What fixes it is killing the Xwin process, rerunning startxwin.bat,
>>> and then rerunning Emacs.

I assumed that this meant you resume from standby with X server and emacs 
running and see this behaviour, but I'm having a little difficulty reconciling 
that with the log below, so can you clarify if I've understood correctly.

>> This might be caused by the internal WM thread not being able to talk to
>> the server anymore after a resume, but I would have thought that would
>> cause the whole process to terminate...

Well, in fact it seems that this isn't treated as a fatal error, but perhaps 
it should be...

>> Can I see a /var/log/Xwin.0.log, please?
>
> Attached is the latest XWin.0.log, after I noticed the window
> decorations gone again.  I'm not sure if it's happening with other X
> apps.  This is the only one I use right now.

Thanks.

Hmm... well, this is not as easy as it might be to interpret (I need to find 
my patch to add timestamps to the log and make it work properly...), but this 
looks like the multiwindow mode internal WM client isn't able to connect to 
the X server at all.

winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5
winMultiWindowXMsgProc - Could not open display, try: 1, sleeping: 5
winInitMultiWindowWM - Could not open display, try: 2, sleeping: 5
winMultiWindowXMsgProc - Could not open display, try: 2, sleeping: 5
winInitMultiWindowWM - Could not open display, try: 3, sleeping: 5
winMultiWindowXMsgProc - Could not open display, try: 3, sleeping: 5
winInitMultiWindowWM - Could not open display, try: 4, sleeping: 5
winMultiWindowXMsgProc - Could not open display, try: 4, sleeping: 5
winInitMultiWindowWM - Could not open display, try: 5, sleeping: 5
winMultiWindowXMsgProc - Could not open display, try: 5, sleeping: 5
winInitMultiWindowWM - Failed opening the display.  Exiting.
winMultiWindowXMsgProc - Failed opening the display.  Exiting.

Normally you should get lines like:

winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the 
display.
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the 
display.

So I'm a bit baffled as to how your windows are getting decorated at all...

--
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/