https://bugs.documentfoundation.org/show_bug.cgi?id=100984
Jan-Marek Glogowski <glo...@fbihome.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTOURBUG
--- Comment #4 from Jan-Marek Glogowski <glo...@fbihome.de> ---
This is AFAIK an unresolvable "bug" in X11. The problem is the way popup
(menus) or combo box dropdowns have to be implemented in X11. Wayland AFAIK
fixes this.
I'm just quoting from
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/49579/comments/45
--8<-- Noël Köthe (noel) --8<--
when you open a menu of e.g. KDE konqueror, GNOME nautilus or firefox
then the screensaver wouldn't start in my tests. First I thought its
a KDE bug http://bugs.kde.org/show_bug.cgi?id=176637 but the same behaviour
can be reproduced with gnome.
Or if you open a pull down menu on a website with firefox/iceweasel the
screensaver will not start.
It is reproducible with installed gnome-screensaver and not installed
xscreensaver so I think its not xscreensaver specific.
If xscreensaver is used you can see the following:
xscreensaver reported the following lines when the timeout expired:
xscreensaver: 20:16:02: couldn't grab keyboard! (AlreadyGrabbed)
xscreensaver: 20:16:06: couldn't grab keyboard! (AlreadyGrabbed)
xscreensaver: 20:16:10: couldn't grab pointer! (AlreadyGrabbed)
xscreensaver: 20:16:10: unable to grab keyboard or mouse! Blanking aborted.
The source code comment says:
xscreensaver-5.07/driver/xscreensaver.c
...
if (! blank_screen (si))
{
/* We were unable to grab either the keyboard or mouse.
This means we did not (and must not) blank the screen.
If we were to blank the screen while some other program
is holding both the mouse and keyboard grabbed, then
we would never be able to un-blank it! We would never
see any events, and the display would be wedged.
So, just go around the loop again and wait for the
next bout of idleness. (If the user remains idle, we
will next try to blank the screen again in no more than
60 seconds.)
*/
I don't know if opening a menu in an application grabs mouse and
keyboard.
this is answered by Michel in http://bugs.debian.org/514036
--8<-- Michel Dänzer
It does; it's the only way the menu can receive input events while the
pointer is outside of it. AFAIK this is a pretty deep X11 design issue,
so I'm afraid this can't be fixed easily. Feel free to bring it up
upstream though.
--8<--
--8<--
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
