Update:
For the 1.3 people who will experiences similar in the future and end up here:
- I could not reproduce on another laptop using the exact same setup.
- This behavior disappeared after a reboot (with new kernel version, but I think that’s not related).
The only possible explanations I can think of are either:
- rare memory corruption /hardware glitch.
- OOM-killer kicked in over many days of uptime, and killed something it shouldn’t, which put the system in a weird state.
Both are very difficult to reproduce reliably.
The Sway issue I opened on github got no response from maintainers.
And it’s definitely not an issue with obsidian, as the developers rightly insisted. My bad.