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.

Sign up for GitHub

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

Jump to bottom

Workspace Freezes in Awesome Window Manager When Using Zed and Switching Workspaces #14268

Closed
1 task done
Daniel-Boll opened this issue Jul 11, 2024 · 1 comment
Closed
1 task done

Workspace Freezes in Awesome Window Manager When Using Zed and Switching Workspaces #14268

Daniel-Boll opened this issue Jul 11, 2024 · 1 comment
Labels
defect [core label] linux linux-x11 Linux X11 panic / crash [core label] unactionable

Comments

@Daniel-Boll
Copy link

Check for existing issues

  • Completed

Describe the bug / provide steps to reproduce it

Within a few minutes of opening Zed and switching workspaces in the Awesome Window Manager, all workspaces freeze. The other monitor remains unaffected, but I cannot recover from this state until I log out. Refreshing Awesome causes the windows to move to the other monitor, but they remain unresponsive and do not repaint.

Oddly, the logs do not indicate any errors, making the debugging process challenging.

Environment

Zed: v0.143.6 (Zed)
OS: Linux X11 endeavouros unknown
Memory: 23.3 GiB
Architecture: x86_64

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.

No response
@Daniel-Boll Daniel-Boll added admin read Pending admin review defect [core label] panic / crash [core label] triage Maintainer needs to classify the issue labels Jul 11, 2024
@github-actions github-actions bot mentioned this issue Jul 12, 2024
Open
@notpeter notpeter added linux linux-x11 Linux X11 and removed triage Maintainer needs to classify the issue admin read Pending admin review labels Jul 13, 2024
@JosephTLyons
Copy link
Contributor

Does Awesome Window manager provide any additional logging that might help us here? I'm not sure there is much we can do here without that. I think I will close this out, feel free to reopen if you run into this again and have any additional logging we can use to drill down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
defect [core label] linux linux-x11 Linux X11 panic / crash [core label] unactionable
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@notpeter @JosephTLyons @Daniel-Boll