You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's no option to reset UI.
When trying on get familiar with the UI, I separated stack window. Now, stack window is non-interactive and doesn't update.
The issue is in WSLg as reported at microsoft/wslg#663.
But since even reinstalling edb-debugger didn't work(clean uninstall is broken?), it would be useful if there was an option to reset edb-debugger with some option in preferences, UI or at least by deleting config files.
Deleting ~/.cache/codef00.com/edb/sessions~/.cache/codef00.com/edb/symbols didn't help either.
Update: Deleting/commenting last [Window] section in ~/.config/codef00.com/edb.conf and starting edb fixed it for now.
A reset UI button or something regarding this mentioned in docs would still be helpful. So, I will keep this feature request open.
The text was updated successfully, but these errors were encountered:
A reasonable request. In the meantime, you have found the current solution, which is to simply delete the layout information from the config and restart.
Using kali-linux WSL on Windows 11 Pro.
There's no option to reset UI.
When trying on get familiar with the UI, I separated stack window. Now, stack window is non-interactive and doesn't update.
The issue is in WSLg as reported at microsoft/wslg#663.
But since even reinstalling edb-debugger didn't work(clean uninstall is broken?), it would be useful if there was an option to reset edb-debugger with some option in preferences, UI or at least by deleting config files.
Deleting
~/.cache/codef00.com/edb/sessions
~/.cache/codef00.com/edb/symbols
didn't help either.Update: Deleting/commenting last
[Window]
section in~/.config/codef00.com/edb.conf
and starting edb fixed it for now.A reset UI button or something regarding this mentioned in docs would still be helpful. So, I will keep this feature request open.
The text was updated successfully, but these errors were encountered: