[opensuse] Kde network manager plasmoid pain still hurts
Hi, I installed opensuse 12.1 on my Toshiba U505-S2950 yesterday with the default KDE 4.7.2 in use. I used it yesterday and today and have been thinking it is a great new version, EXCEPT for the kde NetworkManager-plasmoid when I try to connect to wlan. I looked through the mailing list archive, and found one thread called "kde network manager plasmoid pain" that parallels my issues. I have to put in the root password sometimes, and the wpa password always after booting. Besides that, it doesn't always see my wireless network when I am in the other room, but it always sees my neighbor's network somewhere in another county. I can't always connect when it does finally agree that my network really only lives one room away. I see that Will Stephenson wrote an answer that effectively answered the archived thread, and I paraphrase when I say it read "the check is in the mail, and fixes just came out." In my case I am all updated, but the fixes haven't worked. So I gave up on NetworkManager and went to ifup. But I am writing to see if someone could respond with current good news on fixes for networkmanager, or instructions on how to get it working right. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, December 07, 2011 06:10:49 PM Mark Misulich wrote:
Hi, I installed opensuse 12.1 on my Toshiba U505-S2950 yesterday with the default KDE 4.7.2 in use. I used it yesterday and today and have been thinking it is a great new version, EXCEPT for the kde NetworkManager-plasmoid when I try to connect to wlan.
I looked through the mailing list archive, and found one thread called "kde network manager plasmoid pain" that parallels my issues. I have to put in the root password sometimes, and the wpa password always after booting. Besides that, it doesn't always see my wireless network when I am in the other room, but it always sees my neighbor's network somewhere in another county. I can't always connect when it does finally agree that my network really only lives one room away.
I see that Will Stephenson wrote an answer that effectively answered the archived thread, and I paraphrase when I say it read "the check is in the mail, and fixes just came out."
In my case I am all updated, but the fixes haven't worked. So I gave up on NetworkManager and went to ifup. But I am writing to see if someone could respond with current good news on fixes for networkmanager, or instructions on how to get it working right.
Mark I had thought it was fixed. You may need to file a new bug report. -- Roger Luedecke openSUSE Ambassador Ind. Repairs and Consulting **Looking for a C++ etc. mentor*** -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/12/11 06:04, Roger Luedecke wrote:
On Wednesday, December 07, 2011 06:10:49 PM Mark Misulich wrote:
Hi, I installed opensuse 12.1 on my Toshiba U505-S2950 yesterday with the default KDE 4.7.2 in use. I used it yesterday and today and have been thinking it is a great new version, EXCEPT for the kde NetworkManager-plasmoid when I try to connect to wlan.
I looked through the mailing list archive, and found one thread called "kde network manager plasmoid pain"
I started that thread. that parallels my issues. I have to
put in the root password sometimes, and the wpa password always after booting. Besides that, it doesn't always see my wireless network when I am in the other room, but it always sees my neighbor's network somewhere in another county. I can't always connect when it does finally agree that my network really only lives one room away.
I see that Will Stephenson wrote an answer that effectively answered the archived thread, and I paraphrase when I say it read "the check is in the mail, and fixes just came out."
In my case I am all updated, but the fixes haven't worked. So I gave up on NetworkManager and went to ifup. But I am writing to see if someone could respond with current good news on fixes for networkmanager, or instructions on how to get it working right.
Mark I had thought it was fixed. You may need to file a new bug report.
The bug you describe is at: https://bugzilla.novell.com/show_bug.cgi?id=716291 Its says resolved but I don't think it is. I have it working but only by applying the stuff at comment 22 in the bug report. HTH L x. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Dec 08, 2011 at 08:56:36AM +0100, lynn wrote:
On 08/12/11 06:04, Roger Luedecke wrote:
On Wednesday, December 07, 2011 06:10:49 PM Mark Misulich wrote: [ 8< ]
I see that Will Stephenson wrote an answer that effectively answered the archived thread, and I paraphrase when I say it read "the check is in the mail, and fixes just came out."
In my case I am all updated, but the fixes haven't worked. So I gave up on NetworkManager and went to ifup. But I am writing to see if someone could respond with current good news on fixes for networkmanager, or instructions on how to get it working right.
I had thought it was fixed. You may need to file a new bug report.
The bug you describe is at:
https://bugzilla.novell.com/show_bug.cgi?id=716291
Its says resolved but I don't think it is.
Either reopen it if it's the same defect or file a fresh one referencing bnc#716291, please. Thanks. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Wed, 2011-12-07 at 18:10 -0500, Mark Misulich wrote:
Hi, I installed opensuse 12.1 on my Toshiba U505-S2950 yesterday with the default KDE 4.7.2 in use. I used it yesterday and today and have been thinking it is a great new version, EXCEPT for the kde NetworkManager-plasmoid when I try to connect to wlan.
I looked through the mailing list archive, and found one thread called "kde network manager plasmoid pain" that parallels my issues. I have to put in the root password sometimes, and the wpa password always after booting. Besides that, it doesn't always see my wireless network when I am in the other room, but it always sees my neighbor's network somewhere in another county. I can't always connect when it does finally agree that my network really only lives one room away.
Me too. I see so many other access points. But the one I am using (also in the next room) works for a bit, then just goes away. When that happens, it will not be in the list for a while. However, it seems that if I click on Manage connections and in the wireless part select it, a connection happens. Of course, it asks for the kwallet password again. I thought the idea with the kwallet was once I told a program about it, it can access the wallet as long as it runs. So I guess the program is dying and restarting. Which is why the connection goes away.
I see that Will Stephenson wrote an answer that effectively answered the archived thread, and I paraphrase when I say it read "the check is in the mail, and fixes just came out."
I saw that too. My system is also up-to-date. But the problem remains. FTIW, this works on 11.4, which makes me think the local network setup is not the root cause.
In my case I am all updated, but the fixes haven't worked. So I gave up on NetworkManager and went to ifup. But I am writing to see if someone could respond with current good news on fixes for networkmanager, or instructions on how to get it working right.
Mark
Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Donnerstag, 8. Dezember 2011, 08:34:59 schrieb Roger Oberholtzer:
Me too. I see so many other access points. But the one I am using (also in the next room) works for a bit, then just goes away. When that happens, it will not be in the list for a while. However, it seems that if I click on Manage connections and in the wireless part select it, a connection happens.
You can check with nm-tool whether NetworkManager sees your connection. If nm- tool does not list it, there is nothing NetworkManager-clients, such as the KDE one, can do about it. If you check the logs /var/log/NetworkManager and maybe even /var/log/wpa_supplicant, you might get more hints, e.g. that your connection was marked as invalid. http://en.opensuse.org/SDB:Tracking_down_wireless_problems#NetworkManager
Of course, it asks for the kwallet password again. I thought the idea with the kwallet was once I told a program about it, it can access the wallet as long as it runs. So I guess the program is dying and restarting. Which is why the connection goes away.
It depends on whether you allow to access it "once" or "always". The wallet closes after some time and your password is not necessarily kept in memory if not needed. Further, since you might have changed something about the connection while you were connected it would make sense to re-read if you connect the next time. Unrelated to connection losses is the policyKit issue, i.e. that you are asked for root-password if you create a new connection. And yet another issue and really a bug is that sometimes you are asked for root-password (PolicyKit) if the connection was lost. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 08/12/2011 10:09, Sven Burmeister a écrit :
You can check with nm-tool whether NetworkManager sees your connection.
what I noticed (but some weeks ago) was than clicking on the link name make it desapear, when usually it did active it. So my main link desapear and I can have it again like described by others, without typing the SSID by hand jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2011-12-08 at 10:16 +0100, jdd wrote:
Le 08/12/2011 10:09, Sven Burmeister a écrit :
You can check with nm-tool whether NetworkManager sees your connection.
what I noticed (but some weeks ago) was than clicking on the link name make it desapear, when usually it did active it.
So my main link desapear and I can have it again like described by others, without typing the SSID by hand
I never saw it removed from the list of managed connections. It only goes away from the list of defected networks. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2011-12-08 at 10:09 +0100, Sven Burmeister wrote:
Am Donnerstag, 8. Dezember 2011, 08:34:59 schrieb Roger Oberholtzer:
Me too. I see so many other access points. But the one I am using (also in the next room) works for a bit, then just goes away. When that happens, it will not be in the list for a while. However, it seems that if I click on Manage connections and in the wireless part select it, a connection happens.
You can check with nm-tool whether NetworkManager sees your connection. If nm- tool does not list it, there is nothing NetworkManager-clients, such as the KDE one, can do about it.
If you check the logs /var/log/NetworkManager and maybe even /var/log/wpa_supplicant, you might get more hints, e.g. that your connection was marked as invalid.
http://en.opensuse.org/SDB:Tracking_down_wireless_problems#NetworkManager
Of course, it asks for the kwallet password again. I thought the idea with the kwallet was once I told a program about it, it can access the wallet as long as it runs. So I guess the program is dying and restarting. Which is why the connection goes away.
It depends on whether you allow to access it "once" or "always". The wallet closes after some time and your password is not necessarily kept in memory if not needed. Further, since you might have changed something about the connection while you were connected it would make sense to re-read if you connect the next time.
I have it set to 'always'. Always. Of course, 'always' never did survive logout. So perhaps 'always' is really 'this session'. Same for all users of kwallet. When I start evolution, it asks as well. Presumably because it uses a different wallet. But it only asks once per login. Even if I restart it.
Unrelated to connection losses is the policyKit issue, i.e. that you are asked for root-password if you create a new connection.
In my case, when it is reconnecting after a loss, I only get asked the kwallet password. Only if I make a change do I get the root password. Which I can only assume is a different issue. The whole point of the Network Manager, as opposed to ifup, I thought, was to let the setup be done by a non-root user.
And yet another issue and really a bug is that sometimes you are asked for root-password (PolicyKit) if the connection was lost.
Not sure I saw that. I really only remember the kwallet one at these times. But don't quote me on that... Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
jdd -
Lars Müller -
lynn -
Mark Misulich -
Roger Luedecke -
Roger Oberholtzer -
Sven Burmeister