Bug 780110 - On boot, KDE Network Manager does not detect previously used networks but detects others
Summary: On boot, KDE Network Manager does not detect previously used networks but det...
Status: RESOLVED DUPLICATE of bug 768564
Alias: None
Product: openSUSE 12.2
Classification: openSUSE
Component: Network (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 12.2
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Bin Li
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-12 22:06 UTC by Foolish Ewe
Modified: 2012-10-06 13:43 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Foolish Ewe 2012-09-12 22:06:01 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0

I recently updated to OpenSuse 12.2 from Opensuse 12.1 Tumbleweed on my Toshiba P855-S5200 using zypper dup.  After the update and a reboot I was not able to see my own wireless network, but was able to see the wireless networks of my neighbors in the network manager, when I left click and observe the "connections window".  However, when my machine went to sleep (i.e. suspend to ram) and I woke it back up, it was able to see my network again.  I also noticed the behavior in my office.  I do use kwallet for key management.

Reproducible: Always

Steps to Reproduce:
1. Boot the machine near a network I have used before, and have configured to autoconnect with credentials in kwallet.
2. Await network manager to autoconnect to network.
3. Left click on kwallet icon, and scan for networks.
4. Put the machine to sleep and wake up
Actual Results:  
1. Boot the machine near a network I have used before, and have configured to autoconnect with credentials in kwallet.
2. Login and await network manager to autoconnect to network (with prompt for kwallet password), doesn't happen.
3. Left click on kwallet icon, and scan for networks, don't see my familiar networks (they are public, i.e. not hidden, and beacon their ssid), but DO SEE unfamiliar networks (unfamiliar in the sense that I've never logged into them, they belong to my neighbors).
4. Put the machine to sleep and wake up - see normal autoconnect.

Expected Results:  
1. boot machine near familiar network.
2. have autoconnect upon login.

I suspect this may be related to bug 768564, but it may also be a Network Manager/KDE issue, due to the fact that it looks like the familiar networks are being excluded from the list of visible networks.  Other laptops have no problem seeing these networks and upon wakeup from sleep, mine sees them too.
Comment 1 Foolish Ewe 2012-10-06 13:43:09 UTC
This was fixed in my most recent zypper up (it had been a week or so), during which I think I got fix for bug 768564.   I marked this as a dup.

*** This bug has been marked as a duplicate of bug 768564 ***