Skip to content
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

Dash not showing when applying pressure #2288

Open
mambucodev opened this issue Sep 19, 2024 · 19 comments
Open

Dash not showing when applying pressure #2288

mambucodev opened this issue Sep 19, 2024 · 19 comments
Labels

Comments

@mambucodev
Copy link

I updated today to gnome 47, and sometimes the dash doesn't come up when it's hidden. I've got intelli auto-hide activated when a focus windows is places on the dash area. I don´t know why but if I reload the extension or I disable and re-enable the intelli auto-hide option, it starts working again but then, after a while, it stops.

I'm on Arch Linux 6.10.10-arch1-1 with Gnome 47

Recording:
Screencast From 2024-09-19 13-58-04.webm
PS: sorry but gnome recording doesn't show the mouse pointer, but I'm moving it up and down to the bottom of the screen to eventually show the dock. Also, the pressure in intelli auto-hide is set to 0.

@Neo-29
Copy link

Neo-29 commented Sep 19, 2024

confirmed here on archlinux too
Must tweak/toggle on off the setting (screenshot below) to make the dock appear, then first reboot.... it doesn't work anymore.
image

@mrpeabody
Copy link

mrpeabody commented Sep 19, 2024

Full reset of dash-to-dock section in dconf fixes the problem, but yes, lots of issues, for example, dominant colors or opacity settings no longer work in custom themes.

@Neo-29
Copy link

Neo-29 commented Sep 19, 2024

Full reset of dash-to-dock section in dconf fixes the problem, but yes, lots of issues, for example, dots/dashes no longer work in custom themes.

Even after reboot the computer?

@mrpeabody
Copy link

Full reset of dash-to-dock section in dconf fixes the problem, but yes, lots of issues, for example, dots/dashes no longer work in custom themes.

Even after reboot the computer?

Correct! Reset /org/gnome/shell/extensions/dash-to-dock reboot, set it up and it works just fine.

@Neo-29
Copy link

Neo-29 commented Sep 19, 2024

Full reset of dash-to-dock section in dconf fixes the problem, but yes, lots of issues, for example, dots/dashes no longer work in custom themes.

Even after reboot the computer?

Correct! Reset /org/gnome/shell/extensions/dash-to-dock reboot, set it up and it works just fine.

Workaround confirmed working 👍

@mambucodev
Copy link
Author

mambucodev commented Sep 19, 2024

Full reset of dash-to-dock section in dconf fixes the problem, but yes, lots of issues, for example, dots/dashes no longer work in custom themes.

Even after reboot the computer?

Correct! Reset /org/gnome/shell/extensions/dash-to-dock reboot, set it up and it works just fine.

How do I reset /org/gnome/shell/extensions/dash-to-dock ? Should I just delete it?

@Neo-29
Copy link

Neo-29 commented Sep 19, 2024

Full reset of dash-to-dock section in dconf fixes the problem, but yes, lots of issues, for example, dots/dashes no longer work in custom themes.

Even after reboot the computer?

Correct! Reset /org/gnome/shell/extensions/dash-to-dock reboot, set it up and it works just fine.

Workaround confirmed working 👍

Broken again....
Suddenly...

@Neo-29
Copy link

Neo-29 commented Sep 19, 2024

Full reset of dash-to-dock section in dconf fixes the problem, but yes, lots of issues, for example, dots/dashes no longer work in custom themes.

Even after reboot the computer?

Correct! Reset /org/gnome/shell/extensions/dash-to-dock reboot, set it up and it works just fine.

How do I reset /org/gnome/shell/extensions/dash-to-dock ? Should I just delete it?

Use dconf-editor

@mrpeabody
Copy link

Full reset of dash-to-dock section in dconf fixes the problem, but yes, lots of issues, for example, dots/dashes no longer work in custom themes.

Even after reboot the computer?

Correct! Reset /org/gnome/shell/extensions/dash-to-dock reboot, set it up and it works just fine.

Workaround confirmed working 👍

Broken again.... Suddenly...

To me, fiddling with theme settings gets it broken again, so I don't touch them until it's fixed.

@mrpeabody
Copy link

Full reset of dash-to-dock section in dconf fixes the problem, but yes, lots of issues, for example, dots/dashes no longer work in custom themes.

Even after reboot the computer?

Correct! Reset /org/gnome/shell/extensions/dash-to-dock reboot, set it up and it works just fine.

How do I reset /org/gnome/shell/extensions/dash-to-dock ? Should I just delete it?

Use dconf-editor

