-
Notifications
You must be signed in to change notification settings - Fork 13
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
way-displays crashes right after startup #153
Comments
Solved by adding to my config.
|
I'm curious though, what's up with the permission denied messages, e.g. |
Similar issues here. This wasn't happened 1.9.0 or below versions. My env: Log:
|
Does your user belongs to |
I have a similar issue and my user did not belong to the Sadly, Env:
Full
|
Many thanks for the detailed report, this will be most useful in diagnosing the root issue and resolving. In the meantime 1.10.1 has been released to avoid the cancellation issue until a proper resolution can be built. It has been released to AUR. Please advise whether the issue is avoided for now. |
My suspicions are changes in wlroots 0.17 which the compositors are handling slightly differently. |
I just tested your latest release, and am afraid nothing relevant has changed in my case: Log
Similar to what hakanyi wrote in a comment above if I disable # disable VRR for all displays
VRR_OFF:
- '!.*$' |
Fantastic, thank you. I've got a lot of information to work with now. Reverting all the cancellations changes, a comprehensive fix for #147 will be built later. /cc @cmvanb |
Apologies for the inconvenience. 1.10.2 released to AUR, reverting all cancellation behaviour changes. |
No need to: Thank you for your hard work on such a nice tool!
Like expected, the logs show that Log
P.S: For anyone reading this running the |
Glad to hear you're back. Thanks for the updates; today I learned of manjaro-sway. Plan of attack: #147 (comment) |
Using the manjaro flavor of sway 1.8.1 and newest way-displays 1.10.0.
way-displays -g
results inAttaching error log here. Lmk how I can help -- many thanks in advance!
The text was updated successfully, but these errors were encountered: