Closed dmayle closed 8 months ago
You should bisect and report the issue to the offending projects repo
Okay, I'm working to do that now. Previous revision 511bd3364d5bab789093d774c7c276d9b7e51011
is good, while revision 791da42b6442870964b11ea28cf5932a76483548
is no longer working:
[douglas@beast:~/src/nix-config]$ git diff
diff --git a/flake.lock b/flake.lock
index 2100970..c4d0c11 100644
--- a/flake.lock
+++ b/flake.lock
@@ -278,11 +278,11 @@
]
},
"locked": {
- "lastModified": 1706386306,
- "narHash": "sha256-YCiWq2bSt+fKxnYpP9PJ52cthm8dkHUuEVFkwJDauSw=",
+ "lastModified": 1703725031,
+ "narHash": "sha256-PYxvnZcqn66Orlfmr/t/f5ywLYnGhP2oDAFlsQ0GFOQ=",
"owner": "nix-community",
"repo": "nixpkgs-wayland",
- "rev": "791da42b6442870964b11ea28cf5932a76483548",
+ "rev": "511bd3364d5bab789093d774c7c276d9b7e51011",
"type": "github"
},
"original": {
Revision b2b2ac38df53cdcae172302a11ae34448f4a2598
is good
Revision b40e4b779702ff40c4e6ef072dccf47c8f077702
is bad, while revision b2b2ac38df53cdcae172302a11ae34448f4a2598
is good.
BTW: I'm using the following command to only update nixpkgs-wayland:
nix flake lock --update-input nixpkgs-wayland --override-input nixpkgs-wayland github:nix-community/nixpkgs-wayland/$REV
Revision 237c5549c149a261165d1116a513c7df84ced1d7
is good
Revision d93ff536c8fecffaf2dc09db3b14b2c8fcbcab7c
is bad
Revision 904707f5522c7414a634c14f29f96f108b6d2d27
is good
Revision 75f79ac32cc3ec8d37b8c2f08b17275f2487384f
is bad
The offending commit is 298b728f5bb64eca3a57e7767cc649cfecf308fb
, which is responsible for updating sway-unwrapped.
Previously, sway was at revision fa294a9094b673e99e5de0c456dc5a6b9ff7db55
from January 2nd.
This commit brings sway up to revision ae33f4eb37a8ee647907e4fef72c6a488b8b1138
from January 19th
That's exactly the issue. It looks like good progress is being made on fixing the issues. I'm freezing my nixpkgs-wayland for the moment until all of the various broken pieces get picked up (XWayland, libva, and sway)
You can launch sway with -Dlegacy-wl-drm
Is that a runtime flag, or a compile-time flag?
On Tue, Jan 30, 2024 at 10:03 AM Artturi @.***> wrote:
You can launch sway with -Dlegacy-wl-drm
— Reply to this email directly, view it on GitHub https://github.com/nix-community/nixpkgs-wayland/issues/438#issuecomment-1917603745, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAQLWNG2EZNWDWCA6PB72TYREYVNAVCNFSM6AAAAABCNPOYE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJXGYYDGNZUGU . You are receiving this because you modified the open/close state.Message ID: @.***>
That is a runtime flag! Once the new sway hits nixpgs-wayland (if it hasn't already), I'll give it a shot.
Merged last week, I'd expect it to be there. Let us know. This is probably why I've had to run Steam under gamescope.
Mpv was segfaulting for me and that flag fixed it
I use nixpgs-wayland with the nvidia driver, and that ensures that my experience under sway is flicker free.
Sometime over the last month, GLX stopped working. If I remove the nixpkgs-wayland overlay, I get GLX working again (but now with all of the flickering).
With the nixpkgs-wayland overlay, EGL and Vulkan work just fine, but GLX fails to load hardware (mesa only)