linuxmemes @lemmy.world Samsy @lemmy.ml 9 mo. ago

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.

72 comments

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.
I know a lot of people enjoy flatpak, and I enjoyed it for a couple apps that had annoying update processes in other package managers, but I'm really not impressed with it overall. Maybe it's an unpopular opinion
- Nah, it's pretty popular. Flatpack for the things you can't / won't use your regular package manager is the most common behavior.
  
  I dunno. A lot of stuff is switching over to flatpak these days. And it is the right direction. Regular repo stuff for the system and flatpak for apps is the way to go. You can have solid base separate from the applications.
  
  Noob question: lately I've been using flatpaks for most things because of the packaged dependencies. I am under the impression that as you add and remove programs over time, you'll run into less issues with flatpak than with the distro package manager because the dependencies will come and go with the flatpaks and not sit in the host accumulating my mistakes. Am I wrong about this?
- I'm convinced most of flatpack's popularity is just it not being snap. When one is meh but you actively dislike the other, "meh" starts to look pretty good. Or maybe I'm just projecting my own feelings.
  
  They both solve a very similar set of problems and they each have their advantages, but canonical really managed to burn a lot of community goodwill with snap, so I'm just not willing to touch it personally (I also dislike having a hundred loop devices in my mounts).
- Maybe I’m talking out my ass, but it seems to be something devs like because it makes their life easier.
  
  Flatpak/snaps are always a hard miss for me as a user, unless there’s no other option.
  
  For users it can mean a lot better app availability since not every distro has enough maintainers to have timely updates for all their repo packages and the maintainer obviously doesn't want to maintain it for every single distro. Less work for maintainers/devs all around, with the benefit of better app availability to the user.
  
  it seems to be something devs like because it makes their life easier.
  
  It seems to be something some devs like because they get annoyed when distro maintainers point out problems in their software or implement workarounds for those issues.
- Given the shortage of people working on FOSS apps, I'm all in for anything that makes their lifes easier, so tgey can focus on the programming part and don't have to care about packaging. That can be solved with community packaging like AUR, but that has it's own problems.
  
  But Flatpak is one of the technologies that explicitly has the developer deal with packaging, something they are usually quite bad at because they don't do it very often, unlike distro maintainers.
- I agree. I prefer using native package manager, nix in my case.
- Maybe you have your own reasons for not being impressed with flatpak and you just didn't list them, but this post is just OP blaming the flatpak CLI for not using sudo for him. There are things that flatpak doesn't do well, but there's currently not a single comment under this post listing any genuine drawbacks.
- I really like it, I think it's genuinely great
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?
- 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.
  
  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.
- 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
  
  Remove --system repos and install them as --user. For me it defaults to --user
  
  Thats probably still not possible over ssh.
I love that this post just turned into people giving helpful solutions and not bullying. Lemmy be awesome
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

THANK YOU SIR! MAY I HAVE ANOTHER! password: *******
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.
next time you can use su or sudo
- That installs and or updates roots flatpaks
  
  Only with --user (I think)? Root can also update the "system installation" flatpaks, which are presumably what OP needed a password for.
  
  Which is what flatpak will always do unless provided with the --user flag.
Wouldn't you just be able to terminate and then run sudo flatpak update ?
- Maybe, I thought this couldn't be end in another ask for password, and again, and again.
Sudo su
- 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.
  
  sudo bash
  
  Take off the training wheels 😎
Polkit rule, if you remove the requirement on subject local then it should work without
sudo flatpak upgrade
I accidentally did a winget upgrade --all from a non-elevated powershell today. I know your pain.
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... :-)
Omg. That doesnt sound great. I‘m using discover on my machine and it works seamless.
- Flatpak uses polkit for permissions. System level flatpak updates are typically permitted without password by polkit but only for local users. For SSH, most flatpak operations require a password, so it's a mess if you try to run an update on system level flatpaks without sudo, which solves OP's problem. They could also move everything to a user level install, which IMO makes more sense for flatpaks than the default system level mode.
Reminds me of updating aur
- yay --sudoloop
- yay using ssu = no password prompt.
sudo -i
???
Good old flatpak.
- This was rather an issue of flatpaks being installed for the system, so updating requires root. One option would've been to use sudo and another would've been --user. I guess flatpak could be blamed for defaulting to --system, which I'm not sure if the blame is on flatpak or distros, dunno.
  
  Who knows. I avoid flatpak for other reasons!
Use NixOS. Then that should not be an issue :)

You've viewed 72 comments.