Bug 280753

Version:           0.9 (using KDE 4.6.0) 
OS:                Linux

The system crashed (this happens on average every 3 days now), and upon
restarting (after reboot) a long-established connection, with was used many times,
and stored as a named connection, had apparently lost its password, that is,
the blanck box opened with the password to enter.

Reproducible: Didn't try

Steps to Reproduce:
I tried for a long time to establish where the crashes come from, but to
no avail at all. So no chance to reproduce it.
With previous crashes no information was lost.

Actual Results:  
It is strange that one is forced to enter here something.

Expected Results:  
KWallet asks to enter the password (this can't be done when launching KDE,
since KDE doesn't recognise the keyboard at that time), after that the
wireless connection is established, without asking for the wpa(2)-password.

By the way, when I now go into the KNetworkManager to inspect the information,
again and again KWallet asks for the password. Perhaps then actually the
KWallet-ask-box disappears, but that is not so easy to tell, since KWallet
always opens on some other virtual desktop, you never know which, and one has
to run through all of them to find it. Sometimes these windows hide behind
other windows.

OS: Linux (x86_64) release 2.6.39.3-0.5-desktop
Compiler: gcc

Since one year I try to use KDE4, first under Suse 11.3, then under Suse 11.4
It is a permanent minefield. And I can't see any attempts to solve any of
the problems I encounter (and some of them I report here, but apparently without
any effect). Before that I used, on my old laptop, for >5 years Suse 9.2 with
the KDE which came with it, and I was very happy with it. Just a few days ago
I deleted the harddisk from the now nearly completely broken old laptop, started
a last time KDE3, and marvelled a last time how it all worked. I fear KDE
will never again get back to this state, since instead of fixing bugs, and
concentrating on the desktop, new stuff is added, which will just make things
worse.

The most obvious thing KDE should do is to ACKNOWLEDGE its broken state, and
care for that. That is, one needs the possibility to store and inspect all
the configuration (whatevery it is, just everything) explicitly, as part of
the KDE service. Not somewhere hidden in some hidden folders, but under full
control, based on standard Linux/Unix tools. Not saving state when the desktop
feels to do it, but also when the user says so. The Linux filesystem is reliable, but not KDE. For example the badly designed KNetwork-connections
management: very easily something is deleted, and that could be a very SERIOUS
problem for some who at a very special moment in time absolutely rely on the
service being available. So every connection should be stored in its own file,
clearly specified where this file is, and I could then just make the file
non-writeable to disable by accident change or removal.