I frequently post in AskLemmy so I think about questions a lot. For example, I was thinking about this in the shower and I was thinking "I really like this handmade soap. It's much better than the usual stuff we get" and then I came up with a related question: "What is something that you would rather buy handmade instead of mass-produced?"

This is absolutely the coolest, most creative music video I have ever watched.

I was trying to edit my community, and I accidentally pressed the delete button. Is there any way to undo this?

It appears every few times I open the app and the usual android back button doesn't make it go away, and there is no cancel button. What you have to do is toggle the toggle, then the button will change to "do not back up" and then you can press it. It annoys me how easy this makes it to accidentally turn on backup.

As a general rule of thumb, I don't set it for the regular 15 minute increments, because it probably won't go off. Today, I set it for 10:37 and it went off at 10:46! 😠

The test prints in the image use the 0.2mm detail mode and 0.07mm ultradetail mode

I recently got a SV06, my first 3D printer, about a month and a half ago. About a week ago I started to find really bad oozing/ stringing on all of my prints, to the point that any functional prints are basically unusable. So far what I have tried is:

• Cleaning the nozzle, inside and out, using a damp cloth and the metal needle tool that came with the printer.
• Drying the filament. I had two rolls that I was using for the current print, so I used a DIY Dryer to dry both rolls, each on 70 degrees celcius for 4+ hours.

Neither of these have worked. What should I do next?

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

As seen in https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2669 and https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4115

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!

Very interesting article!