From Newsgroup: alt.os.linux.mageia

I was having trouble with "no space" messages on my other machine.
Looking around, I saw /var/lib/flatpack was very large, so I uninstalled flatpak and deleted /var/lib/flatpack. When I reboted, I found my only
window manager available was IceWM, I'd lost all my saved passwords and
I couldn't find the equivalent of kmenuedit.
How can I get Plasma back?
--
Grimble
Registered Linux User #450547
Machine 'Bach' running Plasma 5.27.10 on 6.6.88-desktop-3.mga9 kernel.
Mageia release 9 (Official) for x86_64

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mageia

Grimble wrote:

I was having trouble with "no space" messages on my other machine.
Looking around, I saw /var/lib/flatpack was very large, so I uninstalled flatpak and deleted /var/lib/flatpack. When I reboted, I found my only window manager available was IceWM, I'd lost all my saved passwords and
I couldn't find the equivalent of kmenuedit.
How can I get Plasma back?

This would be a good time to have a Timeshift backup.
--
Mike Easter
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mageia

Grimble wrote:

I was having trouble with "no space" messages on my other machine.
Looking around, I saw /var/lib/flatpack was very large, so I
uninstalled flatpak and deleted /var/lib/flatpack. When I reboted, I
found my only window manager available was IceWM, I'd lost all my
saved passwords and I couldn't find the equivalent of kmenuedit. How
can I get Plasma back?

Seen in the Mag wiki:

One of the down-side of using Flatpak, the first time you install
one of them, it will download a lot of dependencies and use quite a
lot of space. Example: after installing only KiCAD (which is rather
big) as Flatpak system wide, /var/lib/flatpak/ was 4GB.

... and seen in the 'dependency hell' experiences manual; sometimes
removing some 'package' causes the removal of dependencies which belong
to other things.
--
Mike Easter
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mageia

Il 14/05/25 19:52, Mike Easter ha scritto:

Grimble wrote:

I was having trouble with "no space" messages on my other machine.
Looking around, I saw /var/lib/flatpack was very large, so I
uninstalled flatpak and deleted /var/lib/flatpack. When I reboted, I
found my only window manager available was IceWM, I'd lost all my
saved passwords and I couldn't find the equivalent of kmenuedit. How
can I get Plasma back?

Seen in the Mag wiki:

One of the down-side of using Flatpak, the first time you install
one of them, it will download a lot of dependencies and use quite a
lot of space. Example: after installing only KiCAD (which is rather
big) as Flatpak system wide, /var/lib/flatpak/ was 4GB.

... and seen in the 'dependency hell' experiences manual; sometimes
removing some 'package' causes the removal of dependencies which belong
to other things.

It could be a solution installing Flatpack only locally, not consuming
the / partition.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mageia

kyuzo wrote:

It could be a solution installing Flatpack only locally, not consuming
the / partition.

How would the 'user' do that? That would have to be flatpak coding or a preferences/option feature availability.

I'm just now reading that flatpak's design is like 'git for apps'. I
didn't realize that.

https://docs.flatpak.org/en/latest/under-the-hood.html

But, I certainly agree that if you *could* that would be a good idea.
--
Mike Easter
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mageia

On 14/05/2025 14:41, Grimble wrote:

I was having trouble with "no space" messages on my other machine.
Looking around, I saw /var/lib/flatpack was very large, so I uninstalled flatpak and deleted /var/lib/flatpack. When I reboted, I found my only window manager available was IceWM, I'd lost all my saved passwords and
I couldn't find the equivalent of kmenuedit.
How can I get Plasma back?

Well, I've re-installed plasma, and the out-of space messages have
stopped, so that's OK. I've forgotten what I installed that needed
flatpak, but I'll be more careful in future.
--
Grimble
Machine 'Haydn' running Plasma 5.27.10 on 6.6.88-desktop-3.mga9 kernel.
Mageia release 9 (Official) for x86_64
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mageia

Il 15/05/25 19:36, Mike Easter ha scritto:

But, I certainly agree that if you *could* that would be a good idea

Excuse me, i read only now.

