kde4 wifi plasmoid(?) defective

[bad sector]

Using kde4 & Suse-12.1 the KDE wifi network management seems to be
defective. If I bail out of X the connection will not resume upon
relaunching it. At that point I have to either cycle the router and the
WAN connection or cycle (pull/reinsert) the usb transceiver.

[Hendrik van Hees]

Strange, this I never had. Which version of KDE and knetworkmanager are
you using?

--
Hendrik van Hees
Frankfurt Institute of Advanced Studies
D-60438 Frankfurt am Main
http://fias.uni-frankfurt.de/~hees/

[bad sector]

On 03/12/2012 08:35 AM, Hendrik van Hees wrote:
> On 09/03/12 00:27, bad sector wrote:
>>
>> Using kde4 & Suse-12.1 the KDE wifi network management seems to be
>> defective. If I bail out of X the connection will not resume upon
>> relaunching it. At that point I have to either cycle the router and the
>> WAN connection or cycle (pull/reinsert) the usb transceiver.
>>
>>
> Strange, this I never had. Which version of KDE and knetworkmanager are
> you using?
>

KDE 4.7.2 & 3.5.10

knetworkmanager 3.5.10

it's not doing it anymore

[Hendrik van Hees]

On 18/03/12 03:34, bad sector wrote:

> KDE 4.7.2 & 3.5.10
>
> knetworkmanager 3.5.10
>
> it's not doing it anymore

Under kde 4.7.2 (which is buggy wrt. the kmenueditor but that's not
related to networking) you should use the networkmanager plasmoid. With
this I never had problems.

[bad sector]

On 03/18/2012 01:05 PM, Hendrik van Hees wrote:
> On 18/03/12 03:34, bad sector wrote:
>
>> KDE 4.7.2 & 3.5.10
>>
>> knetworkmanager 3.5.10
>>
>> it's not doing it anymore
>
> Under kde 4.7.2 (which is buggy wrt. the kmenueditor but that's not
> related to networking) you should use the networkmanager plasmoid. With
> this I never had problems.

I spoke too soon, it's doing it again and I can't put a finger on it. I
had a suse-11.4 system up and connected without any intervention (using
nm-applet under ~/.kde4/autostart). Then I rebooted to suse-12.1 which
doesn't (I presume it's using the kde plasmoid if that's what the icon
in the system tray is). I had to remove/insert the usb dongle to get
going so I presume it's not initiating something correctly.

[bad sector]

On 03/18/2012 01:05 PM, Hendrik van Hees wrote:

> On 18/03/12 03:34, bad sector wrote:
>
>> KDE 4.7.2 & 3.5.10
>>
>> knetworkmanager 3.5.10
>>
>> it's not doing it anymore
>
> Under kde 4.7.2 (which is buggy wrt. the kmenueditor but that's not
> related to networking) you should use the networkmanager plasmoid. With
> this I never had problems.

Thanks for the hint.

Additional typical symptom was that for unknown reasons the router would
simply drop wifi capability forcing a reboot. I'm still with just
nm-applet but I had noticed that my old router had a stuck WPS button
(SMC WBGR14N design). I swappeed it out for a new Netgear and sofar the
problem has not recurred. Remains now to isolate if that's because of
nm-applet or because of the new router, however seeing that everything
is working I think I'll just leave it as is :-)

The only time I had used the WPS button was to set up my wifi printer
(cp1525nw) & I know too little about networking or routers to even guess
what the effect of a WPS button possibly stuck 'ON' would/could have
been or if ity was a factor at all.

[bad sector]

On 03/12/2012 04:35 AM, Hendrik van Hees wrote:
> On 09/03/12 00:27, bad sector wrote:
>>
>> Using kde4 & Suse-12.1 the KDE wifi network management seems to be
>> defective. If I bail out of X the connection will not resume upon
>> relaunching it. At that point I have to either cycle the router and the
>> WAN connection or cycle (pull/reinsert) the usb transceiver.
>>
>>
> Strange, this I never had. Which version of KDE and knetworkmanager are
> you using?
>

I've now had the kde4 networkmanager and plasmoid ON for several days
and the problem has not come back using the new routwer. So it was most
likely a router problem.