Skip to content
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

No longer seems to work with games #16

Open
a-priestley opened this issue Oct 8, 2023 · 6 comments
Open

No longer seems to work with games #16

a-priestley opened this issue Oct 8, 2023 · 6 comments

Comments

@a-priestley
Copy link

a-priestley commented Oct 8, 2023

It's hard to sus out precisely which actor is the culprit here, but I've observed the following while running sway-audio-idle-inhibit against swayidle built with systemd support, on hyprland (pipewire for audio):

  • While playing a video with firefox, sway-audio-idle-inhibit --dry-print-both reports RUNNING, and swayidle is inhibited as expected when not using the flag.
  • But, while running a game with audio, sway-audio-idle-inhibit --dry-print-both still reports RUNNING, but idle is not inhibited as expected without the dry-run.

I've always had intermittent issues with idle in general, but I think this is the first time I've observed unwanted behavior that I can actually pin down and reproduce.
I may be doing something wrong, or making some incorrect assumptions about how the underlying mechanism works (It's probably not as simple as "if any audio stream is playing, block swayidle"). So I'm wondering if there is a concrete list of requirements that the audio stream needs to have such that it will be picked up by the inhibitor.

Edit: Here's some extra info I just observed:
While running a game, I can "cajole" the inhibitor into working by adjusting the volume. After doing so, swayidle is successfully blocked. But interestingly, after closing the game, the inhibitor does not release until I poke it again with another volume adjustment.

@sh4r10
Copy link

sh4r10 commented Mar 9, 2024

Having the same issue but with firefox, it reports running but idle is not inhibited. I am running it on qtile-wayland though, maybe that could be causing some conflicts.

The run command I use for swayidle:
swayidle -w timeout 300 'swaylock -f' timeout 320 'systemctl suspend' before-sleep "swaylock -f"

Any help is much appreciated

@fahim44
Copy link

fahim44 commented Mar 10, 2024

Same issue on fedora39-sway. App: Firefox. While running video on Firefox, IDLE INHIBITED is called. But actually, idle is not inhabited.

@Jeff-WuYo
Copy link

Jeff-WuYo commented Sep 12, 2024

Same issue on Arch with qtile, with librewolf and brave. I don't know if zwp_idle_inhibit_manager_v1 is implemented or not. During dryrun, it says it's running, but idle still happened.
With brave, even the video is stopped, it still says running.

@ErikReider
Copy link
Owner

Same issue on Arch with qtile, with librewolf and brave. I don't know if zwp_idle_inhibit_manager_v1 is implemented or not. During dryrun, it says it's running, but idle still happened. \

With brave, even the video is stopped, it still says running.

Only Wayland compositor are supported...

@Jeff-WuYo
Copy link

qtile wayland is wayland compositor I suppose? DWL works as intended.

@ErikReider
Copy link
Owner

qtile wayland is wayland compositor I suppose? DWL works as intended.

Oh my bad...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants