wth, that was really annoying
Background-Story: I did a “flatpak update” on a remote client and every package wants the PW for downloading and for installing again. I had to enter the password like 30 times or more.
Background-Story: I did a “flatpak update” on a remote client and every package wants the PW for downloading and for installing again. I had to enter the password like 30 times or more.
quicksand, I love that this post just turned into people giving helpful solutions and not bullying. Lemmy be awesome
corsicanguppy, I like this.
Flatpak is so bad for single-source-of-truth for install state that you should have to put in your password every time just to confirm you understand the pain you’re signing up for.
My only advice here would be if they can change the prompt to say
<span style="color:#323232;">THANK YOU SIR! MAY I HAVE ANOTHER! </span><span style="color:#323232;">password: ******* </span>
NoLifeGaming, (edited ) Wouldn’t you just be able to terminate and then run
sudo flatpak update
?
EpicFailGuy, sudo -i
KISSmyOS, I accidentally did a
winget upgrade --all
from a non-elevated powershell today. I know your pain.
Linkerbaan, Sudo su
corsicanguppy, Sudo su
… for a brief period exposes you to risk. And its double-child kills a lot of context you may want. And it’s ghetto like
cat file | grep string | cat | more
try
sudo -i
and join us in this millennium.
cyberpunk007, Reminds me of updating aur
Overtheveloper, yay --sudoloop
Ilgaz, Really weird thing is, distros and flathub kinda pushes users to do system wide installs while most of the packages can work and get updated per user. They are pushing the thing which made Windows almost impossible to use without an administrator user. A dramatic example would be gnu guix, almost never requires root for updates or installs. It is also usable by normal users. From GNU… :-)
dadarobot, sudo flatpak upgrade
Kusimulkku, (edited ) I update flatpak through ssh and haven’t had this issue. I think you installed it system wide and not for the user, since with user you don’t need password at all
E: From the comments it looks like they didn’t use sudo to update either. With it it would’ve asked once. With --user that wouldn’t have been necessary ofc.
SuperIce, 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.
Pantherina, Polkit rule, if you remove the requirement on
subject local
then it should work without
Sibbo, Use NixOS. Then that should not be an issue :)
observantTrapezium, ???
Kerb, (edited ) huh?
why would you need to enter a password to update flatpacks?why would flatpack ask for your pw multiple times when every other package manager only needs to ask once?
somethingsomethingidk, For every sever install I’ve had, flatpak defaults to the system install which requires a password. You have to explicity pass the --user flag.
I’m not sure how to make it the default
Kusimulkku, Remove --system repos and install them as --user. For me it defaults to --user
Pantherina, Thats probably still not possible over ssh.
SuperIce, Because he tried to update a system-wide flatpak install as a non-root user. Flatpak uses polkit for root permissions. Polkit is usually set up to allow non-root local users to update flatpak without a password, but not remote ones, hence having to continually enter the password for polit when using SSH. He could just run the update with
sudo
like a normal package manager and would only have to enter the password once. But then he wouldn’t be able to complain on Lemmy.
Samsy, Hm, next time when I run into a serious issue, I make a meme here and wait for the explanation.
Thx, next time I just use sudo.
Add comment