(not really pipewire itself but an interaction with wireplumber/libcamera/the kernel, but pipewire is what triggers the problem)

As seen in gitlab.freedesktop.org/pipewir… and gitlab.freedesktop.org/pipewir…

The camera's /dev/video file is kept open (without streaming), sadly causing the camera to be powered on what looks to be most devices. For some reason, this completely nullifies the soc power management on modern laptops and can result in increases from 3W to 8W at idle!

On Intel laptops it's a bit easier to debug because you can see the Cstates in powertop not going low but it also wrecks AMD ones. Some laptops can reach lower cstates, but the camera module wastes a few W anyway.

I can't believe this shipped in Ubuntu, Fedora etc without anyone noticing, and for so long. This bug is quite literally wasting GWh of power and destroys the user experience of distros in laptops.

If you have a laptop with a switch that detaches the camera from the usb bus you are probably out of the water, just plug it when you use it and the problem is sidestepped. Removing uvcvideo and modprobing it on demand can also work. Disabling the camera in Lenovo's UEFI is what I did for a year until I finally found the issue on the tracker. Some laptops also seem to not be affected, but for me it happens to every machine I've tested.

Thanks to this comment for another workaround that tells wireplumber to ignore cameras. ~/.config/wireplumber/wireplumber.conf.d/10-disable-camera.conf

wireplumber.profiles = { main = { monitor.libcamera = disabled } }

Software that only captures cameras using pipewire is rare and this hasn't given me any problem. This should probably be shipped by distros while the problem is sorted out.

Note that most laptops will have other problems stopping them from reaching deep cstates, borked pcie sd card readers, ancient ethernet nics that don't support pcie sleep properly, outdated nvme firwmare... those are separate issues that most of the time can also be tackled with some dose of tlp, but it's all for nothing if the usb camera is keeping the soc awake!

Hey all,

I'm a big fan of my plain text and terminal -based applications for things, and I'm looking a calendar system in this spirit.
I'd like for a system which:

1. If possible, is stored in a plain-text (human-readable) format (a la calendar.txt)
2. Has some way of managing repeating events/automating some of the process (which is my only problem with calendar.txt)
3. Can be accessed on my phone (an iPhone---yes yes, I know, I can sense everyone's disappointment) while on the go (either through some application, or just through a plain text editor)

For the past month or two, I've been using remind, which, while fantastic in features and usage, seems relatively obscure and unsupported, and the file format isn't as human-readable as I'd prefer (take this slightly modified excerpt from my class schedule):

OMIT 2024-11-25 THROUGH 2024-11-29 MSG Thanksgiving Break
REM Tue Thu FROM 2024-08-19 UNTIL 2024-12-20 SKIP AT 09:05 DURATION [1:15] MSG Class 1
REM Tue Thu FROM 2024-08-19 UNTIL 2024-12-20 SKIP AT 10:40 DURATION [0:50] MSG Class 2
REM Tue Thu FROM 2024-08-19 UNTIL 2024-12-20 SKIP AT 12:00 DURATION [1:15] MSG Class 3

For my to-dos, I've been pretty happy with the todo.txt format, and with topydo and todooo as frontends for it---surely there is something like this, but for calendar events?

P.S.---Before someone mentions it, yes, I am familiar with org-mode, and I know it perfectly fits my bill, and perhaps it is what I will ultimately turn to---but I'd strongly prefer not to, as I'm currently rebelling against Emacs, and we all know how poorly implemented org is outside of it.