View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004816 | Kali Linux | Kali Package Bug | public | 2018-06-22 23:55 | 2018-07-07 00:51 |
Reporter | elwood | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Summary | 0004816: Workspaces to dock will "shake" when autohide is disabled | ||||
Description | Noticed after bug 4794 was corrected, there seems to be an issue where the workspaces to doc display will "shake". This can be seen at https://drive.google.com/open?id=155cGlIkcTRV0Wu-XYB4XgPEzryRxITlL. | ||||
Steps To Reproduce | To reproduce this, some specific settings need to be in place. Tweaks, extensions, workspaces to dock enabled. Settings for workspaces for dock, behavior, turn off autohiding. At that point, the shake will start. If autohiding is turned back on, the shake will stop. This has been reproduced in VMware as well as bare metal install. | ||||
Additional Information | While this occurs, CPU usage seems to go to 100% for gnome-shell, and stay there. UI becomes very sporadic and unresponsive. Once workspaces to dock is turned off, CPU usage returns to normal. | ||||
Overall, this seems like an issue that will not impact many users, due to the fact it is only manifesting itself under specific non-standard configurations. However, due to the odd issues related to the previously mentioned bug its best to capture this incase the issue arrises in other circumstances. |
|
It would be nice to see if the issue is fixed with the git version of the extension. You can do that by extracting the "[email protected]" directory of https://github.com/passingthru67/workspaces-to-dock into ~/.local/share/gnome-shell/extensions/ and restarting the shell (ALT+F2 followed by "r", or just logging out and back in). |
|
Yes, after unzipping the file into ~/.local/share/gnome-shell/extensions/ we get the exact same behavior with both the shake and the high CPU usage. |
|
Then we should report this bug to the upstream developer: |
|
This issue is no longer reproducible. It is assumed that some of the recent gnome changes may have corrected it. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2018-06-22 23:55 | elwood | New Issue | |
2018-06-22 23:55 | elwood | Status | new => acknowledged |
2018-06-22 23:58 | elwood | Reproducibility | have not tried => always |
2018-06-22 23:58 | elwood | Description Updated | |
2018-06-22 23:58 | elwood | Steps to Reproduce Updated | |
2018-06-22 23:58 | elwood | Additional Information Updated | |
2018-06-22 23:58 | elwood | Note Added: 0009299 | |
2018-06-23 07:57 | rhertzog | Note Added: 0009302 | |
2018-06-25 15:44 | elwood | Note Added: 0009313 | |
2018-06-26 09:32 | rhertzog | Note Added: 0009317 | |
2018-07-07 00:51 | elwood | Status | acknowledged => closed |
2018-07-07 00:51 | elwood | Resolution | open => no change required |
2018-07-07 00:51 | elwood | Note Added: 0009347 |