desktop-packages team mailing list archive

["Jonas G. Drange" <1434591@xxxxxxxxxxxxxxxxxx>]

Also, the [mako] was there from the start. Could mako mean anything else
than Nexus 4? In that case, do you need a serial number/production date?

** Description changed:

  $ system-image-cli -i
  current build number: 138
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-17 15:04:46
  version version: 138
  version ubuntu: 20150317.1
  version device: 20150210
  version custom: 20150317.1
  
  I have tried most types of security, but the spec [2] says for maximum
  compatibility, most of the options should be left blank. Blank settings
  failed on both a and bg bands.
  
  How to reproduce:
  1. Create a secure hotspot (I am using this [1] script)
  2. Confirm that the hotspot is active and appears secured for other devices
  
  What happens:
  Connecting to it fails.
  
  What should have happened:
  Connecting to it should not fail.
  
  Excerpt from syslog
  http://pastebin.ubuntu.com/10627959/
  
  [1] http://pastebin.ubuntu.com/10683465/
+ [2] https://developer.gnome.org/NetworkManager/stable/ref-settings.html

-- 
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/1434591

Title:
  [mako] Cannot connect to a secure, shared "ap" hotspot

Status in network-manager package in Ubuntu:
  New

Bug description:
  $ system-image-cli -i
  current build number: 138
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-17 15:04:46
  version version: 138
  version ubuntu: 20150317.1
  version device: 20150210
  version custom: 20150317.1

  I have tried most types of security, but the spec [2] says for maximum
  compatibility, most of the options should be left blank. Blank
  settings failed on both a and bg bands.

  How to reproduce:
  1. Create a secure hotspot (I am using this [1] script)
  2. Confirm that the hotspot is active and appears secured for other devices

  What happens:
  Connecting to it fails.

  What should have happened:
  Connecting to it should not fail.

  Excerpt from syslog
  http://pastebin.ubuntu.com/10627959/

  [1] http://pastebin.ubuntu.com/10683465/
  [2] https://developer.gnome.org/NetworkManager/stable/ref-settings.html

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