gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Windows Version
Microsoft Windows [版本 10.0.26200.7171]
WSL Version
WSL 版本: 2.6.1.0 内核版本: 6.6.87.2-1 WSLg 版本: 1.0.66 MSRDC 版本: 1.2.6353 Direct3D 版本: 1.611.1-81528511 DXCore 版本: 10.0.26100.1-240331-1435.ge-release Windows: 10.0.26200.7171
Are you using WSL 1 or WSL 2?
- [x] WSL 2
- [ ] WSL 1
Kernel Version
Linux version 6.6.87.2-microsoft-standard-WSL2 (root@439a258ad544) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP PREEMPT_DYNAMIC Thu Jun 5 18:30:46 UTC 2025
Distro Version
22.04
Other Software
Repro Steps
cc-switch
(cc-switch:647): Gtk-CRITICAL **: 08:45:31.860: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
(cc-switch:647): Gtk-CRITICAL **: 08:45:31.860: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Expected Behavior
正常显示GUI
Actual Behavior
cc-switch
(cc-switch:647): Gtk-CRITICAL **: 08:45:31.860: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
(cc-switch:647): Gtk-CRITICAL **: 08:45:31.860: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Diagnostic Logs
No response
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 in Collect WSL logs for networking issues
Once completed please upload the output files to this GitHub issue.
See Collect WSL logs (recommended method).
If you choose to email these logs instead of attaching them to the bug, please send them to [email protected] with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.
/question
Diagnostic information
Found '/question', adding tag 'question'