On Sat, 26 Nov 2016 17:46:35 -0800 Samuel Sieb <samuel@xxxxxxxx> wrote: > On 11/26/2016 04:04 PM, Ranjan Maitra wrote: > > On Sat, 26 Nov 2016 11:53:55 -0800 Samuel Sieb <samuel@xxxxxxxx> wrote: > >> On 11/26/2016 10:36 AM, Ranjan Maitra wrote: > >>> Could not load editor VPN plugin for 'org.freedesktop.NetworkManager.openconnect' (missing plugin file "/usr/lib64/NetworkManager/libnm-vpn-plugin-openconnect-editor.so") > >>> > > > It's actually NetworkManager-openconnect-gnome that you need, which also > explains why it wasn't included because it's a new package. I see: I am surprised that it did not add this package during the upgrade, because it seems that NetworkManager-openconnect is pointless now without it. (I installed it and it works fine, so thanks again for that!) > > Sorry, my musings were not clear. I was thinking that a lot fewer of the files/rpms being upgraded have anything to do with the system. So, perhaps these rpms (eg kernel, glibc, openssh, etc) should be upgraded before boot and then once the user logs back in with the new system files, then s/he can continue working while other files (eg. firefox) get upgraded after login. Then waits of as much as 30-35 minutes for some of my systems could have been obviated. That is a suggestion which may not be possible to implement (but perhaps some modified version can be). > > > That would be very difficult and not possible anyway, because you will > have mismatched library requirements during the second part. I wonder if this would be impossible to implement, completely. After all, we do go through updates just fine, when whole libraries are updated sometimes. It depends on how it is/can be done. Thanks, Ranjan _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
