• 2 Posts
  • 7 Comments
Joined 1 year ago
cake
Cake day: December 27th, 2023

help-circle
  • Running as root is a forceful workaround, not the solution to my problem. I want to open this lock, not break it.

    I don't want to run as root because...
    • It’s bad for security. Think of running sudoedit vs sudo nano or sudo vim. If you run the editor as root directly, you can access the shell as root. This is a feature, not a bug! But if you run sudoedit, it stays at low privilege level until it actually saves the file.
    • The “Retry as Sudo” feature exists. If it’s there, why not use it instead of circumventing it?
    • At this point, editing the file is irrelevant. This is not an XY problem. I want to stop getting the second error.

    The “Retry as Sudo” dialog is supposed to appear, and when I click on the button, I am supposed to get a password prompt. That’s what happens in the Apt version; that’s what happens in the Snap version; and in the NixPKG version, they had the same problem, but they fixed it.

    How do I fix it in my flatpak version?







  • When I open profiles.ini the only profile mentioned there is “default-esr”. That directory exists, and has a bunch of stuff in it, but I don’t see the profile in the profile manager.

    The profile I’m using is called “default-release” and that directory does not exist, but does have an entry in the profile manager.

    The directory “default” exists in the directory structure and in the profile manager, but the directory is almost empty. It has only one thing in it; a file called times.json.

    I created a new profile, and it doesn’t show up in the directory structure either. Curiouser and curiouser…

    PS: It’s not a Snap, but it is a Flatpak.