Re: Fedora 24 -> 25 upgrade smooth and successful (but for one small vpn openconnect issue)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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")

What does "rpm -q NetworkManager-openconnect" show?  If it says not
installed, then run "dnf install NetworkManager-openconnect".

$ rpm -q NetworkManager-openconnect
NetworkManager-openconnect-1.2.3-0.20160606git5009f9.fc25.x86_64

It is indeed, installed (as it was before the upgrade).


Where do I get this plugin, and more importantly, why is it not pulled in with an upgrade/install?

That's a good question.

Yes, indeed, so where do I find the solution?

It's actually NetworkManager-openconnect-gnome that you need, which also explains why it wasn't included because it's a new package.

As an aside, while very smooth, I think that the upgrade itself can do with a bit more installation before the reboot: perhaps some of the things that are applications can be installed after the other ones have upgraded and after the system has come up since upgrade during the boot process leaves the computer pretty unusable. Just a thought: I have no idea if it is possible to implement what I am suggesting (or something similar) but I want to stress again that this was a very smooth upgrade in general.

Sorry, I have no idea what you are saying here.  Can you try explaining
again?

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.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]
  Powered by Linux