I can run updates in Gnome but I’m stuck at “Fetching Updates” within Discover. The blue line is about 90% and never progresses. I have an internet connection and the google speedtest gives me a speed of about 450Mbps in Firefox in KDE.
Discover can take a while to get and process all the package metadata. I noticed it was very slow on older hardware, but runs fine for me on newer, better resourced hardware. Are you able to increase the memory and/or vcpu for your vm guest?
I don’t think that makes any difference. I’ve let it sit overnight before with no result. But I just put it to 8GB of RAM and 6 processors and let it sit for almost 2 hours. This is the new screenshot and you can see there is little to no change from before.
1 Like
If you run journalctl -f in the background while it runs, do you see any clues about it failing to resolve software sources, etc.?
try with
pkcon refresh force
then restart and check if that solves the issue.
No joy with
pkcon refresh force
and then a reboot.
I don’t know what to look for so I don’t know if these starts and stops are related to your question. But here is the result of the command
journalctl -f
[parallels@fedora ~]$ journalctl -f
Aug 17 14:24:34 fedora systemd[1]: Reached target multi-user.target - Multi-User System.
Aug 17 14:24:34 fedora systemd[1]: Reached target graphical.target - Graphical Interface.
Aug 17 14:24:34 fedora systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP…
Aug 17 14:24:34 fedora audit[3068]: SYSTEM_RUNLEVEL pid=3068 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_
r:init_t:s0 msg=‘old-level=N new-level=5 comm=“systemd-update-utmp” exe=“/usr/lib/systemd/systemd-update-utmp” hostname
=? addr=? terminal=? res=success’
Aug 17 14:24:34 fedora systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Aug 17 14:24:34 fedora systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.
Aug 17 14:24:34 fedora systemd[1]: Startup finished in 705ms (kernel) + 3.906s (initrd) + 29.436s (userspace) = 34.048s
.
Aug 17 14:24:34 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t
:s0 msg=‘unit=systemd-update-utmp-runlevel comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? r
es=success’
Aug 17 14:24:34 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:
s0 msg=‘unit=systemd-update-utmp-runlevel comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? re
s=success’
Aug 17 14:24:38 fedora PackageKit[2336]: get-updates transaction /690_eebbdcde from uid 1000 finished with success afte
r 144ms
Aug 17 14:24:44 fedora systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Aug 17 14:24:44 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:
s0 msg=‘unit=systemd-hostnamed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Aug 17 14:24:44 fedora audit: BPF prog-id=0 op=UNLOAD
Aug 17 14:24:44 fedora audit: BPF prog-id=0 op=UNLOAD
This is the only line that’s obviously relevant and it looks normal to me.
Why would anyone even use KDE’s disKover, or Gnome’s software-center to update their system in the first place? They both drain resources with no end in sight and try to make Windows-Update seem like Cheetah running through the savannah.
Escapes me, really!
I daily do this in terminal (regardless of my WM or DE):
sudo dnf upgrade && flatpak update
About once a week, I do
sudo dnf upgrade --refresh && flatpak update
It is the real cheetah, and it beats all beforementioned graphical software management systems by eons in time when it comes to updating your system!
Plus, searching for new packages to install may well be done through browsing the web, instead. Just search for the terms “Fedora” plus “package-name” or the type of software you are looking for.
It usually is much faster (and more precise), too.
People have different preferences and those are both supported means of managing software on Fedora. It’s a completely valid question, even if you have a different preference.
I wasn’t questioning the vailidity of the OP’s post. Just trying to give some hints on updating Fedora in a much, much quicker way.
I did try his commands in Konsole. But I still seem to have un-updated apps as the taskbar keeps telling me I have updates.
In regards to using the terminal. I’m a mild computer geek. I’m a RE Broker not a programmer. I’d like to get away from Mac, Chrome OS and Windows to something more secure. I think the only way to grow this Linux community is to be able to operate Linux desktop without the Terminal. Just as you can use the Terminal in Mac if you want to, but you don’t have do and can get done just about anything without ever using the Terminal. This is how Linux needs to operate. So I don’t argue that his Terminal commands may be faster, but due to their technical nature it’s not something Linux needs to be leaning on going forward if it wants to grow Linux past the Server community.
I agree with this sentiment, and apparent bugs such as this should be reported. It is likely that something may be not performing as it should and the lack of messages or info about where the hang is makes it almost impossible to track down.
Please report the bug at bugzilla.redhat.com.
For a work-around the use of the command line to do the update may allow finishing it properly, but this should not happen without some means for a gui user to know the actual cause.
1 Like
I happens, because Discover is still running in the background, before and after updating via terminal (konsole). You could set discover to not run on startup, or even delete it completely, which you probably won’t anyway… as per your ideological stance. Fedora certainly is following your logic to be a hastle-free point-and-click adventure.
But if you really want a more secure system, as you say, there will be no way around learning some terminal commands, and how the whole system operates beyond a GUI.
Just sayin’. Have a nice one!
Ivanhoe, I appreciate your attempts to resolve the problem but I think it would be more helpful for you to move on while the rest of us try to fix the issue.
no you have to restart system after updating with command line
Nah, you can do a pkcon refresh after. Generally, the GUI updates process dnf, flatpak, and fwupdmgr, and some of those (esp fwupdmgr) require a reboot, so it’s still possible to have real pending updates after a dnf update, but Discover has its own Metadata cache and may be out of date until the next packagekit refresh.