[opensuse-kde3] knetworkmanager
I have tried again the knetworkmanager (I was using the nm-applet for some time due to memory leakage of the knetworkmanager) and found that, beside the memory leakage, which is still present (the knetworkmanager allocates more and more memory every time it connects to a network and releases it very seldom), there are some more diseases. First, it does not change the system dock icon when the network cable is unplugged. It only do it when the computer has been hibernated/resumed or after it has found a new network and tries to connect. Second, no notifications (either visual or sound) appear, as if it would not communicate events to the knotify. Michael -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Wednesday 23 May 2012 04:28:37 am Michael Lashkevich wrote:
I have tried again the knetworkmanager (I was using the nm-applet for some time due to memory leakage of the knetworkmanager) and found that, beside the memory leakage, which is still present (the knetworkmanager allocates more and more memory every time it connects to a network and releases it very seldom), there are some more diseases.
First, it does not change the system dock icon when the network cable is unplugged. It only do it when the computer has been hibernated/resumed or after it has found a new network and tries to connect.
Second, no notifications (either visual or sound) appear, as if it would not communicate events to the knotify.
Michael
install wicd, change the network control to ifup and forget that knetworkmanager ever existed. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 05/23/2012 12:28 PM, mechanical wrote:
install wicd, change the network control to ifup and forget that knetworkmanager ever existed.
Brilliant suggestion. I did it and only have one niggling problem. Everytime I reboot, wicd and the network fires up, then it dies until I do ifup wlan0, sometimes followed by dhcpcd wlan0. My message log shows: Jun 5 15:58:44 Diggerodell ifup-dhcp: . Jun 5 15:58:50 ifup-dhcp: last message repeated 2 times Jun 5 15:58:50 Diggerodell dhcpcd[9141]: wlan0: offered 192.168.1.3 from 192.168.1.1 Jun 5 15:58:50 Diggerodell dhcpcd[9141]: wlan0: checking 192.168.1.3 is available on attached networks Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: leased 192.168.1.3 for 86400 seconds Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: no renewal time supplied, assuming 43200 seconds Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: no rebind time supplied, assuming 75600 seconds Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: adding IP address 192.168.1.3/24 Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: adding default route via 192.168.1.1 metric 0 Jun 5 15:58:51 Diggerodell ifdown: wlan0 Jun 5 15:58:51 Diggerodell ifup-dhcp: . Jun 5 15:58:51 Diggerodell ifup: wlan0 Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: exiting Jun 5 15:58:52 Diggerodell ifup-dhcp: Jun 5 15:58:52 Diggerodell ifup-dhcp: wlan0 IP address: 192.168.1.3/24 At 15:58:51 after getting an IP, it does the ifdown!! I do the ifup wlan0 and I'm back in business. Can anyone tell me what I'm doing wrong or why the ifdown gets added in there and how do I make sure the ifup wlan0 gets done and stays done at the next boot? I'm running 11.4 with kde3. Thanks to those who made kde useful again. Sure is nice to just use the thing without having to look for how to do stuff that used to work. Regards. Richard -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Tuesday 05 June 2012 11:19:44 am Richard wrote:
On 05/23/2012 12:28 PM, mechanical wrote:
install wicd, change the network control to ifup and forget that knetworkmanager ever existed.
Brilliant suggestion. I did it and only have one niggling problem. Everytime I reboot, wicd and the network fires up, then it dies until I do ifup wlan0, sometimes followed by dhcpcd wlan0. My message log shows:
Jun 5 15:58:44 Diggerodell ifup-dhcp: . Jun 5 15:58:50 ifup-dhcp: last message repeated 2 times Jun 5 15:58:50 Diggerodell dhcpcd[9141]: wlan0: offered 192.168.1.3 from 192.168.1.1 Jun 5 15:58:50 Diggerodell dhcpcd[9141]: wlan0: checking 192.168.1.3 is available on attached networks Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: leased 192.168.1.3 for 86400 seconds Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: no renewal time supplied, assuming 43200 seconds Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: no rebind time supplied, assuming 75600 seconds Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: adding IP address 192.168.1.3/24 Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: adding default route via 192.168.1.1 metric 0 Jun 5 15:58:51 Diggerodell ifdown: wlan0 Jun 5 15:58:51 Diggerodell ifup-dhcp: . Jun 5 15:58:51 Diggerodell ifup: wlan0 Jun 5 15:58:51 Diggerodell dhcpcd[9141]: wlan0: exiting Jun 5 15:58:52 Diggerodell ifup-dhcp: Jun 5 15:58:52 Diggerodell ifup-dhcp: wlan0 IP address: 192.168.1.3/24
At 15:58:51 after getting an IP, it does the ifdown!! I do the ifup wlan0 and I'm back in business.
Can anyone tell me what I'm doing wrong or why the ifdown gets added in there and how do I make sure the ifup wlan0 gets done and stays done at the next boot?
I'm running 11.4 with kde3. Thanks to those who made kde useful again. Sure is nice to just use the thing without having to look for how to do stuff that used to work.
Regards. Richard
first make sure that wicd starts in system services. hit the advanced button and make wicd start at runlevels 3 && 5. then make sure that you have your favorite connection set up to automatically connect . a problem you might have could be with a permissions snafu, if you are not root you can not see the full tab with the available connections when you click on the wicd icon. so either try it as root, or, fire up conqueror as a superuser and start turning permissinons in /etc/wicd to your regular user until you see the screen as a mortal. that was not necessary in 11.1, but it has become so afterwards. actually, to see what i mean, perhaps you should first try a graphic login as root , click on the wicd icon and enjoy the "bims" :) as well:) good luck, d. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 06/05/2012 07:01 PM, kanenas@hawaii.rr.com wrote:
first make sure that wicd starts in system services. hit the advanced button and make wicd start at runlevels 3&& 5. then make sure that you have your favorite connection set up to automatically connect . a problem you might have could be with a permissions snafu, if you are not root you can not see the full tab with the available connections when you click on the wicd icon. so either try it as root, or, fire up conqueror as a superuser and start turning permissinons in /etc/wicd to your regular user until you see the screen as a mortal. that was not necessary in 11.1, but it has become so afterwards. actually, to see what i mean, perhaps you should first try a graphic login as root , click on the wicd icon and enjoy the "bims":) as well:) good luck,
That was it!! Did the runlevel setup, then the permissions thing and voila, it works. Thank you , thank you, thank you. Richard -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
participants (4)
-
kanenas＠hawaii.rr.com -
mechanical -
Michael Lashkevich -
Richard