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
--
If simple questions can be answered with a simple google query then why are there so many of them?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
