It also might not come on even for affected users. OP's comment in the reddit post:

From gathering info on their issue tracker, the act of opening the video file but not grab frames is some weird usecase that is acting in weird ways. Additionally, the indicator light is turned on by the uvcvideo driver in a lot of hardware (yes, an attacker can theoretically watch you without you noticing). A possible fix for this is would be in the kernel itself, which should basically ignore the fd being open and only truly act when frames are grabbed.

This is probably an additional halving. 😂

That's the thing: power managment works correctly. It is pipewire that does not let power managnent to save power.

I use ALSA btw.

Well, you're not affected by this specific bug, anyway. Whether you're virtuous in other aspects of your life is beyond the knowledge of anyone here. 😜

Interesting.. I've never had this issue in Fedora KDE, which I run on my PC, but exactly the same thing happens on my wife's PC and the HTPC which both run Xubuntu. Tried setting screen saver, power save options and eventually even uninstalling the screensaver completely. At least in my case it's caused by Xorg DPMS if I remember correctly. Fixed it a while ago but then it came back on one of the computers at some point. Check out https://wiki.archlinux.org/title/Display_Power_Management_Signaling if it could be the same for you.

Same here. I have a 2021 dell xps

Sleep mode seems to be working well for me on fedora atomic with kde (aurora).

Deep sleep works well and can stay sleeping for days.

Normally sleep rules are working well. The do not sleep toggle in the power menu also works to prevent it from sleeping.

Only thing that doesn't work is flatpak apps can't prevent the system from sleeping, so watching a video, using Handbrake to encode etc will all just allow it to sleep if there is no physical input.

I have a 2018 dell xps

Have you looked into the "Activity" settings within system settings already? When you click on the default activity there you should see the option "Automatically shutting down or sleeping". I'm sure you already tinkered with the energy system-settings.

Depends on your distribution. I guess most of them use pipewire nowadays, and the bug has not been fixed yet so... if you are using a common GNU/Linux distro, the bug is likely on your system.

Does it affect you, well, from what I understood, as long as your system registers the camera and pipewire is running, your camera is going to waste energy regardless of whether it's actively streaming video or not.

From what I've understood there are several workarounds, each bad but in a different way:

• Disabling pipewire is not a good universal solution since it would effectively disable all audio on your system.
• Disabling the kernel driver for your camera would be a more precise workaround but it's not simple: apart from knowing how to do -- and undo -- that, you would need to find out which driver it is, and that depends on your actual hardware. And of course, with the driver disabled you would not be able to use the camera, so depending on your situation this might only be viable if you were willing to go back and disable/enable the driver as you need.
• Physically disconnecting the camera - with desktop computer with the camera connected using a cable; you could just unplug it and plug it back in when you need it. With laptops, this is generally not possible; some laptops do have switches which effectively do the same thing but from technical standpoint that switch is a liability and costs something so most main-stream laptops won't have it.

In either case, it's also worth noting that whatever app you are using the camera with is likely to keep a "list of cameras" and some sort of memory of your last selection. In theory, disabling or enabling a camera should work fine, but it's not uncommon that apps will have bugs when managing the list; for example an app might not "see" the camera being back on, etc. so if you are going to use any of the above you might need to get used to restarting an app from time to time.

Assuming that eventually this bug is going to be fixed, the question of when it will be available for your system, again, depends on the distribution you are using. Many distributions have own public bug trackers so you could try and look it up and watch their ticket (in some cases, some distributions might even have fixes available sooner than the bug is fixed upstream, but I would not count on that), or you can try and talk to the community (look for an IRC/matrix channel, discord server, etc.)

I don't think this should have an effect when the laptop is put to sleep. Maybe you want to try out hibernation, though.

8 hours? I would kill to get 8 hours battery life.

Same in case of the audio chipset, the popping is so annoying

@princessnorah @Interstellar_1 Facts. Linux is da bomb.