If the package manager leaves you with broken dependencies, a broken system, or a system that “doesn’t work,” then there are significant bugs in how the distro has packaged things. It happens, but seldomly.
Package managers aren’t “hard.” There are GUIs where you can search and install packages, even. In my opinion, if you have a Linux user that has avoided learning how package managers work, then they’re skipping a core foundation of how to use their operating system.
You’re recommending Flatpak for users that are confused by packages?
It looks like sonarr is not in the official Ubuntu mirrors. The website mentions adding a new repo to apt. Is this what you did, or something else?
Also, how are you starting it? I’m looking at the Arch package in the AUR (not your distro, but just looking), and I notice that it includes a .service file. This means that it would be started as a service, and not as a user, like you’re probably attempting to do.
What directory is it trying to write to? Can you show us the full error, preferably as text and not a screenshot?
What happens when you try to start it?
If there is a dependency problem in the upstream packages, then there is a bug in Ubuntu. This doesn’t happen often, and isn’t a good reason to go to Flatpak by itself. A bug should be filed upstream and it’ll likely get fixed quickly.
From man systemd:
DESCRIPTION
systemd is a system and service manager for Linux operating systems. When run as first process on boot
(as PID 1), it acts as init system that brings up and maintains userspace services. Separate instances
are started for logged-in users to start their services.
systemd is usually not invoked directly by the user, but is installed as the /sbin/init symlink and
started during early boot. The user manager instances are started automatically through the
user@.service(5) service.
For compatibility with SysV, if the binary is called as init and is not the first process on the
machine (PID is not 1), it will execute telinit and pass all command line arguments unmodified. That
means init and telinit are mostly equivalent when invoked from normal login sessions. See telinit(8)
for more information.
When run as a system instance, systemd interprets the configuration file system.conf and the files in
system.conf.d directories; when run as a user instance, systemd interprets the configuration file
user.conf and the files in user.conf.d directories. See systemd-system.conf(5) for more information.
On my Ubiquiti APs? I suppose I could. I’m also looking to upgrade the network capabilities to a modern 6E setup if I can swing it.
Yeah, Ubiquiti has the “great at most things with a point-and-click UI” market down pat. Although, personally, I don’t really care about webapp UIs and such for networking gear. Give me a man page and configuration file, and I’ll get down to it.
Here’s a small ad block list for your Unifi controller, if it helps: https://github.com/synthead/unifi-adfree
This is what’s important. If you don’t enable power saving in some fashion, your hardware will always be “on” at full specs. Even if the machine isn’t actually being used, it’s still powering everything to be ready to jump at any opportunity to process something quickly without ramping down.
TLP has pretty excellent default settings. Simply turning it on will likely make your battery life go 2-3x longer than without it being on, and you will have about 80% of the performance from a UX perspective. And if you want to crunch numbers faster on battery, you can tune TLP or turn it off temporarily.
VIA jumped onboard to this proprietary stuff, too: https://usevia.app
It’s a real shame. Related threads for both Logitech and VIA:
This is so deliciously hypocritical.
Just discovered this also. I’m out. What a disappointment.