In case of disaster, what is the procedure to downgrade (assuming I can get a network connection somehow)?

Rex Dieter wrote: > On 06/17/2011 10:17 AM, Neal Becker wrote: > >> In case of disaster, what is the procedure to downgrade (assuming I can get >> a network connection somehow)? > > yum history undo > or > yum downgrade \ > kde-plasma-networkmanagement \ > kde-plasma-networkmanagement-libs > > (plus any other subpkg's you may have installed). > > -- Rex I see in /var/log/messages that on the update, an infinite syslog loop caused my system to be unresponsive, with thousands of these messages: Jun 17 09:50:15 nbecker1 NetworkManager[798]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-W34O4

On 06/17/2011 02:06 PM, Neal Becker wrote: > Sorry guys, let me know when this one's fully baked. > > I tried using plasma to edit wireless connection (actually, just wanted to > look > at it). It went into infinite loop again. > > Jun 17 12:58:25 nbecker1 NetworkManager[806]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-W34O4 Try restarting NetworkManager when this starts to happen. I know I had to fight with it quite a bit on my laptop before it finally got stable. I am a revision behind though.

Sorry guys, let me know when this one's fully baked. I tried using plasma to edit wireless connection (actually, just wanted to look at it). It went into infinite loop again.

Rex Dieter wrote: > On 06/17/2011 12:06 PM, Neal Becker wrote: >> Sorry guys, let me know when this one's fully baked. >> >> I tried using plasma to edit wireless connection (actually, just wanted to >> look >> at it). It went into infinite loop again. > > So, you just went into the connection editor, and didn't actually edit > anything? I'm just looking for a recipe to trigger this. > > -- Rex Yes, I believe I did manage connections, then click on a wireless connection.

_______________________________________________ kde mailing list kde(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org

Patrick Boutilier wrote: > I can reproduce by going to Manage Connections, selecting the wireless > AP I want and clicking the Edit button. At this point a dialog box comes > up that says "No agents were available for this request". The title of > the dialog box is "Error - KDE Control Module" . Click "Ok" and the > "Edit Network Connection" box does come up. Select "Wireless Security" > tab and enter WPA/WPA2 Personal password. As soon as I click "Ok" > NetworkManager goes haywire. > > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > > > And so on... > > > At this point the only way out is to kill -9 NetworkManager. WPA2 > password never gets saved but I am able to connect if I type the > password in each time when the dialog box pops up asking for the password. Can somebody please report this to kde-plasma-networkmanagement upstream? I guess upstream is not aware of it because this is only reproducible with the ifcfg-rh plugin.

Kevin Kofler _______________________________________________ kde mailing list kde(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org

Patrick Boutilier wrote on Saturday 18 June 2011: > On 06/17/2011 02:58 PM, Neal Becker wrote: >> Rex Dieter wrote: >>> On 06/17/2011 12:06 PM, Neal Becker wrote: >>>> Sorry guys, let me know when this one's fully baked. >>>> >>>> I tried using plasma to edit wireless connection (actually, just wanted >>>> to look >>>> at it). It went into infinite loop again. >>> >>> So, you just went into the connection editor, and didn't actually edit >>> anything? I'm just looking for a recipe to trigger this. >>> >>> -- Rex >> >> Yes, I believe I did manage connections, then click on a wireless >> connection. > > I can reproduce by going to Manage Connections, selecting the wireless > AP I want and clicking the Edit button. At this point a dialog box comes > up that says "No agents were available for this request". The title of > the dialog box is "Error - KDE Control Module" . Click "Ok" and the > "Edit Network Connection" box does come up. Select "Wireless Security" > tab and enter WPA/WPA2 Personal password. As soon as I click "Ok" > NetworkManager goes haywire. > > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating > /etc/sysconfig/network-scripts/ifcfg-WWOOD3 > > > And so on... > > > At this point the only way out is to kill -9 NetworkManager. WPA2 > password never gets saved but I am able to connect if I type the > password in each time when the dialog box pops up asking for the password. Did you test nm-applet? I could not try the new plasma-nm, but with nm-applet I'm seeing the same behavior of NetworkManager when I try to setup a WPA2 enterprise connection. So this might be a bug in NetworkManager itself instead of plasma-nm.

_______________________________________________ kde mailing list kde(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org

Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-WWOOD3 Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-WWOOD3 Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-WWOOD3 Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-WWOOD3 Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-WWOOD3 Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-WWOOD3 Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-WWOOD3 Jun 17 23:49:47 hplaptop NetworkManager[1956]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-WWOOD3

However, WPA2 password never gets saved to the wallet. Even though password appears to be saved when editing a connection it is lost after a reboot. Anybody else seeing this?

Next problem is with Openvpn plugin. Anybody have success or do you also get the "failed to connect: 'property 'user-name' invalid or not supported'." error?

Handling of WPA-EAP secrets looks badly broken: 1. Migration should create a IEEE_8021X_PASSWORD_FLAGS=user entry in the ifcfg-rh config file (probably a flag to set through the NM API), it fails to do that. (In particular, this means the connection fails to load entirely in NetworkManager and your configuration is completely lost unless you can deal with hand-editing config files.) 2. Migration should store the password in KWallet, it fails to do that. I have to enter it there manually. (In particular, this means the stored password is lost, because the original connections got deleted. If you don't remember it, you're screwed.)

3. Changing the password through the connection editing UI doesn't work! I tried to set a password of "test" first, then change it to the real password, it didn't do it. I had to manually find and edit the entry in kwalletmanager. (The average user would probably have had to delete and recreate the connection from scratch.)

Kevin Kofler wrote: > I've also had trouble with secrets with the new build. :-( Mine is working :-) Secrets must be being stored somewhere, because I have an infallible wireless connection.

> These bugs need manual workarounding in config files, or deleting and > recreating connections, both of which sucks as a user experience. Nope. I didn't do any manual configuring. I admit that I also logged in to gnome and entered the secret there, too, so that both kde and gnome have it. Could this new networkmanager plasmoid be accessing pam (or whatever it is that gnome uses) for the wireless network password?

> Now I don't know how to proceed, because the previously working build > doesn't work anymore, and this one doesn't work reliably either. I had absolutely no luck with the previous build. I was unable to get any wireless connection at all, only wired. This build is, as I said earlier, giving me no grief, only pleasure.

> Kevin Kofler wrote: > >> I've also had trouble with secrets with the new build. :-( > > Mine is working :-) Secrets must be being stored somewhere, because I have

I notice lots of lovely new things on the applet - under 'Band' it offers 2 choices: 'a' and 'b/g'. Will this be confusing to those with N - or those who think band is 20 or 40 Wide ?

Hi Kevin - well kinda but not really .. Well N supports wide bands - which for sure b/g do not. Don't know about a as it has been effectively largely deprecated

It would be helpful if you could explain exactly what this choice does to NM - what effect does it have on the connection?

This is all the fault of several bad aligning circumstances: The NetworkManager update broke the previous kde-plasma-networkmanagement build, forcing us to get the new one out ASAP. The NM update got tested, but apparently only by GNOME users and by KDE users testing the new kde-plasma- networkmanagement (for which it fixed a showstopper issue, which made us actually want that update pushed quickly), so nobody noticed that it broke the previous kde-plasma-networkmanagement build. (When it got noticed, it was too late, the update was already pushed as "stable".) Now, unfortunately, it looks like we have no other choice than getting the kde- plasma-networkmanagement update out no matter what it breaks. Kevin Kofler

Well, in particular, I'll be moving a new kde-plasma-networkmanagement-0.9-0.53.20110616git.nm09.fc15 build into f15's kde-testing repo shortly. As opposed to prior plasma-nm builds in f15 that use some hacks/patches in nm-0.9 to be backward compatible with nm-0.8 clients, these newer builds will use nm-0.9 in native mode. That's a lot of techno-gibberish, admittedly, but what it means is this native nm-0.9 support is the future. Moving forward, we'd like to get a native nm09 client into f15 as soon as possible, and that means we need to test, test, test this sucker. So, please go forth and do. Thank you.

What's the hubub in $SUBJECT mean? speak english man! Well, in particular, I'll be moving a new kde-plasma-networkmanagement-0.9-0.53.20110616git.nm09.fc15 build into f15's kde-testing repo shortly. As opposed to prior plasma-nm builds in f15 that use some hacks/patches in nm-0.9 to be backward compatible with nm-0.8 clients, these newer builds will use nm-0.9 in native mode. That's a lot of techno-gibberish, admittedly, but what it means is this native nm-0.9 support is the future. Moving forward, we'd like to get a native nm09 client into f15 as soon as possible, and that means we need to test, test, test this sucker. So, please go forth and do. Thank you.