Gnome wifi menu items jumping up and down make clicking risky
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
0. I don't know the relevant circumstances about Wi-Fi networks being available and about the adapter's reception (I use a 2.4GHz USB adapter). This occurs mainly when I first try to get on a network, probably right after waking the machine from sleep and trying to get on a network.
1. In the Gnome desktop environment's top panel, at the far right, open the menu. If Wi-Fi is off, turn it on. If it says Wi-Fi Not Connected, see if that line is appearing and disappearing several times.
2. Try to select a command below that line, not a command that is exposed only by selecting Wi-Fi Not Connected but one below that, such as Settings. Because the network line is disappearing and reappearing in unpredictably rapid cycles, you may not want to click on a command below it (and risk clicking the wrong command) but merely position your cursor as if you intend to click it.
Actual result: You can't be sure what you're going to click.
Expected result:
If a menu command must appear and disappear in unpredictable fashion, have it do so without everything below it in the menu jumping up and down.
This can be managed by having the disappearing menu item be replaced by an unselectable blank menu item. Then, anything below would not jump. If the menu while it has a blank menu item is closed by any method, the blank menu item should be deleted. Thus, when the menu is opened later by any method, in the same login session or not, the blank menu item would not be included.
Additional info:
Ubuntu 20.04.2 LTS, kept evergreen, with Gnome desktop environment 3.36.8 (still).
The package was guessed from the list of process IDs. The string: gnome-shell 3.36.9-
I'm told that Gnome bugs have to be reported to a distro bug tracker first for proper component assignment, so I'm reporting here now.
Changed in gnome-shell (Ubuntu): | |
importance: | Undecided → Low |
status: | Incomplete → Triaged |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1933748/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]