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.
-- Rex
Rex Dieter wrote:
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.
-- Rex
I'm testing. First experience was bad - just updated and then logout/login. Pretty much locked up the machine. Had to force reboot. This means the upgrade path may not be possible - might have to wait for F16.
After reboot, seems to work on wired at least. Haven't tried wireless yet.
In case of disaster, what is the procedure to downgrade (assuming I can get a network connection somehow)?
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
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
Neal Becker wrote:
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
I see I now have:
/etc/sysconfig/network-scripts: total used in directory 236 available 42595680 -rw-r--r--. 1 root root 0 Jun 17 09:52 ifcfg-nbecker -rw-r--r--. 1 root root 258 Jun 17 09:52 ifcfg-W34O4 -rw-r--r--. 1 root root 180 Jun 17 09:50 ifcfg-eth0 1 -rw-r--r--. 1 root root 73 May 13 09:36 ifcfg-eth0
The 1st 3 were created by the kde-plasma-networkmanagement update.
1. Should I have two different ifcfg-eth0, ifcfg-eth0\ 1? Should I delete one of them?
2. As you can see, ifcfg-nbecker (which I guess was for my home wireless) was not created successfully. Should I just delete it?
On 06/17/2011 12:47 PM, Neal Becker wrote:
Neal Becker wrote:
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
I see I now have:
/etc/sysconfig/network-scripts: total used in directory 236 available 42595680 -rw-r--r--. 1 root root 0 Jun 17 09:52 ifcfg-nbecker -rw-r--r--. 1 root root 258 Jun 17 09:52 ifcfg-W34O4 -rw-r--r--. 1 root root 180 Jun 17 09:50 ifcfg-eth0 1 -rw-r--r--. 1 root root 73 May 13 09:36 ifcfg-eth0
The 1st 3 were created by the kde-plasma-networkmanagement update.
- Should I have two different ifcfg-eth0, ifcfg-eth0\ 1? Should I delete one
of them?
I deleted the \1 that one of my connections had.
- As you can see, ifcfg-nbecker (which I guess was for my home wireless) was
not created successfully. Should I just delete it?
I would. I believe it will just get recreated.
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
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
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.
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Patrick Boutilier wrote:
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.
Both times I first tried system NetworkManager restart, but it just hung until I hit the power switch (OK, I didn't wait too long, but I was afraid of some log files filling up)
On 06/17/2011 02:28 PM, Neal Becker wrote:
Patrick Boutilier wrote:
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.
Both times I first tried system NetworkManager restart, but it just hung until I hit the power switch (OK, I didn't wait too long, but I was afraid of some log files filling up)
Yeah, it took quite a while (at least a minute) to restart when I was having the problems.
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
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
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.
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.
kde mailing list kde@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
On 06/18/2011 10:52 AM, Kevin Kofler wrote:
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.
https://bugs.kde.org/show_bug.cgi?id=276004
Kevin Kofler
kde mailing list kde@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.
On 06/18/2011 05:27 PM, Lukas Middendorf wrote:
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.
Tested with nm-applet and it saved the password fine, into /etc/sysconfig/network-scripts/keys-WWOOD3 . So now kde-plasma-networkmanagement looks there for the password so it no longer asks for the key.
This brings me to another issue. I notice that it doesn't matter if the NetworkManager User Settings Service is running not for kde-plasma-networkmanagement to work. And nm-applet also works with it running where before it would complain that another program was already using NetworManager, Is this expected in 4.6.4 ?
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Patrick Boutilier wrote:
This brings me to another issue. I notice that it doesn't matter if the NetworkManager User Settings Service is running not for kde-plasma-networkmanagement to work. And nm-applet also works with it running where before it would complain that another program was already using NetworManager, Is this expected in 4.6.4 ?
That's expected with the new nm09 branch kde-plasma-networkmanagement which uses the native NetworkManager 0.9 API. It is a feature of NetworkManager 0.9 that multiple applets can coexist and that all settings are stored systemwide (with appropriate permissions/visibility, and with secrets stored separately in secure per-user storage (e.g. KWallet) when desired).
Kevin Kofler
Patrick Boutilier wrote:
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
This is a NetworkManager bug. It should be fixed by this update: https://admin.fedoraproject.org/updates/NetworkManager-0.8.9997-4.git2011062... which is currently in updates-testing and queued for stable.
Please test whether that update fixes your problems with the new kde-plasma-networkmanagement.
Kevin Kofler
On 06/23/2011 06:43 AM, Kevin Kofler wrote:
Patrick Boutilier wrote:
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
This is a NetworkManager bug. It should be fixed by this update: https://admin.fedoraproject.org/updates/NetworkManager-0.8.9997-4.git2011062... which is currently in updates-testing and queued for stable.
Please test whether that update fixes your problems with the new kde-plasma-networkmanagement.
The above problem is fixed.
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?
Kevin Kofler
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Patrick Boutilier wrote:
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?
I guess I must have gotten NetworkManager from updates-testing. I have had no problems.
Yes, the password seems to go somewhere, but I don't know where. It is not in the key file that was mentioned earlier, and, if it is going into kwallet, then the system must be opening my kwallet all by iteself while login is occurring, since I don't have to give any password to unlock it. Wireless is magically connected as soon as the desktop appears... mercifully, without any input from me.
On 06/24/2011 12:35 AM, Petrus de Calguarium wrote:
Patrick Boutilier wrote:
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?
I guess I must have gotten NetworkManager from updates-testing. I have had no problems.
Yes, the password seems to go somewhere, but I don't know where. It is not in the key file that was mentioned earlier, and, if it is going into kwallet, then the system must be opening my kwallet all by iteself while login is occurring, since I don't have to give any password to unlock it. Wireless is magically connected as soon as the desktop appears... mercifully, without any input from me.
As of yesterday the password saved (no idea why) and wireless connection is now stable.
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?
Jun 23 16:09:28 hplaptop NetworkManager[781]: <info> Starting VPN service 'openvpn'... Jun 23 16:09:28 hplaptop NetworkManager[781]: <info> VPN service 'openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 2770 Jun 23 16:09:28 hplaptop NetworkManager[781]: <info> VPN service 'openvpn' appeared; activating connections Jun 23 16:09:28 hplaptop NetworkManager[781]: <info> VPN plugin state changed: 1 Jun 23 16:09:28 hplaptop NetworkManager[781]: <info> VPN plugin state changed: 3 Jun 23 16:09:28 hplaptop NetworkManager[781]: <info> VPN connection 'BARTL-TLS' (Connect) reply received. Jun 23 16:09:28 hplaptop NetworkManager[781]: <warn> VPN connection 'BARTL-TLS' failed to connect: 'property 'user-name' invalid or not supported'. Jun 23 16:09:34 hplaptop NetworkManager[781]: <info> VPN service 'openvpn' disappeared
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Patrick Boutilier wrote:
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?
Please file this bug to: https://bugs.kde.org/
Any issues with kde-plasma-networkmanagement-0.9-0.53.20110616git.nm09.fc15 should be reported upstream as well, upstream needs to know about the problems.
Kevin Kofler
Petrus de Calguarium wrote:
Yes, the password seems to go somewhere, but I don't know where. It is not in the key file that was mentioned earlier, and, if it is going into kwallet, then the system must be opening my kwallet all by iteself while login is occurring, since I don't have to give any password to unlock it. Wireless is magically connected as soon as the desktop appears... mercifully, without any input from me.
I've also had trouble with secrets with the new build. :-(
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.)
These bugs need manual workarounding in config files, or deleting and recreating connections, both of which sucks as a user experience.
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.
Kevin Kofler
I wrote:
Handling of WPA-EAP secrets looks badly broken:
- 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.)
- 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.)
These are now: https://bugs.kde.org/show_bug.cgi?id=276485
- 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.)
And this is now: https://bugs.kde.org/show_bug.cgi?id=276486
Kevin Kofler
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.
Petrus de Calguarium wrote:
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.
So I guess I replied to the wrong message in the thread. :-)
FWIW, I'm seeing the trouble with WPA-EAP (WPA Enterprise) secrets only, my WPA-PSK connections got migrated correctly.
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?
GNOME uses gnome-keyring. Normally, it shouldn't get the secrets from gnome- keyring… Are you sure they aren't in the wallet. They're normally under a dedicated "Network Management" category.
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.
What previous build are you referring to? An older nm09 build? What I was referring to with "the previously working build" is the kde-plasma-networkmanagement-0.9-0.47.20110323.fc15.1 build, which doesn't work anymore with the current NetworkManager. :-( It worked fine before that update. ("previously working" != "previous, working". Language is subtle.)
Kevin Kofler
Kevin Kofler wrote:
FWIW, I'm seeing the trouble with WPA-EAP (WPA Enterprise) secrets only, my WPA-PSK connections got migrated correctly.
Sorry for the misunderstanding. I should have clued in when you used the word 'secrets', instead of passphrase or password. Yes, I am using WPA-PSK.
Are you sure they aren't in the wallet. They're normally under a dedicated "Network Management" category.
Ah ha! I see it. So, I guess kdm opens my kwallet and gets the network password, too, since I have it set to log me in automatically. The wireless network is up even before the desktop fully appears.
What previous build are you referring to? An older nm09 build?
Yes, the previous nm09 build from kde-redhat. I believe only 2 were released on kde-redhat. The one prior to the current was no good.
On 06/26/2011 02:49 AM, Kevin Kofler wrote:
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
After this update - all my passwords are lost.
I have
Store Connection Secrets: In File (unencrypted).
Now if I try edit to fix the missing passwords - then I get a pop up error
No agents are available for this request
clicking this away lets me edit the passwords back in - but will they be stored properly now?
I cannot go back to previous version because it totally crashes the desktop with the new NetworkManager.
thank you!
gene
Genes MailLists wrote:
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 ?
N supports both the a band and the b/g band, doesn't it? Printing the bands as frequencies won't necessarily be more helpful to the beginner.
Kevin Kofler
On 06/28/2011 07:25 PM, Kevin Kofler wrote:
Genes MailLists wrote:
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 ?
N supports both the a band and the b/g band, doesn't it? Printing the bands as frequencies won't necessarily be more helpful to the beginner.
Kevin Kofler
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 - if you go to configure an N/b/g Access Point - one chooses bands as either Narrow (20 Mhz for b/g) or wide (40) for N only. So the choices seem odd to me - perhaps experts can opine ...
It would be helpful if you could explain exactly what this choice does to NM - what effect does it have on the connection?
Genes MailLists wrote:
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
That doesn't change the frequency ranges in which the access points operate. It just means they can claim more than one channel. The channels are subsets of the overall range.
The b/g range is around 2.4 GHz, the a range is around 5.2 GHz. N supports both.
It would be helpful if you could explain exactly what this choice does to NM - what effect does it have on the connection?
The band + the channel number = the effective frequency.
Kevin Kofler
Genes MailLists wrote:
After this update - all my passwords are lost.
I wonder if that's the same bug as: https://bugs.kde.org/show_bug.cgi?id=276485 or a different one. Maybe file a new upstream bug at bugs.kde.org?
I cannot go back to previous version because it totally crashes the desktop with the new NetworkManager.
Downgrading wouldn't have restored your connections anyway, the migration process deletes the connections in the old format.
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
On 06/28/2011 07:31 PM, Kevin Kofler wrote:
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
Yeh i was hit by the mismatch and this was a fix - unfortunate for sure - but re-entering passwords is less painful than losing the plasma-desktop.
On 06/17/2011 12:41 PM, Neal Becker wrote:
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
I got those after upgrading as well (kde-plasma-networkmanagement-0.9-0.52.20110608git.nm09.fc15.x86_64). Went away after reboot.
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Rex Dieter wrote:
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 this also means is that we get or will get new features from kde- plasma-networkmanagement upstream, including, but not limited to: system connections (definitely supported now), Bluetooth tethering, IPv6 support (not sure of the status of those, but they're being worked on) etc.
Kevin Kofler
On Friday 17 June 2011 08:20:45 Rex Dieter wrote:
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.
Failed to connect using mobile broadband connection here. Downgrading again (it is my main connection method). Thank God for wvdial :)
-
Genes MailLists -
Gombang Nan Cengka -
Kevin Kofler -
Lukas Middendorf -
Neal Becker -
Patrick Boutilier -
Peter G. -
Rex Dieter