Comment # 5 on bug 953921 from Adi Meyerhofer

As I see it the trouble is not so much the network drop, but the inability to
re-connect unless rebooting. 

As mentioned in March I initially suspected a hardware incompatability with the
FritzBox 7490 as the problem occured in the following (all machines quite
recent and set up in Feb./Mch. 2015) 

Setups:
a) is a Laptop with openSuse 13.2 KDE 4.8.3 
b) is a desktop with th same suse/KDE combination connected
-- at different locations -- are connected to different boxes FritzBox 7490.
The "automatically disconnect after inactivity" option of that router is off
for "a" not known for "b". Even more erratic is the use of "a" behind a
Squid-proxy in an environment with seven WLAN networks using a single
accesspoint. testing with collectNWData.sh yielded no useful information.

In most cases -- when a PW is asked for -- no matter how many times one
attempts to enter the passwort (usually WPA-2) no reconnection is possible
until reboot. Attempting to change the settings in the KDE-network manager
(GUI) has no effect. Passwords are NEVER stored.

One can therefore exclude any hardware/firmware problems causing. The following
description was created whilst being connected to a "TP Link" router (unknown
model details).

Trying to change the settings in NetworkManager (saving the PW) caused a crash.

An hour later after rebotung the network connection was lost again:

journalctl -b
<code>
Nov 10 18:04:32 linux-XXXX.site org.a11y.Bus[2072]: Activating service
name='org.a11y.atspi.Registry'
Nov 10 18:04:32 linux-XXXX.site org.a11y.Bus[2072]: Successfully activated
service 'org.a11y.atspi.Registry'
Nov 10 18:04:32 linux-XXXX.site org.a11y.atspi.Registry[3012]: SpiRegistry
daemon is running with well-known name - org.a11y.atspi.Registry
Nov 10 18:04:32 linux-XXXX.site org.a11y.atspi.Registry[3012]: Xlib:  extension
"XEVIE" missing on display ":0".
</code>

dsmeg (after an instance where re-connecting worked WITHOUT entering a PW)