Try systemctl --user restart pipewire pipewire-pulse
Try systemctl --user restart pipewire pipewire-pulse
I really don’t understand dbus.
I think systemd targets work opposite to your expectation. The Wants in [unit] define the things that that unit needs to already be available. For instance, you might add Wants=network.target to the unit for nginx so that it won’t try to start until the network is available. When I wrote a unit to start my company’s application, I also had Wants=postgresql.service to ensure that the database came up before the application. Remember that sysyemd tries to run as many things in parallel as it can. This is one thing that makes it much faster than classic sysvinit which started things sequentially. But it means race conditions can occur. You use Wants to break those races where necessary. The targets that you’d specify in WantedBy in [install] more closely resemble SysV runlevels. You might want to read how runlevels used to work in SysV, in order to understand systemd targets.
Every user can enable services from /etc/systemd/user for their account. If the user doesn’t log in, their instance of the service won’t start. There is a way to have user services launch without logging in, but that would obviously be nonsensical for desktop services.
I don’t think systemd would find units in /etc/systemd/user/KDE. Look at the mess that is /usr/lib/systemd/system. Organization doesn’t seem to be a thing.
For your unit files, you have Wants in the [Install] section. That is not correct. Wants belong in the [Unit] section. The [Install] section is where you define WantedBys. You may want to read the man page for systemd.unit.
To interact with user services, you do have to always use systemctl --user
.
If you put your user unit files in /etc/systemd/user, they’re accessible to all users. If a particular user wants to enable the service, they can run systemctl --user enable $service
. Defining the unit in ~/.config/systemd will mean only the one user will be able to start the service. Defining the unit in /etc/systemd/system indicates it is not a user service but a system service.
It doesn’t have to be the main GPU. I’m not even sure it would be possible to pass through integrated graphics. But if all you need is HDMI output, you can use the absolute cheapest GPU you can find (assuming there’s an open PCIe slot). PCIe pass-through does require CPU support (Intel VT-d or AMD-Vi) on the host and may need to be enabled in the BIOS/UEFI. I have an NVIDIA Telsa card passed through to a VM on my Proxmox server, but I’m only using it for compute; my card doesn’t even have a video output.
Read the documentation on the sudoers file. You can specify particular commands to not require a password.
SMB is a network protocol developed by Microsoft. It’s the protocol used by Windows computers to share files with each other. But the protocol was reverse-engineered and a program called Samba provides SMB functionality on Linux. You only see print$ because your Samba isn’t configured with any file shares. You’ll have to configure it. You can find guides online about how to configure Samba. Samba also maintains its own user list independent of the system. That’s why your local account password didn’t work.
The primary concern is switchover time. A purpose-built UPS can switch in about 10 microseconds. Those large “solar generator” battery packs switch in about 30 microseconds. That might be fast enough, but it’s not guaranteed to be fast enough like a UPS is.
UPS batteries are only rated for a few years’ use, so you probably are due for replacement.
That is a fascinating image. It lets you see how color information is encoded in video. The vertical green bar is a glimpse of the luma (Y) channel. To the left is the chrominance blue (Cb) and to the right is the chrominance red (Cr). But the chroma channels are (obviously) supposed to be aligned with the luma, yielding full color video. Unfortunately, I can’t offer a suggestion why they aren’t aligned.
It may be important for OP’s dual-boot setup to note that Windows should be used to check an NTFS filesystem.
Do you already have a rack? Rack servers are an inconvenient size and shape except in a rack.
This is what RAID is for. Duplicate, or at least spread, data across multiple disks so that a failure of one disk doesn’t result in data loss.
But it can draw more current than the line is rated for. Everything electrical is about “can”, not “will”.
Divide 3000VA by your line voltage to get the required amps. Here in the States, I’d need a 30A circuit at 120V and would absolutely have to run a new line from my breaker panel.
::1 is a compelling alternative
Baloo is the file indexer for KDE. It has little or nothing to do with Akonadi.
I don’t like it when a project’s website only says “here, run this Docker container” and doesn’t have manual setup instructions. I don’t want to just run a black box Docker container, I want to know what the knobs are and what they do.
Thanks, Satan
Have you shopped eBay for used switches?