Bug 42884 - "allow macros" dialog raised to top *several* times
Summary: "allow macros" dialog raised to top *several* times
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
Master old -3.6
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Dialog Macro-VBA
  Show dependency treegraph
 
Reported: 2011-11-13 12:32 UTC by Lionel Elie Mamane
Modified: 2019-05-08 18:28 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lionel Elie Mamane 2011-11-13 12:32:10 UTC
I'm using Debian GNU/Linux, and libreoffice uses GTK.

The "allow macros" dialog (shown in macro security mode medium when opening a document with macros) grabs focus several times. Grabbing the focus even *once* is debatable (really, the window manager should decide), but doing it several times is really overboard and annoys the user: if libreoffice is slow, the dialog grabs focus, the user switches focus to another window, the same dialog grabs focus *again*, and this cycle is repeated several times.

To observe this, one has to switch away focus from the dialog faster than it regrabs it; the easiest way to do that is to slow down LibreOffice, for example by running it over a slow network connection. The upload of an ADSL line is about right for this test. Alternatively, one can set a breakpoint on GtkSalFrame::ToTop, and each time the breakpoint is hit, give focus to another window, then let LO continue executing.

In a multiple workspace scenario, interspersed with the "grabbing focus and raising to top", the dialog also switches from the current workspace to the workspace the document  window is in and vice-versa.

Further testing shows that LO will raise the dialog each time the user switches to the workspace that contains it or to the workspace that contains the document window, so this can go on indefinitely.
Comment 1 sasha.libreoffice 2012-04-20 05:24:25 UTC
Thanks for bugreport
Please, verify if in last version of LibreOffice still reproducible
Comment 2 Joel Madero 2013-05-15 02:40:41 UTC
@Lionel - I can't reproduce this, are you still seeing it? Maybe it's because I'm not running off a slow network but if you still see it, let's just mark as NEW and move it forward
Comment 3 retired 2013-07-17 09:01:56 UTC
Setting to NEEDINFO. Lionel, as Joel said, if you still see this behavior with the latest LO release, please set this bug to NEW.
Comment 4 Lionel Elie Mamane 2013-07-17 09:59:40 UTC
Yes, can still reproduce:

With macro security to medium, and foo.odb file has Basic macros.

1) Start in workspace 1

2) Give LibreOffice window focus

3) File / Recent / foo.odb

4) Immediately switch to workspace 2,
   *before* the "Security Warning" appears".
   Since I have a keyboard shortcut for that,
   I can easily hit the race window.

5) Do not give focus to anybody else.

6) The "Security Warning" appears in Workspace 2
   and gets focus.

7) Switch back to Workspace 1 (I again use the keyboard
   shortcut for that). This gives focus back
   to the LibreOffice window. This automatically
   switches back to Workspace 2 and focus to security warning.

8) Goto 7).

(I can break out of the loop by giving focus to *another* window
 in Workspace 1, by clicking directly on that window in the XFCE
 workspace switcher. But as soon as my mouse hovers over the
 LibreOffice window, it sends me back to Workspace 2.)
Comment 5 QA Administrators 2015-04-01 14:42:23 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2017-03-06 15:57:48 UTC Comment hidden (obsolete)
Comment 7 Thomas Lendo 2018-09-16 19:42:44 UTC
Set back to UNCONFIRMED as nobody else than the bug opener has reproduced the issue. Lionel, please don't set to NEW by yourself.
Comment 8 Xisco Faulí 2018-10-17 17:24:41 UTC
(In reply to Thomas Lendo from comment #7)
> Set back to UNCONFIRMED as nobody else than the bug opener has reproduced
> the issue. Lionel, please don't set to NEW by yourself.

Lionel Elie Mamane, Do you still reproduce this issue in master?
OTOH, would it be possible to have a short screencast showing the issue?
Setting to NEEDINFO
Comment 9 QA Administrators 2019-05-08 18:28:05 UTC
Dear Lionel Elie Mamane,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-NeedInfo-Ping