Bug 693348

Summary: the network list is going out of a small screen - cant access to all wifi AP
Product: [Fedora] Fedora Reporter: Kevin Raymond <kraymond>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dcbw, fmuellner, maxamillion, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-05 14:35:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
print screen none

Description Kevin Raymond 2011-04-04 11:48:14 UTC
Created attachment 489743 [details]
print screen

Description of problem:
if there are too many networks around, on a small screen (10 inches for me) the network list is higher than the screen. Then we can't connect to the last one, which is hidden.
This appears only we we ask to show all networks using the "more" option.

Version-Release number of selected component (if applicable):
NetworkManager-gnome-0.8.997-8.git20110331.fc15.i686

How reproducible:
always with more that 13 wifi access points around.

Steps to Reproduce:
1. On the NM icon at the upper right, left-click to show networks
2. click on "more" to see all wifi around (once WIFI is on)
3. Use the bottom arrow to verify that there are networks name hidden out of the screen
  
Actual results:
see screenshot added

Expected results:
Dunno, adding a scroll bar

Additional info:

Comment 1 Florian Müllner 2011-04-05 14:35:10 UTC
The upstream fix in https://bugzilla.gnome.org/show_bug.cgi?id=646001 should be available with the next update. Please follow bug 693588 to track integration/testing in Fedora.

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