With the latest updates the problem of crashing when entering certain folders has gone. There are still gpg issues. More importantly, knetworkmanager is now broken. Since NetworkManager-gnome was problematic for me this is a catastrophe.
Anne
On Sunday 25 January 2009 06:34:39 Anne Wilson wrote:
With the latest updates the problem of crashing when entering certain folders has gone. There are still gpg issues. More importantly, knetworkmanager is now broken. Since NetworkManager-gnome was problematic for me this is a catastrophe.
Anne
What is broken in knetworkmanager for you, Anne? For me, it's working fine - I'm on it this moment - this is a laptop with Broadcom 4306 usiing WPAK and all the latest updates from testing and kderedhat-unstable - I connect to a Linksys WRT54G running OpenWRT (open source distro for Linksys routers) if that is relevant...
On Sunday 25 January 2009, Claude Jones wrote:
On Sunday 25 January 2009 06:34:39 Anne Wilson wrote:
With the latest updates the problem of crashing when entering certain folders has gone. There are still gpg issues. More importantly, knetworkmanager is now broken. Since NetworkManager-gnome was problematic for me this is a catastrophe.
Anne
What is broken in knetworkmanager for you, Anne? For me, it's working fine
- I'm on it this moment - this is a laptop with Broadcom 4306 usiing WPAK
and all the latest updates from testing and kderedhat-unstable - I connect to a Linksys WRT54G running OpenWRT (open source distro for Linksys routers) if that is relevant...
For the record, my issue with NetworkManager-gnome is it always asks for passwords. That's an annoyance to me (maybe a showstopper to newbs), but not a catastrophe.
On Sunday 25 January 2009 09:37:51 Neal Becker wrote:
On Sunday 25 January 2009, Claude Jones wrote:
On Sunday 25 January 2009 06:34:39 Anne Wilson wrote:
With the latest updates the problem of crashing when entering certain folders has gone. There are still gpg issues. More importantly, knetworkmanager is now broken. Since NetworkManager-gnome was problematic for me this is a catastrophe.
Anne
What is broken in knetworkmanager for you, Anne? For me, it's working fine - I'm on it this moment - this is a laptop with Broadcom 4306 usiing WPAK and all the latest updates from testing and kderedhat-unstable - I connect to a Linksys WRT54G running OpenWRT (open source distro for Linksys routers) if that is relevant...
For the record, my issue with NetworkManager-gnome is it always asks for passwords. That's an annoyance to me (maybe a showstopper to newbs), but not a catastrophe.
I just noticed a warning icon saying I needed to re-log in in my systray. I just did, so I'm now definitely up on all the latest versions of things. kNM came right up and auto-connected to my network with no intervention on my part.
On the password prompting, could it be a gnome-keyring-pam issue? If you don't know what this is, just google it - it allows you to set up auto-logging-in for things like NM
Anne Wilson wrote:
With the latest updates the problem of crashing when entering certain folders has gone. There are still gpg issues. More importantly, knetworkmanager is now broken. Since NetworkManager-gnome was problematic for me this is a catastrophe.
I don't really understand that, because knetworkmanager is KDE 3 code, it should not be affected by the KDE 4 changes at all.
How is it broken?
Kevin Kofler
On Sunday 25 January 2009 16:23:08 Kevin Kofler wrote:
Anne Wilson wrote:
With the latest updates the problem of crashing when entering certain folders has gone. There are still gpg issues. More importantly, knetworkmanager is now broken. Since NetworkManager-gnome was problematic for me this is a catastrophe.
I don't really understand that, because knetworkmanager is KDE 3 code, it should not be affected by the KDE 4 changes at all.
How is it broken?
Kevin & Claude - I can't find what's wrong. It worked perfectly before the update. Now the cog spins and the tiny progress bar sits at halfway, then it disappears. I tried deleting the connection and creating a new one. It immediately offered me my network, accepted my key, but then the same thing happened when I tried to connect.
Kevin - could wpa be affected?
Anne
On Sunday 25 January 2009 12:41:50 Anne Wilson wrote:
Kevin & Claude - I can't find what's wrong. It worked perfectly before the update. Now the cog spins and the tiny progress bar sits at halfway, then it disappears. I tried deleting the connection and creating a new one. It immediately offered me my network, accepted my key, but then the same thing happened when I tried to connect.
Kevin - could wpa be affected?
I'm not Kevin, and I'm not offering a "mine works so what's wrong with you?" comment - just noting that for me it is working. Here's my info:
rpm -qa | grep network ..........snip irrelevant....... kdenetwork-4.2.0-1.fc10.i386 kdenetwork-libs-4.2.0-1.fc10.i386 [cj@cjasus ~]$ rpm -qa | grep wpa wpa_supplicant-0.6.4-2.fc10.i386
I mentioned earlier I had a Broadcom 4306, but that's wrong -that's on my other laptop: on this machine the chip is: 03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
Hope this helps. Did you do a full reboot? I'm finding as time goes on, that the old "you never have to reboot linux" maxim is fading; of course you had to for new kernels, but, there seem to be more and more issues that can be quickly cured by reboots - there's probably workarounds and commands that can substitute for most, but, sometimes, it's just dirty and quicker.
I guess you're down to sleuthing if all else fails - maybe 'network' got turned on? You're sure the network is up? Reboot the router? The usual suspects...
On Sunday 25 January 2009 18:14:51 Claude Jones wrote:
On Sunday 25 January 2009 12:41:50 Anne Wilson wrote:
Kevin & Claude - I can't find what's wrong. It worked perfectly before the update. Now the cog spins and the tiny progress bar sits at halfway, then it disappears. I tried deleting the connection and creating a new one. It immediately offered me my network, accepted my key, but then the same thing happened when I tried to connect.
Kevin - could wpa be affected?
I'm not Kevin, and I'm not offering a "mine works so what's wrong with you?" comment - just noting that for me it is working. Here's my info:
rpm -qa | grep network ..........snip irrelevant....... kdenetwork-4.2.0-1.fc10.i386 kdenetwork-libs-4.2.0-1.fc10.i386 [cj@cjasus ~]$ rpm -qa | grep wpa wpa_supplicant-0.6.4-2.fc10.i386
I'm using the same versions.
I mentioned earlier I had a Broadcom 4306, but that's wrong -that's on my other laptop: on this machine the chip is: 03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
Hope this helps. Did you do a full reboot? I'm finding as time goes on, that the old "you never have to reboot linux" maxim is fading; of course you had to for new kernels, but, there seem to be more and more issues that can be quickly cured by reboots - there's probably workarounds and commands that can substitute for most, but, sometimes, it's just dirty and quicker.
I guess you're down to sleuthing if all else fails - maybe 'network' got turned on? You're sure the network is up? Reboot the router? The usual suspects...
I didn't do a complete reboot - I tend to only do that for kernels - but I have now. Now, when I click on the network icon, my network is not listed. If I click on the icon and select Connect to Other Network it offers me my own network, but follows it up with a message "KNetworkManager Wireless Network Disappeared". 'iwlist wlan0 scanning' tells me that there are no scan results.
I know the router is behaving itself, as this laptop is using the same wireless connection. Basically, knetworkmanager seems to now be behaving the same way as NetworkManager-gnome :-(
Anne
On Sunday 25 January 2009 18:29:26 Kevin Kofler wrote:
Anne Wilson wrote:
Kevin & Claude - I can't find what's wrong. It worked perfectly before the update.
Did you upgrade something other than KDE too? Kernel maybe?
Checked the logs - the kernel update was yesterday. It was still working after that.
wpa_supplicant.log is full of
Failed to initiate AP scan. CTRL-EVENT-SCAN-RESULTS
Nothing else at all.
Anne
On Sun, Jan 25, 2009 at 7:46 PM, Anne Wilson cannewilson@googlemail.com wrote:
Checked the logs - the kernel update was yesterday. It was still working after that.
wpa_supplicant.log is full of
Failed to initiate AP scan. CTRL-EVENT-SCAN-RESULTS
This and the other symptoms you mentioned in the other message make me think that this is an issue with the wireless drivers rather than which version of NetworkManager is running -- if "iwlist wlan0 scan" returns nothing, there's nothing any other component can do. If my netbook gets into this mood (haven't seen it for a while because I'm not using wireless in my current flat) I think I generally had to reboot.
MEF
On Sunday 25 January 2009 18:52:59 Mary Ellen Foster wrote:
On Sun, Jan 25, 2009 at 7:46 PM, Anne Wilson cannewilson@googlemail.com
wrote:
Checked the logs - the kernel update was yesterday. It was still working after that.
wpa_supplicant.log is full of
Failed to initiate AP scan. CTRL-EVENT-SCAN-RESULTS
This and the other symptoms you mentioned in the other message make me think that this is an issue with the wireless drivers rather than which version of NetworkManager is running -- if "iwlist wlan0 scan" returns nothing, there's nothing any other component can do. If my netbook gets into this mood (haven't seen it for a while because I'm not using wireless in my current flat) I think I generally had to reboot.
This is following a reboot :-( I can't believe that it's a driver issue, when it was working so well before this update. The driver is kernel-provided, and that hasn't been touched. It's not making any sense to me at the moment.
Anne
On Sunday 25 January 2009 13:58:13 Anne Wilson wrote:
This is following a reboot :-( I can't believe that it's a driver issue, when it was working so well before this update. The driver is kernel-provided, and that hasn't been touched. It's not making any sense to me at the moment.
You're not alone - something strange there - I'm thinking about it, but no further ideas are coming. Are you sure your radio is on? It should be turned on automatically when you reboot, even if you've managed to turn it off, but, you never know...are we talking about your ASUS?
On Sunday 25 January 2009 22:37:14 Claude Jones wrote:
On Sunday 25 January 2009 13:58:13 Anne Wilson wrote:
This is following a reboot :-( I can't believe that it's a driver issue, when it was working so well before this update. The driver is kernel-provided, and that hasn't been touched. It's not making any sense to me at the moment.
You're not alone - something strange there - I'm thinking about it, but no further ideas are coming. Are you sure your radio is on? It should be turned on automatically when you reboot, even if you've managed to turn it off, but, you never know...are we talking about your ASUS?
The Acer Aspire One, yes. I'm connected this morning. This reminds me of the problem I had with NetworkManager-gnome - when it lost connection it could not re-connect. In fact it couldn't see the network at all. Just the same as I saw last night. I'll see what happens today.
Anne
On Monday 26 January 2009, Anne Wilson wrote:
On Sunday 25 January 2009 22:37:14 Claude Jones wrote:
On Sunday 25 January 2009 13:58:13 Anne Wilson wrote:
This is following a reboot :-( I can't believe that it's a driver issue, when it was working so well before this update. The driver is kernel-provided, and that hasn't been touched. It's not making any sense to me at the moment.
You're not alone - something strange there - I'm thinking about it, but no further ideas are coming. Are you sure your radio is on? It should be turned on automatically when you reboot, even if you've managed to turn it off, but, you never know...are we talking about your ASUS?
The Acer Aspire One, yes. I'm connected this morning. This reminds me of the problem I had with NetworkManager-gnome - when it lost connection it could not re-connect. In fact it couldn't see the network at all. Just the same as I saw last night. I'll see what happens today.
Anne
Have you rebooted since seeing non-functioning driver or reloaded the driver? At random (with low probability) I get this. I just reload the kernel driver and then it works. Also with some probability, sometimes I notice I accidentally switch the wireless off with the physical switch :) The latter seems to require restarting NM to notice the switch is turned on (it shouldn't, but it does).
On Mon January 26 2009 6:19:17 am Anne Wilson wrote:
The Acer Aspire One, yes. I'm connected this morning. This reminds me of the problem I had with NetworkManager-gnome - when it lost connection it could not re-connect. In fact it couldn't see the network at all. Just the same as I saw last night. I'll see what happens today.
I'm going to guess that some thing changed in your configuration at some point recently, and old info was in a cache somewhere in the network path. Did you ever reboot your router during this event? Either that, or some flakiness with your radio - I have an old HP with Broadcom 4306 wireless that gets real funny with the wireless configuration sometimes. It acts like you describe, suddenly, mysteriously, and then clears up - on occasion, I've found the radio to seemingly have a mind of its own - and the LED on the radio to be useless - it can appear to be off, and wireless works, and vice-versa; also, the lost-connection-can't- reconnect bit - usually, rebooting clears that one up, as well as the radio problem.