Hi,
I have upgraded all my machines (3 laptops, 2 desktop warhorses) using fedup and all went smoothly. The only thing that does not work is openconnect with NetworkManager. I got the following when I looked into it.
Could not load editor VPN plugin for 'org.freedesktop.NetworkManager.openconnect' (missing plugin file "/usr/lib64/NetworkManager/libnm-vpn-plugin-openconnect-editor.so")
Where do I get this plugin, and more importantly, why is it not pulled in with an upgrade/install?
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.
Thanks, Fedora developers!!
Best wishes, Ranjan
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".
Where do I get this plugin, and more importantly, why is it not pulled in with an upgrade/install?
That's a good question.
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?
Samuel,
Thanks for the response!
On Sat, 26 Nov 2016 11:53:55 -0800 Samuel Sieb samuel@sieb.net 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?
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).
Thanks again!
Best wishes, Ranjan
On 11/26/2016 04:04 PM, Ranjan Maitra wrote:
On Sat, 26 Nov 2016 11:53:55 -0800 Samuel Sieb samuel@sieb.net 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.
On Sat, 26 Nov 2016 17:46:35 -0800 Samuel Sieb samuel@sieb.net wrote:
On 11/26/2016 04:04 PM, Ranjan Maitra wrote:
On Sat, 26 Nov 2016 11:53:55 -0800 Samuel Sieb samuel@sieb.net 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
On Sat, 2016-11-26 at 20:33 -0600, Ranjan Maitra wrote:
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.
Sounds like more of a rolling release model, similar to Arch. That would be a big change.
poc
On 11/26/2016 10:36 AM, Ranjan Maitra wrote:
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.
Personally, I've always thought it was a waste of time to reboot, upgrade and reboot again. Download everything, upgrade and reboot once seems much more time effective.
-
Joe Zeff -
Patrick O'Callaghan -
Ranjan Maitra -
Samuel Sieb