-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving mouse to bottom of screen doesn't always open the dock #2320
Comments
Maybe you have enabled the "Push to show: requires doing pressure to show the dock" option inside the "Intellihide" option? I have it disabled and showing the dock works like a charm... |
Reading through both of those issues, I don't read anything that seems to be even close to what I am seeing. I tend to doubt this is related to either of those issues.
I seem to have made it even worse. I tried to just disable Intellihide and I was no longer able to get the dash to open with any activity at the bottom of the screen. I then re-enabled Intellihide and still nothing would make the dash appear. I even restarted gnome-shell and still no amount of activity at the bottom of the screen shows the dock any more. So now the only way I can see the dock is by activating the shell overview mode, which frankly completely invalidates the entire point of using the dock. |
If the title "Dash not showing when applying pressure" of #2288 is right then this should either be discussed there or someone would need to explain how it's different. |
I find the reliability of opening the dock when it's auto-hiding to be really bad. Most of the time simply moving the mouse to the bottom of the screen the dock does not open. I usually have to move the mouse back up a small way and then back down to get it to finally open.
I'm using dash-to-dock version 96 on gnome-shell 46.5. But to be clear, this is not new in this version. This has been happening for a long time. I've only just started getting frustrated enough with it lately to finally file an issue.
The text was updated successfully, but these errors were encountered: