Re: dnf is "broken"

2018-12-31 Thread Kevin Cummings
On 12/31/18 11:13 AM, stan wrote: > I just ran an update on fc28.x86_64 and there were no problems. Well, > other than package conflicts like snmp and clamav that are keeping them > from updating, and have been for a while. When I tried looking at snmp > there were a lot of conflicts, and it wasn

Re: dnf is "broken" [not anymore]

2018-12-31 Thread Kevin Cummings
On 12/31/18 7:41 AM, Jeandet Alexis wrote: > Hi Kevin, > > did you try a 'dnf clean all'? No, I didn't. Hmmm, it seems to have done the job. Thank-you. -- Kevin J. Cummings cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us kjch...@icloud.com Registered Linux User #1232 (http://www.

Re: dnf is "broken"

2018-12-31 Thread stan
On Mon, 31 Dec 2018 00:13:15 -0500 Kevin Cummings wrote: > I last updated my laptop on 12/26. It is running fc28.x86_64 > > Today I tried to run dnf update: > > > _hawkey.Exception: > > repo_add_solv() has failed. > > Is it Fedora 28? dnf? some dnf dependency? or my laptop? that is > br

Can't create a new VM with Virtual Machine Manager

2018-12-31 Thread Patrick O'Callaghan
I currently run a couple of VMs (one Windows 10 and one Fedora Server) under QEMU/KVM. I wanted to create a new one and got this: Unable to complete install: 'internal error: process exited while connecting to monitor: 2018-12-31T14:23:14.816147Z qemu-system-x86_64: can't apply global IvyBrid

Re: bis repetita.... wrong grub.cfg

2018-12-31 Thread Jeandet Alexis
Hi François, I think I have a similar problem with an old server I might have installed with a Fedora 26 or 27 where I used to have issues in the past kernel updates used to generated grub.cfg with plenty of '=' chars at the end of the file. It seemed to be reoslved until last week, I did an updat

Re: dnf is "broken"

2018-12-31 Thread Jeandet Alexis
Hi Kevin, did you try a 'dnf clean all'? Then you didn't do any 'sudo pip intall ' on your machine or set the PYTHONPATH? You can easily break your system whide packages by dooing this. Alexis. Le lundi 31 décembre 2018 à 00:13 -0500, Kevin Cummings a écrit : > I last updated my laptop on 12/26.