fvwm with java yet again (maple process)

[Peter G]

Hi:

my issue seems similar to the one presented here:
https://www.mail-archive.com/fvwm-workers@fvwm.org/msg03376.html
but with maple.

In most cases opening and using maple works fine, but with some worksheets,
in particular those that may contain many plots, fvwm "freezes" when maple
is loading. The fvwm process runs at 100% on a single core. Maple is
actually usable, that is I can type in it and letters show up, but the
mouse is not, and I am not able to control other clients. In order to make
fvwm usable again, I have to kill all the maple processes (java, mserver).
Then, usually after a minute or more, fvwm is responsive again.

I am on ubuntu 12.04 64-bit, and this behavior is consistent across 3
different machines.

I've checked 2.6.5 and the cvs versions of fvwm and observe the same
problem. I have also tried countless combinations of possible Style
settings from "Lenient" to various focus policies.

Attaching to the fvwm process with a debugger it would seem that fvwm is
just stuck in the main loop, and waiting for x events when this happens.

I should note that things work fine with (for example) gnome, but as the
maple worksheet is loading, for a couple of seconds the window manager also
"stops" (meaning one can't for example move another window), but comes back
right after the document has loaded.

Now, I get that this is an issue with java, but realistically the chances
that this will get sorted out by maplesoft in any active way is zero (I am
a participant in their beta program). I really mean ZERO - it's not going
to happen.

So my question would be if anyone would have an idea how one would overcome
something like this (i.e. do whatever it is that say gnome is doing in
order to not let a java process put it in a funny state). I realize it
would be a dirty hack, and would maybe break protocol, but quite frankly
the only other solution for me is not using fvwm at all.

I don't know the code base well yet, but would be happy to  play with
things to try to get this sorted out. So if anyone has any ideas, it would
be appreciated. The more detailed the better...(i.e if you know what
files/code would be involved, and what would have to be changed, that would
be very helpful).

thanks!

Re: fvwm with java yet again (maple process)

[Peter G]

>
> So attach gdb to the fvwm process and show a backtrace of what fvwm is
> doing.
>
> -- Thomas Adam
>
>

I show the backtrace below (at the bottom). As I mentioned fvwm is just
stuck in the main event loop.



$sudo gdb ./fvwm/install/bin/fvwm 18419
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /home/user/fvwm/install-cvs-2.6/bin/fvwm...done.
Attaching to program: /home/user/fvwm/install-cvs-2.6/bin/fvwm, process
18419
Reading symbols from /usr/lib/x86_64-linux-gnu/libXft.so.2...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libXft.so.2
Reading symbols from /usr/lib/x86_64-linux-gnu/libXpm.so.4...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libXpm.so.4
Reading symbols from /usr/lib/libstroke.so.0...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libstroke.so.0
Reading symbols from /usr/lib/x86_64-linux-gnu/libSM.so.6...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libSM.so.6
Reading symbols from /usr/lib/x86_64-linux-gnu/libICE.so.6...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libICE.so.6
Reading symbols from /usr/lib/x86_64-linux-gnu/libXinerama.so.1...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libXinerama.so.1
Reading symbols from /usr/lib/x86_64-linux-gnu/libXext.so.6...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libXext.so.6
Reading symbols from /usr/lib/x86_64-linux-gnu/libX11.so.6...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libX11.so.6
Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...(no debugging
symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libm.so.6
Reading symbols from /usr/lib/x86_64-linux-gnu/libXrender.so.1...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libXrender.so.1
Reading symbols from /usr/lib/x86_64-linux-gnu/libXcursor.so.1...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libXcursor.so.1
Reading symbols from /usr/lib/libfribidi.so.0...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libfribidi.so.0
Reading symbols from /lib/x86_64-linux-gnu/libpng12.so.0...(no debugging
symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libpng12.so.0
Reading symbols from /usr/lib/x86_64-linux-gnu/librsvg-2.so.2...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/librsvg-2.so.2
Reading symbols from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Reading symbols from /usr/lib/x86_64-linux-gnu/libcairo.so.2...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libcairo.so.2
Reading symbols from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...(no debugging
symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libc.so.6
Reading symbols from /usr/lib/x86_64-linux-gnu/libfreetype.so.6...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libfreetype.so.6
Reading symbols from /lib/x86_64-linux-gnu/libuuid.so.1...(no debugging
symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libuuid.so.1
Reading symbols from /usr/lib/x86_64-linux-gnu/libxcb.so.1...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libxcb.so.1
Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2...(no debugging
symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libdl.so.2
Reading symbols from /usr/lib/x86_64-linux-gnu/libXfixes.so.3...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libXfixes.so.3
Reading symbols from /lib/x86_64-linux-gnu/libz.so.1...(no debugging
symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libz.so.1
Reading symbols from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
Reading symbols from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Reading symbols from /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0

Re: fvwm with java yet again (maple process)

[Peter G]

thanks taking the time to look at this, and for the pointers!


On Sun, Sep 14, 2014 at 7:26 AM, Dominik Vogt  wrote:

> Could you place printfs in events.c in the My_XNextEvent() function
> and print out the event type?  That should identify the mass of
> events that are coming in, probably just the PropertyNotify from
> the stack trace, but maybe more.
>
> Then put printfs all over the responsible Handle()
> functions to print out the exact contents of the events and how
> fvwm reacts to them.  You can find descriptions of the various
> event types in the event union by searching for "X11 event
> structure" on the net.
>
>
yes, will do that and will look at dispatch_event() as you suggest in your
other email and post back.

In the man time, could you please verify that it's best that I play with
the cvs version of the code? (as opposed to say 2.6.5, or maybe the
github's repo here https://github.com/ThomasAdam/fvwm)?

thanks.

Re: fvwm with java yet again (maple process)

[Peter G]

Hi:

Here is an update. To play with things I have been using the 2.6 branch
from the cvs.

First, let me note that even with the same maple worksheet, from time to
maple loads correctly (this is without any obvious changes to anything). In
that case, I can see all the cores of my CPU spike up for a few seconds,
but then they all settle. When I see the problem, all the cores spike up,
then all except one die down.. that one stays at 100% as described earlier
and it's the fvwm process that is using the cpu. Also, not sure if this is
anecdotal, but it would seem like the more i force fvwm to print debug
info, the more likely maple loads correctly.

Could you place printfs in events.c in the My_XNextEvent() function
> and print out the event type?  That should identify the mass of
> events that are coming in, probably just the PropertyNotify from
> the stack trace, but maybe more.
>
> Then put printfs all over the responsible Handle()
> functions to print out the exact contents of the events and how
> fvwm reacts to them.  You can find descriptions of the various
> event types in the event union by searching for "X11 event
> structure" on the net.
>

I've added some printfs, in My_XNextEvent(), dispatch_event() and
HandlePropertyNotify(). So the event when the problem occurs, seems to
always be PropertyNotify. The rough output should be self explanatory... So
as I start maple in a case where things break, I see:


My_XNextEvent: event type 28
dispatch_event: event type 28
HandlePropertyNotify: beginning
HandlePropertyNotify: switch XA_WM_ICON_NAME
My_XNextEvent: event type 28
dispatch_event: event type 28
HandlePropertyNotify: beginning
HandlePropertyNotify: switch XA_WM_NAME
My_XNextEvent: event type 28
dispatch_event: event type 28
HandlePropertyNotify: beginning
HandlePropertyNotify: switch default
HandlePropertyNotify: ruturn  natural
My_XNextEvent: event type 28
dispatch_event: event type 28
HandlePropertyNotify: beginning
HandlePropertyNotify: switch default

Here the output the ~/.xsession-errors stops (not always on the same
statement)...  I then switch to a different terminal, and kill maple, java,
mserver. Then switch back. Get:

(gnome-settings-daemon:18525): color-plugin-WARNING **: Done switch to new
account, reload devices


Then after a little while, 10s of thousands of events are quickly dumped
like so:


HandlePropertyNotify: ruturn  natural
My_XNextEvent: event type 28
dispatch_event: event type 28
HandlePropertyNotify: beginning
HandlePropertyNotify: return if (XGetGeometry(...
My_XNextEvent: event type 28
dispatch_event: event type 28
HandlePropertyNotify: beginning
HandlePropertyNotify: return if (XGetGeometry(...
My_XNextEvent: event type 28
dispatch_event: event type 28
HandlePropertyNotify: beginning
HandlePropertyNotify: return if (XGetGeometry(...
My_XNextEvent: event type 28

This goes on for a while... what it tells me is that in
HandlePropertyNotify() every event ends up returning in this bit of code:

if (XGetGeometry(
dpy, FW_W(fw), &JunkRoot, &JunkX, &JunkY,
(unsigned int*)&JunkWidth, (unsigned int*)&JunkHeight,
(unsigned int*)&JunkBW, (unsigned int*)&JunkDepth) == 0)
{
return;
}

When things load correctly I don't see this return path from
HandlePropertyNotify().
Any ideas how to get around this?



> More evidence that the application probably generates too many
> events.  Have you tried sitting the situation out?  Do things go
> back to normal after, say, five minutes?
>
>
Yes, if I leave things alone (and not kill maple), fvwm comes back to life
after 10+ minutes (this is without no debugging turned on). So I suppose
that would be consistent with your theory... at some stage fvwm finishes
"processing" all the events.


thanks

Re: fvwm with java yet again (maple process)

[Peter G]

> > dispatch_event: event type 28
> > HandlePropertyNotify: send_event 0, window 0x2e00043, atom 133
> '_NET_WM_NAME', time 187328, state 0
> > dispatch_event: event type 28
> > HandlePropertyNotify: send_event 0, window 0x2e00043, atom 25
> 'WM_ICON_NAME', time 187328, state 0
> > dispatch_event: event type 28
> > HandlePropertyNotify: send_event 0, window 0x2e00043, atom 132
> '_NET_WM_ICON_NAME', time 187328, state 0
> > dispatch_event: event type 28
> > HandlePropertyNotify: send_event 0, window 0x2e00043, atom 27 'WM_NAME',
> time 187682, state 0
>
> Are these four types of PropertyNotify the only ones until the end
> of the log (I care only about massive occurences of others, not
> just a few stray ones)?
>
>
yup, there are ~60k occurrences of each.



> So, the application tries to change its window's and icon's names
> like crazy while loading.  Probably every time it loads some
> element from a file.  Does it display some kind of complexity
> counter in its title?
>
>
the tile is not visibly changing (maybe it's updating to the same thing
though?)  as the worksheet loads. I have not seen this with empty files, so
it would seem like the complexity of a maple worksheet may have something
to do with this issue... I could check what/how-many events are generated
when I load an empty/simple one.



> I'll think about how to get the allication under control tomorrow.
>
>
thanks!

Re: fvwm with java yet again (maple process)

[Peter G]

they are running on the same machine.
About to send you the log with the second round of changes.

On Sun, Sep 14, 2014 at 9:14 PM, Dominik Vogt  wrote:

> Hm, are fvwm and/or the application running on the same machine as
> the X server or over a network?
>
> Ciao
>
> Dominik ^_^  ^_^
>
> --
>
> Dominik Vogt
>
>

Re: fvwm with java yet again (maple process)

[Peter G]

> > around line 246 i skip a lot of the same events...
> >
> > then after line 511 i kill maple.
>
> I assume you mean line 411?
>
>
no, i really mean 511. Whenever you see a like like:

(gnome-settings-daemon:2443): color-plugin-WARNING **: Done switch to new
account, reload devices

that's when I switch to a different terminal.


> > ..things now come back quickly - seems you're "flushing" the left over
> > events.
>
> Hrm, I just added another flush call in the case XGetGeometry()
> fails.  I wonder why that catches 26k events per atom, when before
> the application was killed it weeded out only between 1 and 50
> events per call.
>
> When you run "top", you see only fvwm using a noticeable amount of
> cpu, and not the application?
>
>
correct:
2337 me  20   0  145m  37m 5216 R  100  0.2   4:14.07 fvwm



> Tomorrow I'll write my own application that generates these events.
> I hope with that I can debug the situation myself.
>
>
ok...i suppose you don't have access to maple 18? if so, i could send you
the worksheet that causes this.

thanks.

Re: fvwm with java yet again (maple process)

[Peter G]

> Can you please try out the latest cvs code wogether with the debug
> patch attached to this message?  I need to see some stretch of the
> log again (only the part with the ..._NAME atoms, the rest is
> irrelevant).
>
>

Thanks for the update and the patch.
Unfortunately it's not working form me. A clean checkout of the cvs,
branch-2_6, either with the patch or no patch applied. As fvwm loads, one
cpu spins up and stays at 100%. I can move the mouse, but have no control
of anything. So can't test maple, as can't properly load the fvwm.

here's is xsessions-errors as things are loading. I will try with maybe a
more trivial config.

me@mycomp~/fvwm$ tail -f ~/.xsession-errors
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 12b
'_NET_ACTIVE_WINDOW', time 618714701, state 0
no fw

(gnome-settings-daemon:26197): power-plugin-WARNING **: gnome-session is
not available
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-RhigLu/pkcs11:
No such file or directory

** (process:26212): WARNING **:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files

** (gnome-settings-daemon:26197): WARNING **: Unable to register client:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files
[FvwmPrint][StartFunction]: Loading AppIconMan
[FvwmPrint][StartFunction]: Loading ButtonsTopBar
[FvwmPrint][StartFunction]: Loading ButtonsControl
[FvwmPrint][StartFunction]: Hacks with Wait/consoles...
dispatch_event: event 19
dispatch_event: event 19
dispatch_event: event 18
dispatch_event: event 17
dispatch_event: event 18
dispatch_event: event 17
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 17
'RESOURCE_MANAGER', time 618714881, state 0
no fw
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 15c
'XKLAVIER_ALLOW_SECONDARY', time 618714921, state 0
no fw
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 15d
'_XKB_RULES_NAMES_BACKUP', time 618714927, state 0
no fw
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 11f
'_XKB_RULES_NAMES', time 618714945, state 0
no fw
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 34
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 166 '_ICC_PROFILE',
time 618715379, state 0
no fw
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 168
'_ICC_PROFILE_IN_X_VERSION', time 618715379, state 0
no fw
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 1cc
'_NET_CLIENT_LIST', time 618716218, state 0
no fw
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 1cd
'_NET_CLIENT_LIST_STACKING', time 618716218, state 0
no fw
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 203
'_WIN_CLIENT_LIST', time 618716218, state 0
no fw
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 1cc
'_NET_CLIENT_LIST', time 618716218, state 0
no fw
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 1cd
'_NET_CLIENT_LIST_STACKING', time 618716218, state 0
no fw
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 203
'_WIN_CLIENT_LIST', time 618716218, state 0
no fw
dispatch_event: event 23
dispatch_event: event 23
dispatch_event: event 20
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-RhigLu/pkcs11:
No such file or directory
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-RhigLu/pkcs11:
No such file or directory
dispatch_event: event 21
dispatch_event: event 21
dispatch_event: event 21
dispatch_event: event 21
dispatch_event: event 21
dispatch_event: event 20
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x260, atom 1cd
'_NET_CLIENT_LIST_STACKING', time 618716248, state 0
no fw
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x121, atom 136
'_NET_WM_STATE', time 618716256, state 0
EWMH property notify?
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x121, atom 130
'_NET_WM_DESKTOP', time 618716256, state 0
EWMH property notify?
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x121, atom 1d1
'_NET_WM_ALLOWED_ACTIONS', time 618716256, state 0
EWMH property notify?
dispatch_event: event 28
HandlePropertyNotify: send_event 0, window 0x121, atom 1d0
'_KDE_NE

Re: fvwm with java yet again (maple process)

[Peter G]

On Tue, Sep 16, 2014 at 2:52 PM, Dominik Vogt  wrote:

> If I disable the debug output, fvwm can throw away 40
> alternating PropertyNotify events for WM_NAME and WM_ICON_NAME in
> about 30 seconds at about 35% cpu (on my machine, of course).  Not
>

This would probably already make a broken maple startup usable (in this
particular case).. I think we were seeing something like ~60k * 4 events
when things went bad 15seconds would be better than 10+ minutes.


>
> I see several possible ways to improve this:
>
> 1) Try to erase events even faster.  Maybe the predicate procedure
>that browses through the events could change their destination
>window to some fvwm internal window so when the events are read
>they can be recognized and dropped immediately.  This would be
>an evil hack and may not work.
>
> 2) Add a style option to unsubscribe from PropertyNotify events
>after a couple have been read (to allow the application to set
>some hints at startup).
>
> 3) Unsubscribe PropertyNotify events when fvwm detects that the
>application is going crazy.  May be very difficult to detect
>automatically, and when this finally kicks in it may be too
>late.  There's no way to get rid of unwanted events that are
>already on the input queue quickly.
>
>
Probably 2 would be the easiest to implement? ... and is probably least
evil as it I guess there would be little impact on other apps that can
behave themselves. Maybe this style option could take a number of events it
should tolerate before unsubscribing. Also, maybe another input could be a
time interval, over which the events would be disregarded... so that after
this time elapses, the application would start responding to the
PropertyNotify again.


I would be really interesting to see how gnome (metacity?) seems to deal
with this - I can try to see if there is anything obvious in their code.

Re: fvwm with java yet again (maple process)

[Peter G]

On Tue, Sep 16, 2014 at 3:35 PM, Dominik Vogt  wrote:

> How does the attached experimental patch work for you?
>
>
So far it seems to work!... I tried  to start maple 30+ times and had no
problems.

I switched to 2.6.5 and "failed" 6 times in 20 starts. This is on a
computer with a slowest hard drive (maple takes longest to load). It would
seem like on my other computers with solid state drives the failure rate
was higher - i ll try those later tonight.

Thanks again for looking into this!..  you seemed to have saved me from my
nightmares of needing to switch away from fvwm ;-)

Re: fvwm with java yet again (maple process)

[Peter G]

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  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 0x226 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

Re: fvwm with java yet again (maple process)

[Peter G]

On Fri, Sep 19, 2014 at 10:45 AM, Dominik Vogt  wrote:

>
> If fvwm crashes I need a stack trace from the core file:
>
>
yup, sorry for not providing that. Now showing below. Info about
DeiconifyAndRaise is in the last email.


 me@mycomp:~$ gdb ~/fvwm/install/bin/fvwm ~/core
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /home/me/fvwm/install-cvs-2.6/bin/fvwm...done.
[New LWP 23391]

warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/home/me/fvwm/install/bin/fvwm'.
Program terminated with signal 8, Arithmetic exception.
#0  0x0046fcff in CMD_WindowList (cond_rc=0x7fff5fcbde50,
exc=0x15b4b70, action=0x15ad160 " Function  DeiconifyAndRaise")
at windowlist.c:979
979 dheight = (dheight -
t->hints.base_height)



(gdb) bt
#0  0x0046fcff in CMD_WindowList (cond_rc=0x7fff5fcbde50,
exc=0x15b4b70, action=0x15ad160 " Function  DeiconifyAndRaise")
at windowlist.c:979
#1  0x004655f2 in __execute_function (cond_rc=0x0, exc=, action=, exec_flags=0 '\000',
args=, has_ref_window_moved=0) at functions.c:648
#2  0x00429924 in __handle_key (ea=, is_press=1) at
events.c:2626
#3  0x0042c813 in dispatch_event (e=0x7fff5fcbe2c0) at events.c:4266
#4  0x0042c968 in HandleEvents () at events.c:4324
#5  0x0040abd5 in main (argc=, argv=)
at fvwm.c:2591

Re: fvwm with java yet again (maple process)

[Peter G]

On Fri, Sep 19, 2014 at 2:21 PM, Dominik Vogt  wrote:

> > #0  0x0046fcff in CMD_WindowList (cond_rc=0x7fff5fcbde50,
> > exc=0x15b4b70, action=0x15ad160 " Function  DeiconifyAndRaise")
> > at windowlist.c:979
> > 979 dheight = (dheight -
> > t->hints.base_height)
>
> Should be fixed now.
>
>
I still seem to be getting the same thing:


$gdb  ~/fvwm/install/bin/fvwm ./core

(...)

Program terminated with signal 8, Arithmetic exception.
#0  0x0046fbff in CMD_WindowList (cond_rc=0x7fff4d4c7b60,
exc=0x1b33830, action=0x1b9f370 " Function  DeiconifyAndRaise")
at windowlist.c:979
979 dheight = (dheight -
t->hints.base_height)


(gdb) bt
#0  0x0046fbff in CMD_WindowList (cond_rc=0x7fff4d4c7b60,
exc=0x1b33830, action=0x1b9f370 " Function  DeiconifyAndRaise")
at windowlist.c:979
#1  0x004654f2 in __execute_function (cond_rc=0x0, exc=, action=, exec_flags=0 '\000',
args=, has_ref_window_moved=0) at functions.c:648
#2  0x00429894 in __handle_key (ea=, is_press=1) at
events.c:2598
#3  0x0042c783 in dispatch_event (e=0x7fff4d4c7fd0) at events.c:4238
#4  0x0042c838 in HandleEvents () at events.c:4282
#5  0x0040abd5 in main (argc=, argv=)
at fvwm.c:2591

Re: fvwm with java yet again (maple process)

[Peter G]

On Fri, Sep 19, 2014 at 4:11 PM, Dominik Vogt  wrote:

> On Fri, Sep 19, 2014 at 03:11:26PM -0400, Peter G wrote:
> > I still seem to be getting the same thing:
>
> Hm.  Can you post a print of the window structure in the crashing
> function, please?
>
> sure:

(gdb) p *t
$1 = {name = {name = 0x1328eb0 "Startpage Search Engine - Vimperator
(Private Browsing)", name_list = 0x0}, icon_name = {
name = 0x1328170 "Startpage Search Engine - Vimperator (Private
Browsing)", name_list = 0x0},
  visible_name = 0x1351330 "Startpage Search Engine - Vimperator (Private
Browsing)",
  visible_icon_name = 0x13489e0 "Startpage Search Engine - Vimperator
(Private Browsing)", style_name = 0x0, name_count = 0,
  icon_name_count = 0, next = 0x0, prev = 0x1344fd0, stack_next = 0x6d2820,
stack_prev = 0x1345ed0, wins = {frame = 8389208,
parent = 8389209, client = 52428982, title = 0, button_w = {0, 0, 0, 0,
0, 0, 0, 0, 0, 0}, sides = {8389211, 8389213, 8389215,
  8389217}, corners = {8389210, 8389212, 8389214, 8389216},
icon_title_w = 8389294, icon_pixmap_w = 8389295, transientfor = 608},
  flags = {common = {is_sticky_across_pages = 0, is_sticky_across_desks =
0, has_icon_font = 1, has_no_border = 0,
  has_window_font = 1, title_dir = 0, user_states = 0, s =
{do_circulate_skip = 0, do_circulate_skip_icon = 0,
do_circulate_skip_shaded = 0, do_ewmh_donate_icon = 0,
do_ewmh_donate_mini_icon = 0, do_ewmh_ignore_state_hints = 0,
do_ewmh_ignore_strut_hints = 0, do_ewmh_mini_icon_override = 0,
do_ewmh_use_stacking_hints = 0,
do_ewmh_ignore_window_type = 0, do_iconify_window_groups = 0,
do_ignore_gnome_hints = 0, do_ignore_icon_boxes = 0,
do_ignore_restack = 0, do_use_window_group_hint = 0,
do_lower_transient = 1, do_not_show_on_map = 0, do_raise_transient = 1,
do_resize_opaque = 1, do_shrink_windowshade = 0,
do_stack_transient_parent = 1, do_window_list_skip = 0,
ewmh_maximize_mode = 2, has_depressable_border = 0, has_mwm_border
= 0, has_mwm_buttons = 0, has_mwm_override = 0,
has_no_icon_title = 0, has_override_size = 1, has_stippled_title =
0, has_stippled_icon_title = 0,
has_no_sticky_stippled_title = 0, has_no_sticky_stippled_icon_title
= 0, icon_override = 1, is_bottom_title_rotated = 0,
is_fixed = 0, is_fixed_ppos = 0, is_uniconifiable = 0,
is_unmaximizable = 0, is_unclosable = 0,
is_maximize_fixed_size_disallowed = 0, is_icon_sticky_across_pages
= 0, is_icon_sticky_across_desks = 0,
is_icon_suppressed = 0, is_left_title_rotated_cw = 0, is_lenient =
0, is_size_fixed = 0, is_psize_fixed = 1,
is_right_title_rotated_cw = 1, is_top_title_rotated = 0,
use_icon_position_hint = 1, use_indexed_window_name = 0,
use_indexed_icon_name = 0, windowshade_laziness = 0,
use_title_decor_rotation = 1, focus_policy = {do_raise_focused_click = {
client = 1, decor = 0, icon = 0}, do_raise_unfocused_click =
{client = 1, decor = 0, icon = 0}, do_focus_click = {
client = 0, decor = 0, icon = 0}, do_focus_enter = 1,
do_unfocus_leave = 0, do_focus_by_program = 1,
  do_focus_by_function = 1, do_warp_pointer_on_focus_func = 1,
is_lenient = 0, use_mouse_buttons = 7, use_modifiers = 0,
  do_pass_focus_click = 1, do_pass_raise_click = 1,
do_ignore_focus_click_motion = 0, do_ignore_raise_click_motion = 0,
  do_allow_func_focus_click = 0, do_allow_func_raise_click = 0,
do_open_grabs_focus = 1, do_open_grabs_focus_transient = 1,
  do_override_grab_focus = 0, do_close_releases_focus = 1,
do_close_releases_focus_transient = 1,
  do_override_release_focus = 0, do_sort_windowlist_by = 1}}},
cr_motion_method = 0, was_cr_motion_method_detected = 0,
does_wm_delete_window = 1, does_wm_take_focus = 1, do_force_next_cr =
0, do_force_next_pn = 0, do_iconify_after_map = 0,
do_disable_constrain_size_fullscreen = 0, do_reuse_destroyed = 0,
has_handles = 1, has_icon_changed = 0, has_title = 0,
has_new_wm_normal_hints = 0, is_decor_changed = 0, is_iconify_pending =
1, is_focused_on_other_desk = 0,
is_focus_change_broadcast_pending = 0, is_fully_visible = 1,
is_iconified = 1, is_iconified_by_parent = 0, is_icon_entered = 0,
is_icon_font_loaded = 1, is_icon_moved = 0, is_icon_ours = 1,
is_icon_shaped = 0, is_icon_unmapped = 0,
is_in_transient_subtree = 0, is_mapped = 0, is_map_pending = 0,
is_maximized = 0, is_name_changed = 1, is_partially_visible = 1,
is_pixmap_ours = 1, is_placed_by_fvwm = 1, is_scheduled_for_destroy =
0, is_scheduled_for_raise = 0, is_size_inc_set = 0,
is_style_deleted = 0, is_tear_off_menu = 0, is_transient = 0,
is_window_drawn_once = 0, is_viewport_moved = 0,
---Type  to continue, or q  to quit---
is_window_being_moved_opaque = 0, is_window_font_loaded = 1,
is_window_shaded = 0, used_title_dir_for_shading = 1,
shaded_dir = 0, using_default_icon_font = 0, using_default_window_

Re: fvwm with java yet again (maple process)

[Peter G]

On Fri, Sep 19, 2014 at 4:25 PM, Dominik Vogt  wrote:

> On Fri, Sep 19, 2014 at 04:17:55PM -0400, Peter G wrote:
> > On Fri, Sep 19, 2014 at 4:11 PM, Dominik Vogt 
> wrote:
> > (gdb) p *t
>
> Thanks.  And now?
>

works fine now - thanks!!.

Re: fvwm with java yet again (maple process)

[Peter G]

On Fri, Sep 19, 2014 at 4:31 PM, Dominik Vogt  wrote:

> I wonder why this bug has never showed up before.  It's been in
> the code for ages.
>

that is strange indeed... it must have been after 2.6.5 though as I don't
see this problem with that release.

Re: fvwm with java yet again (maple process)

[Peter G]

> fvwm stays barely usable when the application generates 20.000.000
> ...NAME... PropertyNotify events (machine with four cores).  The
> X server blocks one cpu at 100%, fvwm uses 50% to 60% on another
> core, and the application uses about 12% on a third.  This looks
> pretty good to me - as long as fvwm is twice as fast as the X
> server it cannot be the bottleneck.
>

ha!... if you can survive 20M spam events, you just might the most
resilient WM out there!


> Do you notice any change in performance when starting maple?  Is
> fvwm more responsive or less?


I have not been able to reproduce the problem from before since running the
fvwm version from a few days ago. Maple seems completely usable no matter
what worksheets I throw at it... I can't tell any obvious differences -
when it loads correctly, it works just fine.



>   (The first time maple freaks out
> responsiveness may be not very good; I think that is caused by the
> X server or Xlib allocating lots of memory for the events; on a
> second go fvwm stays usable for me.)
>

Since the version from a few days ago, when it loads, all cores are doing
stuff for a couple of seconds... but then once loaded all is good. I've
tried tripping it by say "manually" flooding the WM with events by
switching desktops, loading new windows, etc... but it's been working ok.



> The code ist still hardly tested and experimental and may cause
> any number of bugs.
>
> I'll play with it for a while, and report anything unusual.

thanks for all your work!!

peter

Re: CVS tadam: Fft: Fix compiler warnings

[Peter G]

just fyi... i think there might be an issue:

make[2]: Entering directory `/blah/fvwm/src/fvwm-2.6.x/libs'
gcc -DHAVE_CONFIG_H -I. -I..  -I..  -I/usr/include/freetype2
-pthread -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/cairo -I/usr/include/libpng12 -I/usr/include/pixman-1
-I/usr/include/freetype2  -Wall -Wno-implicit-int -g -O2   -MT Fft.o
-MD -MP -MF .deps/Fft.Tpo -c -o Fft.o Fft.c
Fft.c: In function ‘FftGetFont’:
Fft.c:327:18: error: ‘result’ undeclared (first use in this function)
Fft.c:327:18: note: each undeclared identifier is reported only once for
each function it appears in
make[2]: *** [Fft.o] Error 1


On Sat, Dec 27, 2014 at 7:00 PM,  wrote:

> CVSROOT:/home/cvs/fvwm
> Module name:fvwm
> Changes by: tadam   14/12/27 18:00:20
>
> Modified files:
> .  : Tag: branch-2_6 ChangeLog
> libs   : Tag: branch-2_6 Fft.c
>
> Log message:
> Fft:  Fix compiler warnings
>
> Pre-initialise some defined variables to shut GCC up.
>
>
>

Re: CVS tadam: Fft: Fix compiler warnings

[Peter G]

No that I can reproduce though.  Try again:
>
> % cvs up -C
>
>

this does not work. I also tried a clean check out of branch-2_6 and get
the same issue when compiling.
weird

Re: CVS tadam: Fft: Fix compiler warnings

[Peter G]

On Sun, Dec 28, 2014 at 6:52 PM, Thomas Adam  wrote:

> Fixed.
>
>
yup, thanks.

a few bugs and an update

[Peter G]

Just wanted to provide a quick update and report a few bugs that have I
been observing.

I am running the latest version from the cvs. Some of you may remember, a
few months ago I had a big issue with maple and its behavior of flooding
fvwm with thousands of events:
https://www.mail-archive.com/fvwm-workers@fvwm.org/msg03650.html
The fix by Dominik seems to work well. I've had fvwm crush twice since
then... but I could not reproduce the issues and it wasn't when a program
was starting.


Here are a few non-critical bugs that I see often:

1) Some windows sometimes start "outside" of the desktop, meaning when they
start, I know they are running but they are not visible on any of my pages.
I use a 9 page, single desktop set up via:
DeskTopSize 3x3
This happens quite a bit with skype, but also other apps as well (for
example spotify). I think it's most likely to happen if the app was not
closed properly (after a power outage for example). I get them to become
visible by running:
Next (Spotify) MoveToPage 0 0
It would be good if the apps were forced to only be first drawn somewhere
where they can be seen by the user (ideally, by default, on the desktop the
user was on, when invoking the app).

2) I use
EdgeThickness 1
to scroll between pages with a mouse. When I scroll from page to page, the
Balloons (i.e hints) on the FvwmPager often don't disappear. The chain of
events is the following:
- Say i'm on a particular desktop page and the mouse in on top of the
pager. The pager balloon/hint will pop up.
- The pager is right at the edge of the page (at the bottom). So say now I
move my mouse downwards, and switch to the page below.
- The page switches, and the mouse is no longer on top of the pager, but
now somewhere near the top...
- ... but the pager balloon/hint is still showing as if the mouse was still
hovering on top of the FvwmPager
The only way to get rid of it, is to move my mouse over the pager, then
move the mouse off the pager, but not while switching the page at the same
time.


3) This is very similar to previous bug, but with FvwmButtons which live at
the top of every the page. I have them setup where the buttons of
FvwmButtons are highlighted when the mouse hovers over them. Here again
when a given button is highlighted (because the mouse is on top of it), and
I then switch the page (move mouse up to the page at the top), sometimes
the button stays highlighted even though the mouse is not on top of it
anymore.


Issues (2) and (3) seem very similar - basically sometimes fvwm is not
aware that the mouse has moved "away" from FvwmPager of FvwmButtons, in
particular when pages are switched. I should stress that I do use
FvwmEvents when switching pages, like so:


*Events: new_page ChangePageEventFunc

DestroyFunc  ChangePageEventFunc
AddToFunc  ChangePageEventFunc
+ I CloseAllConsoles
+ I DeSchedule $[schedule.last]
+ I Next (FvwmPager) RaiseToTop
+ I All (FvwmPager) Schedule 700 Lower


thanks!

Re: a few bugs and an update

[Peter G]

Thanks for the quick response.

On Sun, Jan 25, 2015 at 2:30 PM, Thomas Adam  wrote:

>
> You can coerce this through various means.  I suspect in your case
> though those applications are starting due to program-specified hints.
> That's usually typical.  Try:
>
> Style foo !PPosition
>
>
This actually does not seem to work. From the console:
Style skype !PPosition
[fvwm][style_parse_and_set_window_style]: <> Bad style option:
!PPosition


Doing:
Style skype NoPPosition
however does not spit out errors - I will see if that fixes the issue.



> > 2) I use
> > EdgeThickness 1
> > to scroll between pages with a mouse. When I scroll from page to page,
> the
> > Balloons (i.e hints) on the FvwmPager often don't disappear. The chain of
> > events is the following:
>
> Yes, whilst the balloon windows are mapped, no other events happen to
> them.  Same for point 3.
>
>
So you are saying this a known bug? in a sense that if the mouse leaves
FvwmPager of FvwmButtons, the balloons should disappear?

While I have seen the case with FvwmButtons for a long time, the one with
the FvwmPager is recent - I am not a hundred percent sure, but I think I
first started seeing it around the time when the new event handling was
implemented.

Would there be any ways around it? for example is there a command that
would force these mouse dependent behavior (balloons, color highlights) to
go to their defaults? If so, I could just force that sort of command into
my ChangePageEventFunc() function.





> -- Thomas Adam
>
> --
> "Deep in my heart I wish I was wrong.  But deep in my heart I know I am
> not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
>
>

cvs server up?

[Peter G]

is anyone having a problem grabbing files from the cvs server right now?

i get this:

$ cvs -d :pserver:anonym...@cvs.fvwm.org:/home/cvs/fvwm checkout -r
branch-2_6 fvwm
cvs [checkout aborted]: connect to cvs.fvwm.org(129.7.128.165):2401 failed:
No route to host

Issues with how fvwm handles certain (3d) applications

[Peter G]

First of all, thanks to everyone involved in the latest batch of changes -
it's great to see fvwm still being actively worked on!

I've had this issue I'm about to describe for some years now, and was
wondering if others have come across it as well.
The problem is that when I open applications that typically use 3d
acceleration, my fvwm slows down substantially. By "slows down" I mean
moving windows around is now "slow". I have some keys that bind to
FvwmRearrange to "tile" windows - that is very slow. Basically any
operation that required moving windows around (maximizing, resizing, etc),
takes ~seconds. Switching pages is also noticeably slower. I should stress
however that after minimizing those 3d applications, things go back to
normal and fvwm starts working correctly again.

 The applications that lead to this problem are (for example) kodi, steam
(in picture mode) or various games (started via steam or wine). Kodi is one
of the biggest offenders.

The easiest way to reproduce it is to simply download kodi (or say steam
and put it in "picture mode"), make it "windowed" (backslash key), open
some other apps (say xterms) and start moving windows around.

Has anyone else come across this behavior? If so any ideas where one would
look to fix it?

Thanks!

Re: Issues with how fvwm handles certain (3d) applications

[Peter G]

On Mon, May 9, 2016 at 7:35 AM, Stephen Dennison 
wrote:

>
> I wonder if this is a graphics driver issue.
>>
>
> It reminds me of the kind of symptoms you can see when running compiz,
> actually.  Though for me the slowdown is with the 3d accelerated program
> when compiz is running, not FVWM.
>
>
Thanks for the replies Stephen and Adam. I will try to send over a minimal
config file with some window manipulation that shows this in most explicit
way , but my hard drive on my main machine just died, so it will be in a
few days.

It could be due to some interplay between the video driver and fvwm, but I
have no issues like this when I test  with other window managers (and with
same driver).

Re: Removing libstroke support?

[Peter G]

Does anybody really use libstroke support?


I do. It's something i could easily live without... but I do like it on
occasion.




It's resonsible for
> quite some hardly readably code, and I suspect nobody uses it
> anymore.  If there's a need for mouse gesture or touchpad support,
> there must certainly be some other library around that does a
> better job.
>
> Opinions?
>
> Ciao
>
> Dominik ^_^  ^_^
>
> --
>
> Dominik Vogt
>
>

Re: [fvwmorg/fvwm] b1912e: Fix disappearing windows.

[Peter G]

>
>   Changed paths:
> M fvwm/events.c
>
>   Log Message:
>   ---
>   Fix disappearing windows.
>
>
oh, just noticed this - thanks for tackling this issue.
I've had occasional problems with "disappearing" windows for a long time
now. In my case, I would bring them to visible areas by running  something
like "Next (myprog) MoveToPage 0 0" from the console. Not sure if this is
the same thing as you discuss... but running your patch now.






> The old patch that removed synthetic UnmapNotify events on the root window
> to
> suppress windows in HandeMapRequestKeepRaised() being unmapped later.
> However,
> this also caused problems.  vmplayer windows still diasppeared when
> returning
> from fullscreen mode.
>
> It seems that the real problem was the XUnmapWindow in HandleUnmapNotify.
> Whoever thought this was a necessary or a good idea is wron.  When we get
> an
> UnmapNotify on a client window, the client has already unmapped it itself.
> When we get a synthetic UnmapNotify on the root window the client has also
> unmapped the window.  There's no need whatsoever to unmap it again, and
> events
> caused by unmapping twice do confuse applications.
>
>
>

fvwm and casting from chrome

[peter g]

Hi Everyone:

i have a frustrating issue with fvwm and casting from google's chrome, 
that maybe somebody has a workaround for.


Normally, under any other WM i've tried (and also on windows), in the 
chrome browser, choosing "Cast", will pop up a small window that asks 
the user what device to cast to. Unfortunately in fvwm that little 
window with those options does not show up.


I've tried both with my config, but also with a very fvwm config such as:
key c  A CM FvwmConsole
key r  A CM Restart
Key u  A CM Exec xterm

If anyone has a work around, that would be much appreciated, as casting, 
for better or worse, is very useful to me.


thanks!

Re: fvwm and casting from chrome

[Peter G]

On 5/27/20 4:58 PM, Thomas Adam wrote:

On Wed, May 27, 2020 at 04:41:08PM -0500, peter g wrote:

Hi Everyone:

Hello!


i have a frustrating issue with fvwm and casting from google's chrome, that
maybe somebody has a workaround for.

Normally, under any other WM i've tried (and also on windows), in the chrome
browser, choosing "Cast", will pop up a small window that asks the user what
device to cast to. Unfortunately in fvwm that little window with those
options does not show up.

I've tried both with my config, but also with a very fvwm config such as:
key c  A CM FvwmConsole
key r  A CM Restart
Key u  A CM Exec xterm

If anyone has a work around, that would be much appreciated, as casting, for
better or worse, is very useful to me.

Well, if it's a transient window, it will (by default) popup along side the
parent window.  That said, you can try:

 BugOpts ExplainWindowPlacement On

in your ~/.fvwm2rc file, and monitor stderr to see what FVMM thinks of your
missing window.


Thanks, I've tried that.

Doesn't show anything (I know that option is working, as I get the debug 
info for other windows). As pointed out in another email, that "cast" 
window might indeed be a chrome internal window... what bothers me 
though, is why it shows up in other window managers.




Kindly,
Thomas

Re: fvwm and casting from chrome

[Peter G]

On 5/27/20 9:37 PM, Jim Diamond wrote:

On Wed, May 27, 2020 at 21:32 (-0500), Peter G wrote:


On 5/27/20 4:58 PM, Thomas Adam wrote:

On Wed, May 27, 2020 at 04:41:08PM -0500, peter g wrote:

Hi Everyone:

Hello!

i have a frustrating issue with fvwm and casting from google's chrome, that
maybe somebody has a workaround for.
Normally, under any other WM i've tried (and also on windows), in the chrome
browser, choosing "Cast", will pop up a small window that asks the user what
device to cast to. Unfortunately in fvwm that little window with those
options does not show up.
I've tried both with my config, but also with a very fvwm config such as:
key c  A CM FvwmConsole
key r  A CM Restart
Key u  A CM Exec xterm
If anyone has a work around, that would be much appreciated, as casting, for
better or worse, is very useful to me.

Well, if it's a transient window, it will (by default) popup along side the
parent window.  That said, you can try:
BugOpts ExplainWindowPlacement On
in your ~/.fvwm2rc file, and monitor stderr to see what FVMM thinks of your
missing window.

Thanks, I've tried that.
Doesn't show anything (I know that option is working, as I get the debug
info for other windows). As pointed out in another email, that "cast" window
might indeed be a chrome internal window... what bothers me though, is why
it shows up in other window managers.

I haven't tried another window manager, but for what it's worth, the
cast window does not show up for me in google-chrome.


Thank you for checking!


By the way, are you running these different window managers on the
same Linux distro?  Or is it possible you are using fvwm on one Linux,
and other window managers on a different Linux distro?


I have done these check on the same machine, with the same installation 
of chrome (i.e just long into a different WM).


A few window managers i checked: icewm, lxde, gnome (ubuntu's 18.04 
default desktop), ubuntu's winland desktop thing. All work as expected.


BTW, I'm running the latest github version 2 master branch of fvwm. 
Which are you running?


I'm wondering this because Dan Espen mentioned in another email that he 
does see the cast window pop up in chromium (which for me is also not 
visible).


thanks





Cheers.
 Jim

Re: fvwm and casting from chrome

[Peter G]

On 5/28/20 8:00 AM, Jim Diamond wrote:

On Wed, May 27, 2020 at 21:58 (-0500), Peter G wrote:



On 5/27/20 9:37 PM, Jim Diamond wrote:

On Wed, May 27, 2020 at 21:32 (-0500), Peter G wrote:

On 5/27/20 4:58 PM, Thomas Adam wrote:

On Wed, May 27, 2020 at 04:41:08PM -0500, peter g wrote:

Hi Everyone:

Hello!

i have a frustrating issue with fvwm and casting from google's chrome, that
maybe somebody has a workaround for.
Normally, under any other WM i've tried (and also on windows), in the chrome
browser, choosing "Cast", will pop up a small window that asks the user what
device to cast to. Unfortunately in fvwm that little window with those
options does not show up.
I've tried both with my config, but also with a very fvwm config such as:
key c  A CM FvwmConsole
key r  A CM Restart
Key u  A CM Exec xterm
If anyone has a work around, that would be much appreciated, as casting, for
better or worse, is very useful to me.

Well, if it's a transient window, it will (by default) popup along side the
parent window.  That said, you can try:
BugOpts ExplainWindowPlacement On
in your ~/.fvwm2rc file, and monitor stderr to see what FVMM thinks of your
missing window.

Thanks, I've tried that.
Doesn't show anything (I know that option is working, as I get the debug
info for other windows). As pointed out in another email, that "cast" window
might indeed be a chrome internal window... what bothers me though, is why
it shows up in other window managers.

I haven't tried another window manager, but for what it's worth, the
cast window does not show up for me in google-chrome.

Thank you for checking!

No trouble!


By the way, are you running these different window managers on the
same Linux distro?  Or is it possible you are using fvwm on one Linux,
and other window managers on a different Linux distro?

I have done these check on the same machine, with the same installation of
chrome (i.e just long into a different WM).
A few window managers i checked: icewm, lxde, gnome (ubuntu's 18.04 default
desktop), ubuntu's winland desktop thing. All work as expected.
BTW, I'm running the latest github version 2 master branch of fvwm. Which
are you running?

I tried this with google-chrome-81.0.4044.113 / fvwm-2.6.6+git on
Slackware64-14.2 as well as google-chrome-83.0.4103.61 / fvwm-2.6.9 on
Slackware64-current.

The 2.6.6+git is probably (memory fails, I installed it in Sept 2017)
a version from git around when 2.6.6 was the latest and greatest.

If I get a chance to try another wm on these systems I'll follow-up.


ok, thanks for that.

Per Dan Espen's recommendation i tried to load some desktop-environment 
thing as well as and seeing what chrome is complaining about via 
strace... but at no avail.


puzzling







 Jim