Update Issue in Discover

Help
,
1

Update section in discover remains on the fetching updates phase indefinitely,
Screenshot_20250217_104526
However when I run the update command in the terminal, it says everything is up to date. Is there a way to fix this?

2

Hi - just to check, which command-line update command are you running?

Do you get any error messages printed to terminal if you try running plasma-discover at a command line?

3

I ran sudo pkcon update to update my system, which is what kde neon requires. I did not get any error messages when I ran plasma-discover in my terminal.

4

For what itā€™s worth, pkcon doesnā€™t require being run as root - it will prompt with a polkit GUI prompt when needed :slight_smile:

Does running pkcon repair help?

What sources do you have setup and enabled in Discover? Pasting in the ones from my basic Neon VM just as a comparison:

image
image679Ɨ527 68 KB

5

I ran pkcon repair, the updates fetching indefinitely issue is still there, am I suppose to restart after running the repair or not? Here is a screenshot of my enabled sources in discover:

Screenshot_20250218_181224
Screenshot_20250218_1812241108Ɨ628 45 KB

6

Maybe see if itā€™s still an issue after disabling lvfs-testing and the Google Chrome one, just to try the ā€œstockā€ setup?

7

Unfortunately, that did not fix it, Iā€™m probably guessing the update manager is trying to update a package that may be broken or missing in my system, I may try a fresh install if any big issues come from the updates not wanting to show.

8

I seem to have the same issue, although I have no idea what it causing it just yet.
However, running pkcon get-distro-upgrades also never returns, but does show errors. (Found that here)

$ pkcon get-distro-upgrades
Getting upgrades                        [=========================]         
Finished                                [                         ] (0%)  
(pkcon:30972): GLib-GIO-CRITICAL **: 15:34:48.751: g_task_return_error: assertion 'error != NULL' failed

(pkcon:30972): GLib-GIO-CRITICAL **: 15:34:48.751: GTask 0x5588c58c4a80 (source object: 0x5588c58c6240, source tag: 0x73f8baa01ed0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
                                        [=========================]         
Waiting in queue                        [            ==           ]

I suspect this might be the root cause, but so far I canā€™t get pkcon to spit anything useful about what is happening.

9

Is it possible for you to update via discover or does that stall for you as well just like the terminal? I will also try the command you ran in your terminal to get better insight on what your running into if that helps.

10

It looks like I get the same error as you when running pkcon get-distro-upgrades.

Screenshot_20250220_104821
Screenshot_20250220_104821805Ɨ136 17.5 KB

11

Discover just hangs on ā€˜Fetching updatesā€¦ā€™ seemingly forever, that was the first issue I ran into. I only ran pkcon to see it that would work.

I also just manually installed packagekit and packagekit-tools version 1.3.0 from the Ubuntu oracular repositories but that does not resolve this.

I can run pkcon refresh, pkcon get-updates and pkcon update to install updates.

12

So it would seem you have the exact issue Iā€™m experiencing as I too can update via pkcon update. I will take a further look into it and let you know what I find.

13

Getting and using gnome software center is what Iā€™m doing as a temporary solution as gnome software center seems to be working perfectly fine. sudo apt install gnome-software

14

Iā€™m having the same issue. The ā€œGetting Updatesā€ progress bar in Discover goes to the end and then hangs. Pkcon works for getting updates. Here are the repositories I get with pkcon refresh.

image
image1076Ɨ632 82.4 KB

15

I came here to report the same issue. Looks like you beat me to it. Doscover just hangs on ā€œfetching updatesā€. Pkcon works normally.

16

I might try viewing discover in a virtual machine on a clean kde neon without any modifications to see if itā€™s an issue with stock kde neon.

17

I tried other bases with kde like fedora and ubuntu and they both are without the issue in the discover center, meaning it is most likely an issue with neon.

18

Note that Plasma Discover handles not only a distros native packages but also Flatpaks, snaps, some firmware, and KDE Store theme components.

The pkcon command only covers the native packages, it is just a wrapper using distroā€™s native tools (apt in this case) so it is very likely that it is one of the others causing the hang.

I suspect the firmware update (fwupmgr)
Iā€™ve seen this in the past but it has been a while, and it was only after I had enabled the ā€œtestingā€ option.
Try unchecking some or all of the firmware sources and see if that helps.

If it was an issue with Ubuntu and neon repos, PPAs, or other external apt sources, there would be some sort of error when running pkcon or apt.

But it could be a bug in the version of things in neon which has newer stuff than Fedora at the moment , I think, and definitely whatā€™s in Ubuntu/Kubuntu

Iā€™m not seeing this here on my neon system, and I have a variety of sources.

1 Like
19

Thanks for the input, I have already tried disabling certain sources, I did end up switch to fedora kde, and I havenā€™t had any issues since then.

20

I have discovered a workaround that works.

  1. Open Discover, navigate to the updates tab and wait until it hangs.
  2. Close Discover.
  3. Turn off networking
  4. Open Discover. You should get an error about networking. Ignore.
  5. Click on the updates tab. You may get another error. You should now see the list of updatable files.
  6. Turn networking back on. You can now install the updates.