• disappearing Plasma

    From Grimble@2:250/1 to All on Wednesday, May 14, 2025 14:41:44
    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


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Mike Easter@2:250/1 to All on Wednesday, May 14, 2025 18:33:39
    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

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Mike Easter@2:250/1 to All on Wednesday, May 14, 2025 18:52:16
    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

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From kyuzo@2:250/1 to All on Thursday, May 15, 2025 07:40:18
    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.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Mike Easter@2:250/1 to All on Thursday, May 15, 2025 18:36:59
    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

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Grimble@2:250/1 to All on Friday, May 16, 2025 17:18:12
    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

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From kyuzo@2:250/1 to All on Sunday, May 25, 2025 23:58:45
    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 won’t
    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.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Mike Easter@2:250/1 to All on Monday, May 26, 2025 17:58:36
    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
    won’t 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

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Mike Easter@2:250/1 to All on Monday, May 26, 2025 18:02:23
    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

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Monday, May 26, 2025 19:07:27

    9sj1kdId3qarXIfXddRGm1yA2fJMYuekHhqsLYoSspZFlOGhP3czTsLwIzaawBjQnHL36Um 2wbXsHP3H2+HdWyp/eQ13UjRO58QEEGcwS8htp9nfFy7myEx9gqBBztskm1VeUzUFW/GGBnu CO/1iLfDt6lXob1vogq4+QXNmzsx6NjtQ91ZD5a4XtB+BMW6bpknQAtyYj30mIPa/y8n6eYv 7HnfBIkI7bl6OQ85/+LlQoKuMExs4SVm9RJeBeFhhMLyzc+/lVURWvStgX6FgHdMwwxnUK13 /T71SeXVBQvk4zYmpHMTgU7uTO2v8vNSIyjJV6H+4yRC8nwllrCvGuUr3iTT0LpB7l1DSi5M jqZJA/51Df95hyyUjy+T9jb6ljvY1QZxea4qusI+XWJ6OBuL6d5fxDWq1tDzx0bzAWgGyvMk HQIv+6iRkUmRidklkJCuOzZ9vOxnMFPLyXgIqytiq2/JsT+Nl9r7wbr5cTE159u7LVAoITCF WygqGzdAT3/IMMuC3em3i+AGPxBX7hH3xWDZxhQy+jNIhTfvi7JJ30t4DjhT3WWMSt5bso9X 29/5+T8bXNfXlHqoE/ebjwADBQ//ck3LyNoQcycCZEYkiBds24ReyAMs+tX8VY1HBHYfC4m6 h+g1JnO6J5CAnxZh4j/uFIOqdiaryVMu4eTIcvRQnrK3orzUNSkpsGSkdZb+04CEc3pOBygk K1HskK+qOr173+NcnCqCSOJhKHX42V7Ez7WfR0BAZQSSY/hY/IDsDpILh+r53WvmrPauYJ/Y STYtJbT+O/xACKfPG9n6HteXIDr8pSpDDeFWQBtIRiqJH20d1remGLVWQKzM6N6T7aFnxpzi 7blICODDHX4KD6K+zJu/uWPxTKgP27cEquKN8ZTGZQBZTmyKxF6utL3ljWE+JvL5zQ0xzwHK 90vbLAiBVFn2Pr0yqjZKdJ3s871I+Ilk3/QKWbBOcsqKiXpK5t+mFSvTVF5RYhVKDnAC4KCd RDVOw5zcYQyFKfmzPEO9u22hZm2Cq3OwviBo/KcXlLedG6TqacjDkLKBEhq1du7m0ZdAlQIf kqgVDsyS0BwM6Clsi5NPdi96XrHUxSg1t4bK02zqRvXF5dM/jKNOh0nM/SZhaHrCphmHxZzi sXMnr4TXZlbdHVDFRHCf2zxldMEbHUVXxO0/2AzFV3RFjZJPesCjitDasXTe14b/DYL3EI8O dxc1fFSN6nxDnXCi/pnD/r1znY/CwlQXAg0f2NjNv3ydBZ0pGKdC5qfUdMQA4a2IYQQYEQgA CQUCZk59rAIbDAAKCRB0C/CavLb3GhglAP9bhXjIBHPyyAI/xqgTmGkDqi5rNaa5tN8LHf1M pPyNiwD/UUOzfgpWhsFfVRC1FopTuJ3UjpSvmDMDJVy2Lp4A4Mw=
    -----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ços

    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-----

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Hejmo (2:250/1@fidonet)