Bug 426310 - Error after updating
Summary: Error after updating
Status: RESOLVED NOT A BUG
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 5.19.5
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-08 13:45 UTC by Luís Dias
Modified: 2020-09-11 02:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Error flatpak (74.43 KB, image/png)
2020-09-09 22:03 UTC, Luís Dias
Details
Error authentication (79.49 KB, image/png)
2020-09-09 22:04 UTC, Luís Dias
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luís Dias 2020-09-08 13:45:02 UTC
SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Hello friends

After updating to base 20.04 discover does not update and displays a message of non-authorization, likewise the button to turn off the system also does not work, I can only update and turn off the system via terminal.
Comment 1 Nate Graham 2020-09-08 20:47:59 UTC
Can you attach a screenshot or a screen recording that depicts the problem?
Comment 2 Luís Dias 2020-09-09 22:03:04 UTC
Created attachment 131529 [details]
Error flatpak
Comment 3 Luís Dias 2020-09-09 22:04:50 UTC
Created attachment 131530 [details]
Error authentication
Comment 4 Nate Graham 2020-09-10 02:53:02 UTC
That's odd. However this is a problem with Flatpak itself, or how it's configured on your system. Discover is simply passing along the (not very helpful) error message. I would suggest that you contact your distro's developers. Perhaps they have not set up Flatpak correctly.
Comment 5 Luís Dias 2020-09-10 10:35:33 UTC
But I am using the KDE Neon distribution and there is also the error of the system shutdown, I believe that the standard user has corrupted permissions because when I use discover in root mode or use sudo poweroff everything works perfectly.
Comment 6 Nate Graham 2020-09-10 15:28:53 UTC
> the standard user has corrupted permissions
Could be, yeah.

> when I use discover in root mode
Yikes, don't do that. That. :) Doing things like that are likely what messed up the permissions in the first place. Or at least, doing that now has messed things up for the future. You'll need to fix the permissions yourself.
Comment 7 Luís Dias 2020-09-10 16:40:09 UTC
> when I use discover in root mode

I only did this because in the standard user it didn't work and the errors appeared after the update.
Comment 8 Nate Graham 2020-09-11 02:49:01 UTC
Now that you have done it, the permissions for all sorts of things are likely messed up and it will be impossible to debug the original issue. :(