On 11/21/18 9:14 AM, Kay Schenk wrote: > > On 11/20/2018 05:35 AM, Johnny Hughes wrote: >> On 11/19/2018 01:38 AM, Nicolas Kovacs wrote: >>> Le 18/11/2018 à 15:14, Yan Li a écrit : >>>> The recommended method for undo an update is >>>> https://access.redhat.com/solutions/64069, but it's not supported if >>>> glibc, >>>> kernel, or selinux are changed. I'd give it a try if the system is not >>>> critical. Make backups first. >>>> >>>> Some other people's experience on downgrading a point release: >>>> https://access.redhat.com/discussions/2933711 >>>> >>>> If you couldn't read that article, just search "yum history undo". >>> >>> That didn't work unfortunately. The lesson learned here is : >>> >>> * CR repository works great for servers >>> >>> * never use it to upgrade a desktop > > Issues for me as well doing this CR upgrade yesterday. > > Two particularly upsetting though I have not investigated yet: > > * the normal boot menu doesn't appear. The back up kernels and setup may > have actually been removed. I need to look into this. Good news on the above. With new updates pushed today, my boot menu is back. \o/ This saved me digging into grub2 setup. So thank you. > > * My console font is now HUGE! This is still the case, but I'm sure I can deal with this. > > Likely due to a bad X server init which set display at like 640 x 360 or > something. > > Gnome desktop. > > Maybe more to come as I look into this a bit more today. > >> >> I used it on all my desktops .. they work great for me .. is your >> desktop Gnome/KDE for something from EPEL or Nux? >> >> >> >> >> >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> https://lists.centos.org/mailman/listinfo/centos >>