-
Notifications
You must be signed in to change notification settings - Fork 0
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
Keeps prohibit swayidle #1
Comments
hey @Jeff-WuYo thanks for making this! I hadn't noticed the zombie process' before. I am working on this now and will link the PR to it |
Just letting you know @Jeff-WuYo there is a new version out both here and on the AUR. Also addressed the build dependency problem you also pointed out over there. LMK if it works, and I will close if it all looks good to you |
It doesn't show zombie process anymore, but even if I close librewolf, |
it may take about a minute for the process to clear. Currently, swaddle wont kill the current process if you pause or close, but rather keep it running until it times out (60s) at which point it will clean up. If you close it and then wait approx 1-2 minutes it should clear, and wont spawn anything else. I have played with the idea of having it immediately close, but for my use case, i found it much simpler to just let the process time out after 60s. tldr; the process should close within 1-2 minutes of closing librewolf |
I still observed new process being spawn, even if I closed librewolf (sorry for the previous typo). |
ahh are you closing librewolf while something is playing ? I dont think i accounted for that properly. Just pushed another patch out for you to try |
It works sometime, but not consistent. I'll get back when I done more testing. |
These are what I've tested, they are somewhat consistent.
|
hmm interesting. This is good info for me to try and reproduce on my end. It seems like things work as expected, except in a specific case where for some reason the closing of the browser or moving away from it, doesnt seem to be seen by the dbus logic i have. I've been playing around, and still digging for what could be the problem |
After 5a91352 , number 3. still persist. Another way to produce 3. is to close the tab ---> after systemd-inhibit despawn ---> ctrl + shift + T reopen the tab and play it. Side Note: |
Any development on this? I've got a similar behavior on Qtile/Wayland. I've tried other inhibitors (sway-audio-idle-inhibit + idle-hack and wayland-pipewire-idle-inhibit) and encountered in all cases faulty inhibition after playing videos on my chrome-based browser. Glad to provide any sort of log. |
yeah i still havent made any progress on this. I haven't tried chrome browsers, but you are encountering ? I have noticed that the dbus signals can sometimes be incorrect, which might be whats happening here. Specifically i have noticed there is somtimes delay when moving from |
I've been investigating this a little and I cannot seriously say now that this issue comes from inhibitors. In my case, the |
just to update here, I have started a rewrite of the app where I periodically check the playback status vs waiting for dbus to report it. Hopefully this makes the tracking of the current status much more reliable |
@tpaniaki or @Jeff-WuYo would you mind building off the |
Just built and tested. On my system this doesn't change the underlying problem. As I said in a previous comment, |
Ahh okay that sounds like it's outside the scope of this. I have been running the rewrite for a bit, and haven't hit anything on my side yet. I'm going to let it run for a few more days on my machine to confirm everything is going ok before cutting a new release |
On my end, qtile behaves weird compare to dwl, either swaddle or sway-audio-idle-inhibit. On qtile, I open a youtube video, systemd-inhibit spawn, after 30 sec or so, it become a zombie process. Close the tab, it get killed after few minutes. As for swayidle itself randomly react to it when the inhibition has stopped, I do encounter few random inhibition, keeping screen on when there's no any audio or video playback (dwl + sway-audio-idle-inhibit). I didn't log anything, I thought it's some website triggering it, I just don't know which. Quick update: On dwl, it behave the same, systemd-inhibit become a zombie. |
hmm i cant seem to replicate the zombie processes on my end. Can you run it in debug mode via |
still behave the same, here are some logs
|
Just quickly adding here some results from further testing. Whatever inhibitor I choose, as soon as inhibition starts / stops swayidle (or hypridle) cannot restart properly and this even if I kill and start swayidle afterwards. This last symptom is really peculiar. Something still inhibits swayidle to run even if all inhibitors debug logs are clear from any sort of inhibition. I need to reload qtile for swayidle to run as it should. |
Hi,
I am using with qtile + swayidle + swaddle under wayland. For initial start, playing youtube via librewolf (firefox fork), it works normally. However, when I stop playing video, it keeps prohibit swayidle to suspend my screen, even I quit librewolf. It keeps sponning
systemd-inhibit --what idle --who swayidle-inhibit --why audio playing --mod block sh -c sleep 60
.The text was updated successfully, but these errors were encountered: