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

gnome-shell: Cannot focus on apps or app bar #30125

Closed
darmon77 opened this issue Apr 10, 2021 · 17 comments
Closed

gnome-shell: Cannot focus on apps or app bar #30125

darmon77 opened this issue Apr 10, 2021 · 17 comments
Labels
bug Something isn't working

Comments

@darmon77
Copy link

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3976

@notthewave
Copy link
Contributor

@Gottox you tested it before didn’t you? Apparently it "worked great", so I assume this problem didn’t occur to you.

If that’s in fact the case, there might be some easy fix or this.

@paper42
Copy link
Member

paper42 commented Apr 10, 2021

Is this happening to you? Please fill the issue template. I have a dual screen setup with Intel integrated graphics like in the issue you posted and I didn't notice this happening.

@Gottox
Copy link
Member

Gottox commented Apr 10, 2021

Can't reproduce here. Can you give more information about your setup?

@Gottox Gottox changed the title Voidlinux team was necessary to update to gnome 40 with this bug Cannot focus on apps or app bar Apr 10, 2021
@Gottox
Copy link
Member

Gottox commented Apr 10, 2021

Also please use proper titles. This has only clickbait level qualities 😝

@Gottox Gottox changed the title Cannot focus on apps or app bar gnome-shell: Cannot focus on apps or app bar Apr 10, 2021
@Gottox Gottox added the bug Something isn't working label Apr 10, 2021
@darmon77
Copy link
Author

Is this happening to you? Please fill the issue template. I have a dual screen setup with Intel integrated graphics like in the issue you posted and I didn't notice this happening.

My problem is exactly the one described in gnome.
A not completely stable package. It is not advisable to update.
Testing and seeing their behavior in beta is a better idea, for some users to work and others not.

@Gottox
Copy link
Member

Gottox commented Apr 10, 2021

Sorry, but I can't help if I can't reproduce the issue. Upstream has a hard time too. Could you provide any more informations?

@Gottox
Copy link
Member

Gottox commented Apr 10, 2021

@darmon77 Could you try to start with a fresh .config directory and see if the issue is still present?

@Gottox
Copy link
Member

Gottox commented Apr 10, 2021

Also does this happen with Xorg too?

@notthewave
Copy link
Contributor

5E611786-1B70-45CD-AE13-EF845DCD7C59
Some basic system info provided by neofetch 😜

I’m on musl

Issue was also present on Xorg after Xorg-fonts and driver install.

Removed everything (inc contents of $HOME). Starting with:
base-system
grub
opendoas

Will install:
Gnome
Mesa
Mesa-intel-dri
lf

TEST:
Wayland issue present.
...
Install:
Gnome-apps

TEST2:
Wayland issue present.
...
Next up Xorg

Install:
Xorg

Result: same issue on Xorg
...

Monitor swap:
1680x1050

Still...

Gottox do you have a glibc system?

@notthewave
Copy link
Contributor

Since I have a Tablet:
Pen and Touch input misbehave as well...

@darmon77
Copy link
Author

It sure is a gnome-shell problem with libinput, I'm going to do the tests.
This should have been seen in testing before the update.

@paper42
Copy link
Member

paper42 commented Apr 10, 2021

@notthewave I have thinkpad x220 (without touch) and glibc. @darmon77 do you have musl too? The touch input was ok when I was testing gnome 40 before it was merged, I don't have my touchscreen laptop right now.

@notthewave
Copy link
Contributor

So I installed libinput-gestures or whatever and I behaves differently. And I can’t map monitors correctly anymore.

@darmon77
Copy link
Author

@paper42 my anomalous behavior is in musl.
I am installing two gnome dbg (glibc & musl) to reproduce the error.
I will comment on everything necessary

@Gottox
Copy link
Member

Gottox commented Apr 11, 2021

Thanks for the report. I'm currently guessing it's bug that is triggered on musl systems. Nevertheless, I can't see why yet.

@Gottox
Copy link
Member

Gottox commented Apr 11, 2021

Update: I'm able to reproduce the issue now. Afaics, the bug should be somewhere in gnome-shell or mutter. First I suspected gtk4, but running the gtk4 demo doesn't result in janky behavior.

@Gottox
Copy link
Member

Gottox commented Apr 11, 2021

@Gottox Gottox closed this as completed in f1884af Apr 11, 2021
adbrown101 pushed a commit to adbrown101/void-packages that referenced this issue Apr 12, 2021
Veganizer pushed a commit to Veganizer/void-packages that referenced this issue Apr 13, 2021
hazayan pushed a commit to hazayan/void-packages that referenced this issue Apr 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants