this post was submitted on 06 Mar 2024
409 points (100.0% liked)
linuxmemes
21222 readers
85 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
It sounds like you're trying to update system-wide flatpak packages as non-root. Most distros use polkit to allow you to update those without a password from the desktop (i.e. a local user), but usually require a password for remote users (like ssh). Just run as root: "sudo flatpak update".
You could also migrate to a user flatpak installation instead a system-wide one. That's what I've done. IMO that's how it should be done, but that's not the default on most distros for some reason.