Discover, false errors due to "root" password dialog

[TxTechnician]

When updating from Discover, I get bogus errors that are a result of the root password not being used.

The error dialogs pop up before the authentication dialog pops up. Which results in false errors (can’t update x because permission). So I get errors, even through there isn’t an error. It’s annoying.

I’ve seen ppl say to create a Wheel group and add your user to it.

The arch wiki has some policykit change suggestion.

And chat has told me to create a “sudoers” file.

What should I do to prevent these false errors?

[myswtest]

Don’t use Discover

The proper way to update TW is to use zypper at a CLI

#  zypper -vvvv dup

[arvidjaar]

@TxTechnician

What should I do to prevent these false errors?

You could start with showing these errors. So far you just showed the authentication dialogue which is normal for system-wide flatpak.

[TxTechnician]

Aborted due to failure (Flatpak system operation Deploy not allowed for user)

So, I’ve misunderstood the problem. And it is just has something to do with flatpak?

[hui]

Make Discover install flatpaks to user by default?

Hello. I like to use discover to install flatpak apps, since it has a much more user friendly installation process than figuring out the reverse DNS address of the app or whatever that org.appname.appname format is called. Unfortuantely, discover installs the flatpaks to the system by default, which is undesireable due to a bug mentioned here: 466559 – Discover doesn't properly handle case where system is configured to prompt for authentication for updating Flatpaks Essentially what happens is…

[arvidjaar]

@TxTechnician

it is just has something to do with flatpak?

Authorization request comes from flatpak, and yes, adding your user to the wheel group should allow systemd-wide installation skipping authentication.

[karlggest]

Hi.

If “The proper way to update TW is to use zypper at a CLI” then TW must not be installed by default using Discover.

Btw with Plasma 5 it worked fine.

[sfalken]

Discover works fine, to upgrade Tumbleweed, with the proviso that it can’t resolve conflicts, and fails silently.

Which can be a consistent problem, if you’re using packman, or other repositories other than OSS and Non-OSS.

Which, when you’ve run into a situation where Discover fails to upgrade the system through the PackageKit backend, yes, you’re going to have to crack open a terminal, and run zypper ref && zypper dup to resolve it.

[TxTechnician]

Turns out that this is just related to flatpak. I’ll mess with it later. For any future readers:
sudo flatpak update