or gsettings reset-recursively org.gnome.shell.extensions.dash-to-dock

@mambucodev
Copy link
Author

Full reset of dash-to-dock section in dconf fixes the problem, but yes, lots of issues, for example, dots/dashes no longer work in custom themes.

Even after reboot the computer?

Correct! Reset /org/gnome/shell/extensions/dash-to-dock reboot, set it up and it works just fine.

How do I reset /org/gnome/shell/extensions/dash-to-dock ? Should I just delete it?

Use dconf-editor

or gsettings reset-recursively org.gnome.shell.extensions.dash-to-dock

I don't have this schema. I also tried running gsettings list-schemas | grep 'dock' but no result came out.

@mrpeabody
Copy link

Full reset of dash-to-dock section in dconf fixes the problem, but yes, lots of issues, for example, dots/dashes no longer work in custom themes.

Even after reboot the computer?

Correct! Reset /org/gnome/shell/extensions/dash-to-dock reboot, set it up and it works just fine.

How do I reset /org/gnome/shell/extensions/dash-to-dock ? Should I just delete it?

Use dconf-editor

or gsettings reset-recursively org.gnome.shell.extensions.dash-to-dock

I don't have this schema. I also tried running gsettings list-schemas | grep 'dock' but no result came out.

image

@Calosis
Copy link

Calosis commented Sep 19, 2024

Use latest git to fix the issue, or do not apply a custom color to the dock. Applying a custom color breaks the dock in 47, unless you use latest git.

@mrpeabody
Copy link

Use latest git to fix the issue, or do not apply a custom color to the dock. Applying a custom color breaks the dock in 47, unless you use latest git.

dominant colors are still broken, even in the latest git version

@Mistakesos
Copy link

Mistakesos commented Sep 19, 2024

Use latest git to fix the issue, or do not apply a custom color to the dock. Applying a custom color breaks the dock in 47, unless you use latest git.

dominant colors are still broken, even in the latest git version

Yes,you're right. In my testing, only maximization (not full screen) was affected, and even when placed on the dock with a regular window, it can still be automatically hidden.

Turn off custom dock colors, logout, and login to restore auto hide to normal.

But there is a problem with the indicator, what I mean is the small dot under the icon. If it is default, it will be displayed "on" the icon, but if it is customized, it will completely disappear.

There is a part of journalctl:

JS ERROR: TypeError: (intermediate value).color_from_string is not a function
                                         _computeStyle@file:///home/nobody/.local/share/gnome-shell/extensions/[email protected]/appIconIndicators.js:382:51
                                         _updateIndicator@file:///home/nobody/.local/share/gnome-shell/extensions/[email protected]/appIconIndicators.js:406:14
                                         _onOverviewHidden@file:///home/nobody/.local/share/gnome-shell/extensions/[email protected]/docking.js:769:14
                                         _callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42
                                         _emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10
                                         _changeShownState@resource:///org/gnome/shell/ui/overview.js:257:14
                                         _hideDone@resource:///org/gnome/shell/ui/overview.js:594:18
                                         _animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:579:55
                                         onStopped@resource:///org/gnome/shell/ui/overviewControls.js:748:21
                                         _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                         _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:247:60
                                         @resource:///org/gnome/shell/ui/init.js:21:20

@Milli189
Copy link

Use latest git to fix the issue, or do not apply a custom color to the dock. Applying a custom color breaks the dock in 47, unless you use latest git.

using the latest git was the solution for me

@mambucodev
Copy link
Author

I should try disabling the dominant color once I come back home, I'll let you guys know in 2 days

@Mistakesos
Copy link

🎉🎉🎉Indicator and dock custom color issue is fixed. As far as I knew, the latest git version fixed pressure issue too. Try to update it or waiting for release. Remember to close this issue, thank you for reading, and have a nice day! 😄

@mambucodev
Copy link
Author

mambucodev commented Sep 24, 2024

🎉🎉🎉Indicator and dock custom color issue is fixed. As far as I knew, the latest git version fixed pressure issue too. Try to update it or waiting for release. Remember to close this issue, thank you for reading, and have a nice day! 😄

Thanks! I'll test it once I get home and close the issue once I assure my dock works correctly! 🥳

@mambucodev mambucodev reopened this Oct 1, 2024
@vanvugt vanvugt added the bug label Oct 15, 2024
lleheny0 added a commit to lleheny0/nixos-config that referenced this issue Nov 4, 2024
lleheny0 added a commit to lleheny0/nixos-config that referenced this issue Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants