Hi
I'm running Fedora 29 and some time ago the Gnome Software Updater stopped working.
It informs me that there are new updates available and I press the Download button. After a while the button changes to Restart and Update and I press it, so the computer reboots and after that it briefly displays Installing new updates; this could take a while. But then it just reboots right away and when the system comes up but no updates have been installed. Gnome Software Updater displays the same software packages as available for updating. If I run yum update, then the software packages are updated just fine.
Any idea what's wrong here?
Could this problem block me from doing an upgrade to Fedora 30?
Cheers Robin
On Sun, 2019-09-15 at 10:51 +0200, Robin Lee wrote:
I'm running Fedora 29 and some time ago the Gnome Software Updater stopped working.
It informs me that there are new updates available and I press the Download button. After a while the button changes to Restart and Update and I press it, so the computer reboots and after that it briefly displays Installing new updates; this could take a while. But then it just reboots right away and when the system comes up but no updates have been installed. Gnome Software Updater displays the same software packages as available for updating. If I run yum update, then the software packages are updated just fine.
Any idea what's wrong here?
Could this problem block me from doing an upgrade to Fedora 30?
No ideas what could be wrong here?
On 9/15/19 1:51 AM, Robin Lee wrote:
I'm running Fedora 29 and some time ago the Gnome Software Updater stopped working.
It informs me that there are new updates available and I press the Download button. After a while the button changes to Restart and Update and I press it, so the computer reboots and after that it briefly displays Installing new updates; this could take a while. But then it just reboots right away and when the system comes up but no updates have been installed. Gnome Software Updater displays the same software packages as available for updating. If I run yum update, then the software packages are updated just fine.
I hope you mean "dnf update".
Any idea what's wrong here?
Try running "dnf system-upgrade log", although that probably doesn't work for regular offline updates. If it gives you a log from the right time, then run "dnf system-upgrade log --number=1" (replace 1 with the right log number). See if you can find an error message.
If that didn't work, then run "journalctl --list-boots" and find the one for the right time. Then run "journalctl -b -1" (again replace with the right number).
Could this problem block me from doing an upgrade to Fedora 30?
It might.
On 9/17/19 4:10 AM, Samuel Sieb wrote:
On 9/15/19 1:51 AM, Robin Lee wrote:
I'm running Fedora 29 and some time ago the Gnome Software Updater stopped working.
It informs me that there are new updates available and I press the Download button. After a while the button changes to Restart and Update and I press it, so the computer reboots and after that it briefly displays Installing new updates; this could take a while. But then it just reboots right away and when the system comes up but no updates have been installed. Gnome Software Updater displays the same software packages as available for updating. If I run yum update, then the software packages are updated just fine.
I hope you mean "dnf update".
I believe the OP is talking about the "gnome-software" utility. This, I'm pretty sure, relies on package-kit on the back-end.
On 9/16/19 4:09 PM, Ed Greshko wrote:
On 9/17/19 4:10 AM, Samuel Sieb wrote:
On 9/15/19 1:51 AM, Robin Lee wrote:
packages as available for updating. If I run yum update, then the software packages are updated just fine.
I hope you mean "dnf update".
I believe the OP is talking about the "gnome-software" utility. This, I'm pretty sure, relies on package-kit on the back-end.
You missed that line at the end.
On 9/17/19 9:02 AM, Samuel Sieb wrote:
On 9/16/19 4:09 PM, Ed Greshko wrote:
On 9/17/19 4:10 AM, Samuel Sieb wrote:
On 9/15/19 1:51 AM, Robin Lee wrote:
packages as available for updating. If I run yum update, then the software packages are updated just fine.
I hope you mean "dnf update".
I believe the OP is talking about the "gnome-software" utility. This, I'm pretty sure, relies on package-kit on the back-end.
You missed that line at the end.
I don't know what I missed.
yum is now redirecting to DNF and that works.
I think he is saying "gnome-software" doesn't work while yum (dnf) does.
What am I missing or misreading?
On 9/17/19 7:09 AM, Ed Greshko wrote:
This, I'm pretty sure, relies on package-kit on the back-end.
A note here. Not being an active gnome user I relied on my memory as opposed to not testing. Part of that was due (excuse) to not having a working gnome VM.
I recalled that doing updates on gnome wouldn't result in info recorded with dnf (history).
Well, I just installed a F31 gnome VM and found that updates and installs using the gnome-software util do what I recall it not doing in the past.
I don't know enough about how gnome-software goes about setting up the reboot process to do the updates. That appears to me to be the question.
On Tue, 2019-09-17 at 09:46 +0800, Ed Greshko wrote:
Well, I just installed a F31 gnome VM and found that updates and installs using the gnome-software util do what I recall it not doing in the past.
The OP is using F29, not the (unlreleased) F31. Don't know if that makes any difference in this case.
poc
On 9/17/19 6:52 PM, Patrick O'Callaghan wrote:
On Tue, 2019-09-17 at 09:46 +0800, Ed Greshko wrote:
Well, I just installed a F31 gnome VM and found that updates and installs using the gnome-software util do what I recall it not doing in the past.
The OP is using F29, not the (unlreleased) F31. Don't know if that makes any difference in this case.
Yeah, I was thinking about that after writing what I did. I may put up a F29 VM tomorrow just for my own edification.
On Mon, 2019-09-16 at 13:10 -0700, Samuel Sieb wrote:
If that didn't work, then run "journalctl --list-boots" and find the one for the right time. Then run "journalctl -b -1" (again replace with the right number).
Thanks for the help. I did run "journalctl -b -1" after a failed try to use Gnome Software to update to latest software packages. And it seems to give me the log from the failed software update. I found the following in the log that looks quite suspicious
python3[1168]: detected unhandled Python exception in '/usr/bin/dnf' python3[1168]: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory python3[1168]: error sending data to ABRT daemon: dnf[1168]: Traceback (most recent call last): dnf[1168]: File "/usr/bin/dnf", line 58, in <module> dnf[1168]: main.user_main(sys.argv[1:], exit_code=True) dnf[1168]: File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 192, in user_main dnf[1168]: errcode = main(args) dnf[1168]: File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 64, in main dnf[1168]: return _main(base, args, cli_class, option_parser_class) dnf[1168]: File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 95, in _main dnf[1168]: cli.configure(list(map(ucd, args)), option_parser()) dnf[1168]: File "/usr/lib/python3.7/site-packages/dnf/cli/cli.py", line 954, in configure dnf[1168]: self.command.configure() dnf[1168]: File "/usr/lib/python3.7/site-packages/dnf- plugins/system_upgrade.py", line 329, in configure dnf[1168]: self._call_sub("configure") dnf[1168]: File "/usr/lib/python3.7/site-packages/dnf- plugins/system_upgrade.py", line 341, in _call_sub dnf[1168]: subfunc() dnf[1168]: File "/usr/lib/python3.7/site-packages/dnf- plugins/system_upgrade.py", line 404, in configure_upgrade dnf[1168]: repo.gpgcheck = repo.id in self.state.gpgcheck_repos dnf[1168]: TypeError: argument of type 'NoneType' is not iterable systemd[1]: dnf-system-upgrade.service: Main process exited, code=exited, status=1/FAILURE audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-system-upgrade comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' systemd[1]: dnf-system-upgrade.service: Failed with result 'exit-code'. systemd[1]: Failed to start System Upgrade using DNF. systemd[1]: dnf-system-upgrade.service: Triggering OnFailure= dependencies. systemd[1]: Starting System Upgrade using DNF failed...
This error could be the main culprit, but not sure what to do about it TypeError: argument of type 'NoneType' is not iterable
Cheers Robin
On 9/17/19 8:21 PM, Robin Lee wrote:
Thanks for the help. I did run "journalctl -b -1" after a failed try to use Gnome Software to update to latest software packages. And it seems to give me the log from the failed software update. I found the following in the log that looks quite suspicious
python3[1168]: detected unhandled Python exception in '/usr/bin/dnf' python3[1168]: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory python3[1168]: error sending data to ABRT daemon:
That does seem to be the issue.
I created an F29 VM. When I booted I logged in and found the process /usr/sbin/abrtd -d -s running.
I killed it and tried to do an update with the gnome-software tool and got the same result as you did.
What is the output of
systemctl --no-pager -l status abrtd
On Tue, 2019-09-17 at 20:45 +0800, Ed Greshko wrote:
On 9/17/19 8:21 PM, Robin Lee wrote:
Thanks for the help. I did run "journalctl -b -1" after a failed try to use Gnome Software to update to latest software packages. And it seems to give me the log from the failed software update. I found the following in the log that looks quite suspicious
python3[1168]: detected unhandled Python exception in '/usr/bin/dnf' python3[1168]: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory python3[1168]: error sending data to ABRT daemon:
That does seem to be the issue.
I created an F29 VM. When I booted I logged in and found the process /usr/sbin/abrtd -d -s running.
I killed it and tried to do an update with the gnome-software tool and got the same result as you did.
What is the output of
systemctl --no-pager -l status abrtd
It is active and running, but that of course is after a normal boot up. Should ABRT also be running in the special boot process when Gnome Software tries to update the software packages?
Cheers Robin
On 9/17/19 8:52 PM, Robin Lee wrote:
On Tue, 2019-09-17 at 20:45 +0800, Ed Greshko wrote:
On 9/17/19 8:21 PM, Robin Lee wrote:
Thanks for the help. I did run "journalctl -b -1" after a failed try to use Gnome Software to update to latest software packages. And it seems to give me the log from the failed software update. I found the following in the log that looks quite suspicious
python3[1168]: detected unhandled Python exception in '/usr/bin/dnf' python3[1168]: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory python3[1168]: error sending data to ABRT daemon:
That does seem to be the issue.
I created an F29 VM. When I booted I logged in and found the process /usr/sbin/abrtd -d -s running.
I killed it and tried to do an update with the gnome-software tool and got the same result as you did.
What is the output of
systemctl --no-pager -l status abrtd
It is active and running, but that of course is after a normal boot up. Should ABRT also be running in the special boot process when Gnome Software tries to update the software packages?
I don't know. But, I'm guessing that it my be dying at some point after you hit the button to start the update.
Assuming you're now rebooted after a previous failed attempt what is the output of
journalctl -b -1 --unit=abrtd
On Tue, 2019-09-17 at 21:03 +0800, Ed Greshko wrote:
On 9/17/19 8:52 PM, Robin Lee wrote:
On Tue, 2019-09-17 at 20:45 +0800, Ed Greshko wrote:
On 9/17/19 8:21 PM, Robin Lee wrote:
Thanks for the help. I did run "journalctl -b -1" after a failed try to use Gnome Software to update to latest software packages. And it seems to give me the log from the failed software update. I found the following in the log that looks quite suspicious
python3[1168]: detected unhandled Python exception in '/usr/bin/dnf' python3[1168]: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory python3[1168]: error sending data to ABRT daemon:
That does seem to be the issue.
I created an F29 VM. When I booted I logged in and found the process /usr/sbin/abrtd -d -s running.
I killed it and tried to do an update with the gnome-software tool and got the same result as you did.
What is the output of
systemctl --no-pager -l status abrtd
It is active and running, but that of course is after a normal boot up. Should ABRT also be running in the special boot process when Gnome Software tries to update the software packages?
I don't know. But, I'm guessing that it my be dying at some point after you hit the button to start the update.
Assuming you're now rebooted after a previous failed attempt what is the output of
journalctl -b -1 --unit=abrtd
It says "No entries"
But, what about the error message I pointed out earlier TypeError: argument of type 'NoneType' is not iterable
Cheers Robin
On 9/17/19 9:10 PM, Robin Lee wrote:
But, what about the error message I pointed out earlier TypeError: argument of type 'NoneType' is not iterable
The part of error you quoted earlier was
dnf[1168]: File "/usr/lib/python3.7/site-packages/dnf- plugins/system_upgrade.py", line 404, in configure_upgrade dnf[1168]: repo.gpgcheck = repo.id in self.state.gpgcheck_repos dnf[1168]: TypeError: argument of type 'NoneType' is not iterable systemd[1]: dnf-system-upgrade.service: Main process exited,
That file doesn't exist on my system since I don't have dnf-plugin-system-upgrade installed on that VM.
It is unclear to me why that is used when just updating packages.
Since you're not doing a system upgrade I'd consider erasing that package to see if it helps. You can always reinstall.
On Tue, 2019-09-17 at 22:44 +0800, Ed Greshko wrote:
On 9/17/19 9:10 PM, Robin Lee wrote:
But, what about the error message I pointed out earlier TypeError: argument of type 'NoneType' is not iterable
The part of error you quoted earlier was
dnf[1168]: File "/usr/lib/python3.7/site-packages/dnf- plugins/system_upgrade.py", line 404, in configure_upgrade dnf[1168]: repo.gpgcheck = repo.id in self.state.gpgcheck_repos dnf[1168]: TypeError: argument of type 'NoneType' is not iterable systemd[1]: dnf-system-upgrade.service: Main process exited,
That file doesn't exist on my system since I don't have dnf-plugin- system-upgrade installed on that VM.
It is unclear to me why that is used when just updating packages.
Since you're not doing a system upgrade I'd consider erasing that package to see if it helps. You can always reinstall.
Yes, I removed the upgrade plugin and then Gnome Software was again able to update software packages.
Thanks Robin
-
Ed Greshko -
Patrick O'Callaghan -
Robin Lee -
Samuel Sieb