sshing in to update flatpaks is very awkward
To update flatpaks: $ sudo flatpak update but this won't work through SSH. You have to start DBUS first. And you cannot do it in a separate sudo because the environment will be different between the two. (The error messages are ugly.) $ ssh other-system $ sudo -i # export $(dbus-launch) # sudo flatpak update flatpak update seems a lot slower than normal package updates.
D. Hugh Redelmeier via Talk said on Thu, 23 Apr 2026 21:55:29 -0400 (EDT)
To update flatpaks: $ sudo flatpak update
but this won't work through SSH. You have to start DBUS first.
Eeeeu, DBUS, get it offa me!
And you cannot do it in a separate sudo because the environment will be different between the two. (The error messages are ugly.)
$ ssh other-system $ sudo -i # export $(dbus-launch) # sudo flatpak update
flatpak update seems a lot slower than normal package updates.
Can you put it all in one shellscript and just run the shellscript over ssh? SteveT Steve Litt http://444domains.com
On 2026-04-24 10:07, Steve Litt via Talk wrote:
D. Hugh Redelmeier via Talk said on Thu, 23 Apr 2026 21:55:29 -0400 (EDT)
To update flatpaks: $ sudo flatpak update
but this won't work through SSH. You have to start DBUS first.
Eeeeu, DBUS, get it offa me!
What... Afraid of spiders also ;)
And you cannot do it in a separate sudo because the environment will be different between the two. (The error messages are ugly.)
$ ssh other-system $ sudo -i # export $(dbus-launch) # sudo flatpak update
flatpak update seems a lot slower than normal package updates.
Can you put it all in one shellscript and just run the shellscript over ssh?
I use nsenter for docker and podman It may work here. A docker example is "nsenter --mount --uts --ipc --net --pid --target $(docker inspect --format {{.State.Pid}} docker_proxy_1 )" -- Alvin Starr || land: (647)478-6285 Netvel Inc. || home: (905)513-7688 alvin@netvel.net ||
participants (3)
-
Alvin Starr -
D. Hugh Redelmeier -
Steve Litt