window resize box freezes if it appears when keyring dialog is blocking input
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
New
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
EDIT: I figured out in more detail what happened, please see comments #4 and #5.
In Unity 7.0.0, after opening chrome after a reboot, I didn't notice that there was a dialog requesting my password for the keyring. Since I at first didn't notice, I was trying to interact with one of the tabs than was left from my last session, but since the keyring dialog blocks input to the window, chrome was shown to be unavailable, with the same colored tinted box shown when resizing. So I noticed and entered my password and got access to my chrome window agian.
This is when the bug appeared, the resize box that was overlaying didn't disappear and also it was not possible to resize the chrome window. In the screenshot you can see that the resize box stays were it was first displayed even after moving the window.
The problem disappears after restarting chrome, but there seems to be a bug with this "unavailability notification" when reacting to dialogs in an unexpected manner. Will try to reproduce.
summary: |
- "window resize/unavailable box" frozen after dialog + window resize box freezes if it appears when keyring dialog is blocking + input |
description: | updated |
first attempt to reproduce the bug was unsuccessful, no resize box appeared over the window when trying to input to another window with keyring manager dialog open.
In the second attempt the same thing happened with my term window. The resize box appeared when adding focus by clicking term window after the keyring dialog from chrome appeared, see new attachment. notice that the resize box is overlapping the chrome window. The resize box went away after exiting term.
Also, the keyring dialog blocks all keyboard input(not mouse, mouse is free to do whatever), even the dash/screenshot etc. However, if the wrong password is entered, input is not blocked. I'm not sure if this is a problem with unity, seahorse 3.6.3ubuntu1 or Chromium 28.0.1500. 71-0ubuntu1. 13.04.1, but the input policies seem inconsistent.
Unity version was 7.0.0daily13. 06.19~13. 04-0ubuntu1