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

dock brokes eveything on GNOME 42 #2111

Open
carepollo opened this issue Oct 20, 2023 · 3 comments
Open

dock brokes eveything on GNOME 42 #2111

carepollo opened this issue Oct 20, 2023 · 3 comments

Comments

@carepollo
Copy link

carepollo commented Oct 20, 2023

this is my configuration and my setup is the default Ubuntu 22.04 but with Qogir theme.
imagen
when the PC locks for inactivity or is suspended, the whole DE breaks, the dock no longer shows, I am unable to click anywhere or move anything, the keyboard becomes completely useless and the only way to solve it is by either reboot or logging out/logging in (if I manage to do so).

I think it is due to the fact that I have two monitors, because when I try it having only one screen it works fine.

so the extension should have support for dual monitor on GNOME 42

@oniric85
Copy link

Same problem here, logging out and back in solves the issue on Ubuntu 22.04.3 LTS and Gnome 42.9.

@xalt7x
Copy link
Contributor

xalt7x commented Nov 2, 2023

Do you have the same problem with pre-installed "Ubuntu Dock"?

@answeb
Copy link

answeb commented Nov 6, 2023

Hi, I think I have the same issue here, gnome 42.9, X11 rendering (but it's the same with wayland), ubuntu 22.04.03
When I resume from suspend, the dash is empty (shown but empty), and I can't click any where. When I press the super key, the ubuntu dock appears at the bottom, but nothing is clickable. I have to ALT-F2 => restart to make everything work again.
It seems that when the dock is shown on all screens, the issue does not occur...
this settings does not prevent the problem.

I found a simple workaround : disable the dash2dock extension... the ubuntu dock keeps all the configuration, but when the extension is disabled, is seems the problem does not occur...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants