Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Appcenter stays apparently doing nothing #2096

Closed
Gabriel-p opened this issue Oct 26, 2023 · 13 comments · Fixed by #2205
Closed

Appcenter stays apparently doing nothing #2096

Gabriel-p opened this issue Oct 26, 2023 · 13 comments · Fixed by #2205

Comments

@Gabriel-p
Copy link
Contributor

What Happened?

Appcenter says there are updates available so I opened it. App looks like this when in fact there are updates available (I checked in terminal)

Captura de pantalla de 2023-10-26 17 13 53

Steps to Reproduce

Open Appcenter when an update is informed as available

Expected Behavior

Updates should be shown

OS Version

7.x (Horus)

Software Version

Latest release (I have run all updates)

Log Output

No response

Hardware Info

No response

@garzajual
Copy link

Me too.

@adrianosiqueira
Copy link

Same here, but I am running it in VirtualBox 7.0.12.

@xvelasqu
Copy link

I solved this by running:
flatpak repair --system
flatpak repair --user

@sauntor
Copy link

sauntor commented Dec 7, 2023

I solved this by running: flatpak repair --system flatpak repair --user

It can't work for me

@sauntor
Copy link

sauntor commented Dec 7, 2023

But if you launch AppCenter from terminal, it may works sometimes.

io.elementary.appcenter --g-fatal-warnings -u

@donnie-j
Copy link

This appears to be a long running problem, I think perhaps related to threading model. If the processes it's running do something unexpected it just hangs, and the WM eventually asks if you want to kill it.

Fixing flatpak (IMHO, flatpak is yet another bad idea) might mitigate for a while, but the problem returns. This needs to be fixed as a high priority, I've had to revert to apt-get for just about everything.

@JohnDumpling
Copy link
Contributor

flatpak-update currently shows no available updates, but AppCenter never shows any available updates anymore. Confirmed on 3 devices of various age including a virtual machine on my main laptop. I switched one device to Zorin OS (as it has to be reliable, it is for a relative), one I kept on eOS (for testing purposes). I'm patient, hopefully the proposed separation of flatpak & system updates will fix this high priority issue.

@zeebok
Copy link
Contributor

zeebok commented Feb 22, 2024

I can confirm this issue and think I know the cause of it. It seems like if you go to the updates page while the little "Checking for Updates" tool tip at the bottom is still going, it should reveal it properly otherwise you will see what you describe. I am going to try a fix this weekend.

@Gabriel-p
Copy link
Contributor Author

Gabriel-p commented Apr 29, 2024

What @zeebok says appears to be right. I you wait until the update checking is finished, it won't show the available updates. You have to click the orange arrow icon to the top right while the checking is happening

@zeebok
Copy link
Contributor

zeebok commented May 19, 2024

I do also notice that this isn't a present issue in OS8 with the newer iterations of AppCenter, and the portion of code I thought was the cause is not really changed between the versions. I will have to dive a little deeper to figure out what is happening.

@diogopessoa
Copy link

I also face this same problem in the stable 7.1 version of elementary. But in the development version 8, I haven't had this problem so far. I'll keep testing to see if this behavior happens again or not.

@zeebok
Copy link
Contributor

zeebok commented Aug 16, 2024

I found a fix for this in OS 7 and if it gets merged will mean it will be patched for everyone

@ryonakano ryonakano linked a pull request Aug 18, 2024 that will close this issue
@ryonakano
Copy link
Member

Closing as fixed in #2205—it looks like the Fixes keyword in the PR didn't work here, maybe because the target branch is not main. Thank you @zeebok for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants