Call-Overlay: callend/cancel button does not work

Cyborgscode commented 2 years ago

Name : twinkle Version : 1.10.3 Release : 1.git15ece11.fc35 Architecture: x86_64 OS: Fedora 35

if a call connects, we get a overlay on the desktop with the callerid and a button to end the call. This overlay does not catch the mouseevents on Cinnamon Desktop ( and mostly likely other DE too ). All attempts to cancel the call via mouseclicks end up on other windows on the display, that reside "under" ( z-axis ) the overlay. Unintended closing of windows is caused by this at best.

fbriere commented 2 years ago

This overlay does not catch the mouseevents on Cinnamon Desktop ( and mostly likely other DE too ).

It works for me with Xfce, though. :smile:

Do you also see the same behavior with the incoming call popup, or does that one work correctly?

Cyborgscode commented 2 years ago

it works on "incoming calls" and .. today.. "outgoing" was working too.

It could be tricky to track this :D

Cyborgscode commented 2 years ago

News:

I had a fullscreen game (not window) running when the phone rang, the overlay was inside the screen ( dual screen) and I was UNABLE to click anything.

fbriere commented 2 years ago

I had a fullscreen game (not window) running

Ah, that explains a lot.

Do you remember if your first report also involved a game (or a full screen app) running?

In any case, games are well-known for grabbing (capturing) the pointer, making it impossible to interact with other windows. And I don't think there's much we can do about it: releasing all active grabs ourselves is a broad-scope action that requires the grab:break_actions option to be enabled (which is typically not the case), and would probably piss off many players; while not displaying the popup if the pointer is grabbed seems impossible, as I haven't found a way to determine this (and it would probably piss off more people).

If anybody knows of an app that has figured out how to handle this situation, please let me know!

As for your situation, if this happens again, here are two possible suggestions:

Find out if you can get your game to release its pointer grab. Exiting full screen will often do the trick. (Obviously, quitting the game is a more drastic solution.)
Set a keyboard shortcut with your window manager to run twinkle --cmd answerbye on the press of a key. (Unfortunately, some games also grab the keyboard, making this solution moot.)

Cyborgscode commented 2 months ago

I do not remember, but i also had no issue anymore since then. I suggest to close it for now.

LubosD / twinkle

Call-Overlay: callend/cancel button does not work #281