-
Notifications
You must be signed in to change notification settings - Fork 202
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
Debian version of swaylock (based on v1.5) in bullseye (currently testing branch) crashing #196
Comments
Please reproduce with a manually compiled swaylock and post the new stack trace. |
I won't be able to do so on this very machine - at least not immediately. For the record, a backtrace with debug symbols installed/resolved:
|
Sounds like #181 |
Can you try running with ASan? This smells like memory corruption. |
(See closed issue Github automatically linked above) Already I see without a crash a couple of memory leaks like
I think this is benign and happens because for leak detection to work properly libraries would have to be compiled with asan as well. Mentioning it just in case. |
So far I have not encountered a crash on master. If I do I will post again. |
Sounds encouraging. Could you upload the binar(y|ies)? Happy to test. |
I just compiled with the instructions in the readme with the extra options to |
Hi, Same issue with swaylock-1.5-2 as shipped by Ubuntu 21.04. |
Upon exit:
|
Update, with the same binary, when laptop left connected to an external monitor via USB-C, |
Another update, I can reproduce the same when running Sway v1.6. Installed from
|
In my current setup swaylock crashes for me when waking up my computer. I see the ring, start typing and even before hitting the second key I already see my desktop - and swaylock having crashed in the logs.
I know it's not swaylock vanilla, though the 3 patches applied to the source for the debian package don't seem invasive (http://deb.debian.org/debian/pool/main/s/swaylock/swaylock_1.5-2.debian.tar.xz) and since its single purpose is to lock the screen which it fails to do so in my case, I allow myself to also report it here.
The text was updated successfully, but these errors were encountered: