Hi:
so just a quick follow up. The patch and the update work great as far as
maple is concerned... I have not experienced maple not loading properly
since the switch.
I do see however a small issue with 'Iconify off' on some windows (but the
issue is probably deeper).
Say I iconify a window, and later use CM+q to bring it back with this:
AddToFunc DeiconifyAndRaise
+ I Iconify off
+ I Raise
Key q A CM WindowList (Iconic, CurrentPage) Function DeiconifyAndRaise
my session will log me out (i.e. fvwm gets instantly killed).
This is only a problem for some windows... for example xterm, gvim work
fine.. but firefox, gnome-control-center, etc.. will cause this problem.
I noticed, that if I call FvwmIdent on the windows that do cause this
issue, nothing will be shown.
The problem is also present with the latest cvs version (with no patch
applied), but goes away if i switch to say 2.6.5.
I attach a log for such a case below.
cheers
On Tue, Sep 16, 2014 at 3:35 PM, Dominik Vogt <[email protected]> wrote:
> Peter,
>
> How does the attached experimental patch work for you?
>
> Ciao
>
> Dominik ^_^ ^_^
>
> --
>
> Dominik Vogt
>
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 741 requests (741 known processed) with 0 events remaining.
(dropbox:2160): Gdk-WARNING **: GdkWindow 0x24000bd unexpectedly destroyed
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 20270 requests (20270 known processed) with 1 events remaining.
(nm-applet:2118): Gdk-WARNING **: GdkWindow 0x2200006 unexpectedly destroyed
** Message: applet now removed from the notification area
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 10 (X_UnmapWindow)
Resource id: 0x1a00136
The program 'dropbox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
(Details: serial 1193 error_code 9 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
X Error: RenderBadPicture (invalid Picture parameter) 174
Extension: 152 (RENDER)
Minor opcode: 7 (RenderFreePicture)
Resource id: 0x260
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 18 (X_ChangeProperty)
Resource id: 0x1a00136
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 4 (X_DestroyWindow)
Resource id: 0x1a00136
(nm-applet:2118): Gdk-WARNING **: The program 'nm-applet' received an X Window
System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 357 error_code 3 request_code 18 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 1425 requests (1421 known processed) with 0 events remaining.
SpiderOak: Fatal IO error: client killed
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X
server ":0"
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X
server ":0"
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X
server ":0"
(gnome-settings-daemon:1498): Gdk-WARNING **: gnome-settings-daemon: Fatal IO
error 11 (Resource temporarily unavailable) on X server :0.
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X
server ":0"
gnome-settings-daemon: no process found
