Hi Jerry.  Thanks for the bug reports.

You could be even more helpful if you would split your information up
into distinct issues.  For each issue, search the existing bug reports;
if you find that the issue has already been reported then add your
information there, otherwise open a new report for that issue.

> Wireless WPA fails to "automatically connect" even
> though "enable wireless" is on when rebooting.

Which hardware should be automatically configured and with what kind of
network should it be connected?

> Systems Settings Network is blank where it should
> have the network name. That's a bug.

That's gnome-control-center, not NM.

> Network Applet Edit Connections says wired connection
> last used 5 minutes ago. Has not been plugged in
> since yesterday. That's a bug.  Network Applet
> Edit Connections says wireless connection last used
> 2 hours ago. Not true, last used 5 minutes ago.
> That's a bug.

Hmm, does nm-connection-editor confuse the wired and wireless
interfaces? !  That certainly deserves its own bug report.

> Selecting Network Applet Edit Connections Wireless Security tab should
ask for pa[ss]word authorization to set/change password. It does not.
That's a bug.

Or else the behavior you describe is a feature request.

> What the Wireless Security tab does is just sit there
> for a couple minutes then (60 to 120 seconds) the menu
> appears. All the correct data is already there. Save, close.
> No changes made.

In another report can you please give the exact sequence of user actions
that leads to this phenomenon?

> Systems Settings Network still shows no network
> name while network applit edit connections shows
> the correct name. Why don't they both show the same
> network name? That's a bug.

Yep, report it.

> After 20 minutes, it suddenly does show the network name.
> Some time after that the wireless WPA connects.
> No new information was used. It already had network name,
> security type, and password when it rebooted.
> "connect automatically" does not. That's a bug.

There have been a few reports recently of NM taking a very long time at
startup to start working.

Shall we make this the topic of the present bug report (#1017738), that
it takes twenty minutes for NM to show ESSIDs?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1017738

Title:
  NM fails to connect to wireless WPA -- Quantal 25 June

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  Wireless WPA fails to "automatically connect" even though "enable
  wireless" is on when rebooting.

  Systems Settings Network  is blank where it should have the network
  name.   That's a bug.

  Correctly says wired network is unplugged.

  Network Applet Edit Connections says wired connection last used 5
  minutes ago.  Has not been plugged in since yesterday.  That's a bug.

  Network Applet Edit Connections says wireless connection last used 2
  hours ago.  Not true, last used 5 minutes ago.  That's a bug.

  Selecting Network Applet Edit Connections Wireless Security tab should
  ask for pathword authorization to set/change password.  It does not.
  That's a bug.

  What the Wireless Security tab does is just sit there for a couple
  minutes then (60 to 120 seconds) the menu appears.  All the correct
  data is already there.  Save, close.  No changes made.

  Wireless WPA still does not connect even though it was running before
  reboot.  "connect automatically" does not. That's a bug.

  Systems Settings Network still shows no network name while network applit 
edit connections shows the correct name.
  Why don't they both show the same network name?  That's a bug.

  After 20 minutes, it suddenly does show the network name.  Some time
  after that the wireless WPA connects.

  No new information was used.  It already had network name, security
  type, and  password when it rebooted.  "cinnect automatically" does
  not.  That's a bug.

  Any clue what to do to "automatically connect"?  This is a
  "Regression" since Precise works very usably on the same hardware.

  Jerry

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.4.0+git201206081144.2efeac8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
  Uname: Linux 3.5.0-1-generic i686
  ApportVersion: 2.2.5-0ubuntu1
  Architecture: i386
  Date: Mon Jun 25 18:39:51 2012
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120625)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1017738/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to