Can't unlock UMTS modem with PIN

Bug #1442406 reported by Andreas Weller
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Incomplete
Medium
Unassigned
policykit (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

I can't unlock my UMTS USB modem with Lubuntu 15.04 (It works on xubuntu 14.10)

(nm-applet:3280): nm-applet-WARNING **: Failed to send PIN to devid: 'c8efb515c36471e33a1e711a672ed5cb45b5c5a2' simid: '(null)' : PolicyKit authorization failed: challenge needed for 'org.freedesktop.ModemManager1.Device.Control'

lsusb output:
Bus 003 Device 005: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E230/E270/E870 HSDPA/HSUPA Modem

usb-modeswitch usb-modeswitch-data is installed.

Any idea?

Thank you!

Regards,
  Andreas Weller

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager-gnome 0.9.10.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Apr 10 01:06:29 2015
ExecutablePath: /usr/bin/nm-applet
InstallationDate: Installed on 2015-03-28 (12 days ago)
InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
IpRoute:
 default via 192.168.1.1 dev wlan0 proto static metric 1024
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.141
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/2 weller 1 094f12c6-3f6a-49bc-aff8-ef0ec57f7512 /org/freedesktop/NetworkManager/ActiveConnection/0
 ttyUSB1 gsm disconnected /org/freedesktop/NetworkManager/Devices/4 -- -- --
 eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

Revision history for this message
Andreas Weller (weller-andreas-weller) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager-applet (Ubuntu):
status: New → Confirmed
Changed in policykit (Ubuntu):
status: New → Confirmed
Revision history for this message
Hugo Otto (hugootto) wrote :

Exactly the same with me. Works with Ubuntu 15.04.

Changed in network-manager-applet (Ubuntu):
importance: Undecided → Medium
Changed in policykit (Ubuntu):
importance: Undecided → Medium
Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

If you use the workaround at #1424362:

WORKAROUND
 1. open Default Apps for LXSession
 2. click on "autostart tab"
 3. make sure "PolicyKit Authentication Agent" is checked
 * NOTE: works on a per user basis

…is this fixed?

If so, please mark it as a dupe.

If it is not, then we need some more information. Specifically, I would like to know if this affects any other network manager tasks and if so, which. I'd start with Ethernet since everyone has that and it's easy to test. Also, having very clear steps to reproduce would be great.

Thus, I'm going to call it incomplete.

Changed in network-manager-applet (Ubuntu):
status: Confirmed → Incomplete
Changed in policykit (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Andreas Weller (weller-andreas-weller) wrote :

The workaround at #1424362 works.
Finally I can unlock 3G modem's SIM.

So I'll mark this bug as duplicate.

But now it asks once for the PIN and then for the current user's password. Is this really necessary?

Regards,
  Andreas

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.