← Back to team overview

touch-packages team mailing list archive

  1. touch-packages team
  2. Mailing list archive
  3. Message #05804

[Bug 704123] Re: Network Manager asks for the PIN even if it is memorized

  Thread Previous • Date Previous • • Thread Next 
** Description changed:

- Binary package hint: network-manager
+ ****************
+ HOW TO REPRODUCE
+ ****************
  
- I've configured a system-wide 3g broadband connection.
- In fact it's there a file with all the provided details in /etc/NetworkManager/system-connections/ .
- If I switch (log-out + log-in) to a non-administrative user, as soon as I plug the USB 3G modem I get asked the modem PIN.
- This is included into the mentioned file.
- The objective is to allow a "normal" user to connect with the modem with out the knowledge of username, password and PIN.
- The defails follow.
+ 1. Plug the USB modem into a port.
  
- $ lsb_release -a
- No LSB modules are available.
- Distributor ID:	Ubuntu
- Description:	Ubuntu 10.10
- Release:	10.10
- Codename:	maverick
+ 2. When you are asked to enter the modem's PIN, do along with the
+ "automatically unlock this device" option.
  
- How to reproduce the bug:
- 1. Log in as an administrative user (the first one you create at installation time)
- 2. Plug the USB 3G modem into a port
- 3. Go to System-->Preferences-->Newtwork Connections-->Mobile Broadband
- 4. Fill all the needed details (as well as the PIN)
- 5. Check "Automatically connect" and "Available to all users"
- 6. Test the connection is working.
- 7. Check the file in /etc/NetworkManager/system-connections/
- 8. Reboot (maybe just logout and long is enough)
- 9. Log in as the administrative user
- 10. Plug the USB modem
+ 3. Unplug the modem, and plug it again.
  
- What happens
- The system asks for the PIN. You can ignore this request. Then you can go to the
- netowrk icon and select the broadband connection and click it. This time the PIN
- is not required and the connection fires up.
  
- What is expected to happen
- No PIN is required at the modem insertion and the connection fires up automatically.
+ ******************
+ EXPECTED BEHAVIOUR
+ ******************
  
- Extra steps.
- 11. Create another non administrative user which is capable to connect through modems (groups dialout and dip).
- 12. Switch to this new user
- 13. Plug the USB modem.
+ - The modem to be automatically unlocked.
  
- What happens
- The system asks for aìthe PIN. You cannot ignore this request.
+ **************
+ REAL BEHAVIOUR
+ **************
  
- ProblemType: Bug
- DistroRelease: Ubuntu 10.10
- Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
- ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
- Uname: Linux 2.6.35-24-generic i686
- Architecture: i386
- CRDA: Error: [Errno 2] File o directory non esistente
- Date: Mon Jan 17 20:50:21 2011
- IfupdownConfig:
-  auto lo
-  iface lo inet loopback
- InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
- IpRoute:
-  192.168.129.0/24 dev wlan0  proto kernel  scope link  src 192.168.129.6  metric 2 
-  169.254.0.0/16 dev wlan0  scope link  metric 1000 
-  default via 192.168.129.254 dev wlan0  proto static
- Keyfiles: Error: [Errno 2] File o directory non esistente
- ProcEnviron:
-  LANG=it_IT.utf8
-  SHELL=/bin/bash
- RfKill:
-  0: phy0: Wireless LAN
-  	Soft blocked: no
-  	Hard blocked: no
- SourcePackage: network-manager
+ - You are asked to enter the PIN again.
+ 
+ ***********
+ WORK-AROUND
+ ***********
+ 
+ - The layout of the PIN dialogue is defined in /usr/share/nm-applet/gsm-
+ unlock.ui. If this file is renamed, whatever program spawns the dialogue
+ silently fails. Hence the bugging dialogue will not appear, but the
+ connection works nevertheless.
+ 
+ ****************
+ RELEVANT DETAILS
+ ****************
+ 
+ - The same behaviour when configuring the PIN from the "Network
+ Connections" menu.
+ 
+ - Even if the PIN is stored in "/etc/NetworkManager/system-
+ connections/", Network Manager cannot retrieve it.
+ 
+ - The bug makes the device to become locked as soon as network
+ connectivity is lost for a while.
+ 
+ - This bug forces administrators to tell the PIN to other users, while
+ they will rather want to keep it in secret and just allow themselves to
+ be able to configure the connectivity in specific devices.

** Bug watch added: GNOME Bug Tracker #733999
   https://bugzilla.gnome.org/show_bug.cgi?id=733999

** Changed in: network-manager
 Remote watch: GNOME Bug Tracker #618532 => GNOME Bug Tracker #733999

** Also affects: network-manager (Debian)
   Importance: Undecided
       Status: New

** Changed in: network-manager (Debian)
   Importance: Undecided => Unknown

** Changed in: network-manager (Debian)
       Status: New => Unknown

** Changed in: network-manager (Debian)
 Remote watch: None => Debian Bug tracker #591723

** Changed in: network-manager (Ubuntu)
       Status: Confirmed => Triaged

** Also affects: hundredpapercuts
   Importance: Undecided
       Status: New

** Tags removed: maverick natty oneiric patch
** Tags added: amd64 lucid utopic

** Changed in: hundredpapercuts
       Status: New => Triaged

** Changed in: hundredpapercuts
   Importance: Undecided => Medium

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

Title:
  Network Manager asks for the PIN even if it is memorized

Status in One Hundred Papercuts:
  Triaged
Status in NetworkManager:
  Unknown
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “network-manager” package in Debian:
  Unknown

Bug description:
  ****************
  HOW TO REPRODUCE
  ****************

  1. Plug the USB modem into a port.

  2. When you are asked to enter the modem's PIN, do along with the
  "automatically unlock this device" option.

  3. Unplug the modem, and plug it again.

  
  ******************
  EXPECTED BEHAVIOUR
  ******************

  - The modem to be automatically unlocked.

  **************
  REAL BEHAVIOUR
  **************

  - You are asked to enter the PIN again.

  ***********
  WORK-AROUND
  ***********

  - The layout of the PIN dialogue is defined in /usr/share/nm-applet
  /gsm-unlock.ui. If this file is renamed, whatever program spawns the
  dialogue silently fails. Hence the bugging dialogue will not appear,
  but the connection works nevertheless.

  ****************
  RELEVANT DETAILS
  ****************

  - The same behaviour when configuring the PIN from the "Network
  Connections" menu.

  - Even if the PIN is stored in "/etc/NetworkManager/system-
  connections/", Network Manager cannot retrieve it.

  - The bug makes the device to become locked as soon as network
  connectivity is lost for a while.

  - This bug forces administrators to tell the PIN to other users, while
  they will rather want to keep it in secret and just allow themselves
  to be able to configure the connectivity in specific devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/704123/+subscriptions
  Thread Previous • Date Previous • • Thread Next