[v2] Debugging issues on Linux stack
@atterpac is already working on this.
Since Aug 4, 2026.
- Dominant language
- Go
- Stars
- 36.3k
- Forks
- 1.9k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 33
Description
Description
I’ve been working with Wails for about 4 years; I’ve never had any problems debugging on Windows (surprisingly), but I’ve never been able to get it to work on Linux. Every now and then I try to revisit the problem, but I always hit a wall. The problem is as follows: when I launch the application through the debugger or attach the application process to the debugger, the application freezes, and after a few seconds, a dialog appears stating that “the application is not responding and asking if I want to stop it or wait” (waiting, of course, doesn’t change anything). The application starts working properly again once I detach the debugger.
To Reproduce
wails init -n debug-test -ide vscodecd debug-testwails dev- verify that the applications workscode .- Set a breaking and run with debugger - the application freezes
Expected behaviour
The program is not freezeing when a debugger is attached.
Screenshots
Attempted Fixes
I found a thread where someone else had similar issues while debugging other programs in a similar desktop stack. It was suggested to change the time after which Mutter should mark the application as unresponsive. The dialog stopped appearing, but the application still froze.
" is not responding" while debugging in gnome 3 ubuntu 17.10
How To Disable the "Window not responding" Dialog
I also found a thread where the symptoms and environment were exactly the same as mine. I don’t quite understand how to apply the suggestions from the replies in that thread, but upgrading Wails to the version that included the mentioned fixes didn’t change anything.
https://github.com/wailsapp/wails/issues/4398
Exactly the same issue was reported on the Discord server (quote from Nilpointers's post), but the thread remained unanswered.
Hi,
I just started my journey into wails and want to use my daily tool chain doing so. Which is linux/macos and goland.
Initializing the project with -ide flag works fine, run/debug configurations are shown.
Problem is - running in debug works but if i set a break-point in go code, the execution of the program halts but the breakpoint is not hit. moments later linux asks me if it should quit the not responding program.
Am I missing some dependency here?
System Details
# Wails
Version | v2.12.0
Package Manager | dnf
# System
┌───────────────────────────────────────────────────────────────────────────────────────────────┐
| OS | Fedora Linux |
| Version | 43 |
| ID | fedora |
| Branding | |
| Go Version | go1.25.10 X:nodwarf5 |
| Platform | linux |
| Architecture | amd64 |
| CPU | AMD Ryzen 7 8845HS w/ Radeon 780M Graphics |
| GPU 1 | AD106M [GeForce RTX 4070 Max-Q / Mobile] (NVIDIA Corporation) - Driver: nvidia |
| GPU 2 | HawkPoint1 (Advanced Micro Devices, Inc. [AMD/ATI]) - Driver: amdgpu |
| Memory | 31GB |
└───────────────────────────────────────────────────────────────────────────────────────────────┘
# Dependencies
┌────────────────────────────────────────────────────────┐
| Dependency | Package Name | Status | Version |
| *docker | moby-engine | Installed | 29.6.0 |
| gcc | gcc-c++ | Installed | 15.2.1 |
| libgtk-3 | gtk3-devel | Installed | 3.24.52 |
| libwebkit | webkit2gtk4.0-devel | Installed | 2.47.2 |
| npm | nodejs-npm | Installed | 10.9.7 |
| pkg-config | pkgconf-pkg-config | Installed | 2.3.0 |
| *upx | upx | Installed | 5.1.1 |
| |
└─────────────── * - Optional Dependency ────────────────┘
# Diagnosis
SUCCESS Your system is ready for Wails development!
Additional context
A few notes regarding the environment:
- Tested on every version of Fedora from 36 to 43
- Tested on every version of Wails from v2.4.1 to v2.12.0
- The problem occurs on X11, Wayland, and XWayland
- Tested on the GNOME desktop environment (the version that came by default with the Fedora version used)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.