IceWM kills non-responding applications in 3 seconds

[PetteriAimonen]

Currently the timeout for _NET_WM_PING is set to 3 seconds:

icewm/src/wmclient.cc

Line 354 in 9175263

fPingTimer->setTimer(3000L, this, true);

Sometimes (especially when running out of memory) I have applications that lag for more than 3 seconds, and then icewm just kills them with SIGTERM and they disappear. I would have preferred just to wait a bit more. A timeout of 3 to 5 seconds seems common, but most other WMs show a confirmation dialog before killing the application.

As a quick fix, I think e.g. 60 seconds might be more reasonable default value and maybe this timeout should be made configurable. I can send a pull request for that if the idea sounds ok.

I guess the correct fix would be to show a confirmation dialog, but I'm not familiar enough with icewm internals to know exactly how to implement that.

[gijsbers]

Okay, I will add a ping timeout preference. Thanks for the suggestion.

[PetteriAimonen]

I agree that it is not a big problem in general usage, but I've been quite confused by applications just disappearing due to this. Great if you can add a setting :)

[PetteriAimonen]

Thanks a lot, I tested the commit and it works great!

(Sorry for not getting back sooner, I must have missed the notification somehow.)