From the documentation:

System versus user

Flatpak commands can be run either system-wide or per-user. Applications
and runtimes that are installed system-wide are available to all users
on the system. Applications and runtimes that are installed per-user are
only available to the users that installed them.

The same principle applies to repositories - repositories that have been
added system-wide are available to all users, whereas per-user
repositories can only be used by a particular user.

Flatpak commands are run system-wide by default. If you are installing applications for day-to-day usage, it is recommended to stick with this default behavior.

However, running commands per-user can be useful for testing and
development purposes, since objects that are installed in this way wonrCOt
be available to other users on the system. To do this, use the --user
option, which can be used in combination with most flatpak commands.

Commands behave in exactly the same way if they are run per-user rather
than system-wide.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mageia

kyuzo wrote:

Il 15/05/25 19:36, Mike Easter ha scritto:

But, I certainly agree that if you *could* that would be a good
idea

Excuse me, i read only now.

From the documentation:

System versus user

Flatpak commands can be run either system-wide or per-user.
Applications and runtimes that are installed system-wide are
available to all users on the system. Applications and runtimes that
are installed per-user are only available to the users that
installed them.

The same principle applies to repositories - repositories that have
been added system-wide are available to all users, whereas per-user repositories can only be used by a particular user.

Flatpak commands are run system-wide by default. If you are
installing applications for day-to-day usage, it is recommended to
stick with this default behavior.

However, running commands per-user can be useful for testing and
development purposes, since objects that are installed in this way
wonrCOt be available to other users on the system. To do this, use the
--user option, which can be used in combination with most flatpak
commands.

Commands behave in exactly the same way if they are run per-user
rather than system-wide.

I understand what that says, but I don't understand it to say that the
choice to run a flatpak command as a user instead of system-wide would
change the default storage for the installed flatpak apps.

However, I have found par/s in the flatpak docs that addresses the storage:

Flatpak can operate in system-wide or per-user mode. The system-wide
data (runtimes, applications and configuration) is located in $prefix/var/lib/flatpak/, and the per-user data is in $HOME/.local/ share/flatpak/. Below these locations, there is a local repository
in the repo/ subdirectory and installed runtimes and applications
are in the corresponding runtime/ and app/ subdirectories.

and

FLATPAK_USER_DIR

The location of the per-user installation. If this is not set, $XDG_DATA_HOME/flatpak is used.

--
Mike Easter
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mageia

Mike Easter wrote:

However, I have found par/s in the flatpak docs that addresses the storage:

The user term appears 127x in this page: https://docs.flatpak.org/en/latest/flatpak-command-reference.html
--
Mike Easter
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mageia

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Grimble wrote:

On 14/05/2025 14:41, Grimble wrote:

I was having trouble with "no space" messages on my other
machine. Looking around, I saw /var/lib/flatpack was very large,
so I uninstalled flatpak and deleted /var/lib/flatpack. When I
reboted, I found my only window manager available was IceWM, I'd
lost all my saved passwords and I couldn't find the equivalent of
kmenuedit. How can I get Plasma back?

Well, I've re-installed plasma, and the out-of space messages have
stopped, so that's OK. I've forgotten what I installed that needed
flatpak, but I'll be more careful in future.

We have many things recorded in computer memories, but original data
created by us are not so many. So it's not so hard to backup.

- --

Abra|oos

Gilberto F da Silva
-----BEGIN PGP SIGNATURE-----
Comment: +-----------------------------------------------------+
Comment: ! https://t.me/Gilberto_F_da_Silva !
Comment: +-----------------------------------------------------+

iHUEAREIAB0WIQSWDU9sZ+hOyX91n7l0C/CavLb3GgUCaDSt3wAKCRB0C/CavLb3 Gns4AQCwmup9lxSa/7LVI1KGsnSzkk1dIasitYOiruxVEeUnTAD+Nfh0QZxo2Ozo h5/80qNEI/C7SgAp8bP4h2LCzGHr8Zc=
=nnfr
-----END PGP SIGNATURE-----
--- Synchronet 3.21d-Linux NewsLink 1.2