ok... few seconds after found a workaround and then the actual reason
--- my AP although was 'trusted' by the running knetworkmanager (at
least according to GUI settings), but never made into its
configuration file /home/yoh/.kde/share/config/knetworkmanagerrc
since I never exit knetworkmanager after being connected to that AP.
Somehow, whatever listed in GUI is not sufficient to actually be trusted
after resume -- KNM didn't try to connect to my ESCAPE.
Ok -- I've connected manually, quit KNM explicitly, mentioned that
ESCAPE appeared in the configuration file, restarted knetworkmanager,
suspend/resume and now everything works smooth.
So, imho, it boils down to absent storing of config upon adding a new
trusted network + somewhat incoherent use of the list of trusted network
-- whatever is displayed in GUI might not actually considered trusted
(if it was not in the configuration file)
NB I am using kwallet to store keys ;)
--
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student Ph.D. @ CS Dept. NJIT
Office: (973) 353-1412 | FWD: 82823 | Fax: (973) 353-1171
101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW: http://www.linkedin.com/in/yarik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
