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

GTK4 Applications with Popup menus become unresponsive after first click #1299

Open
1 of 2 tasks
smac89 opened this issue Nov 27, 2024 · 3 comments
Open
1 of 2 tasks

Comments

@smac89
Copy link

smac89 commented Nov 27, 2024

Windows Version

Microsoft Windows [Version 10.0.22631.4541]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Arch

Other Software

Cambalache (flatpak ar.xjuan.Cambalache), version 0.94.0
Workbench (flatpak re.sonny.Workbench), version 46.1
GParted, version 1.6.0

Repro Steps

Launching any of the flatpak apps (including their non-flatpak versions) and attempting to click anything that resembles a popup or a dropdown menu, results in the menu becoming unresponsive with subsequent clicks.

Only GParted's popup's behaved well. I also noticed that Qt applications behave well. The problem only seems to arise with these newer GTK applcations, which may be due to CSD.

Expected Behavior

All applications with Popups should behave correctly

Actual Behavior

Workbench

Screen.Recording.2024-11-27.134412.mp4

Cambalache

Screen.Recording.2024-11-27.134836.mp4

GParted

Screen.Recording.2024-11-27.140158.mp4

Diagnostic Logs

Another one I tested, but didn't show is gnome-builder. Upon launching that one and attempting to move the popups, I get the following message in the logs:

Compositor doesn't support moving popups, relying on remapping

Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

@smac89
Copy link
Author

smac89 commented Nov 27, 2024

Copy link

Diagnostic information
.wslconfig found
	Custom kernel command line found: 'audit=1'
Detected appx version: 2.3.26.0

@OneBlue OneBlue transferred this issue from microsoft/WSL Nov 27, 2024
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

1 participant