Nothing to add.

I can confirm this!

When connecting my Huawei 3520 I always have to enter the PIN (again). Which is
annoying.

Also as the textfield is not a passwordfield everybody can see the PIN which
is entered, this should not happen!

What informations/logs are needed to track the problem down?

best regards
Achim

Hi,

Also with the 0.8.1-2-b1 version I still have to enter a PIN.
After entering the PIN the modem becomes visible (in my case also a
CD-icon appears on the desktop).
I have to connect manually to the broadband-network (the connect auto
however is enabled in the panel).

After closing and remove the stick and re-installing the stick I have to
enter the PIN again and also enter
the mobile-provider password. The last is not the case when I start the
connection for the first time.

Reinstalling the 0.8 version (with the correct modemmanager (0.3.2) and
ppp (2.4.4) all is back to
normal.

This makes the network-manager 0.8.1 package unusable for
mobile-broadband usage (HUWAI modem).

Some logfile output:
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) starting connection 'Vodafone Business'
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> (ttyUSB0): device
state change: 3 -> 4 (reason 0)
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> (ttyUSB0): device
state change: 4 -> 6 (reason 0)
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> (ttyUSB0): device
state change: 6 -> 4 (reason 0)
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Sep  4 13:47:45 localhost modem-manager: (ttyUSB0) opening serial
device...
Sep  4 13:47:45 localhost modem-manager:
Modem /org/freedesktop/ModemManager/Modems/3: state changed (disabled ->
enabling)
Sep  4 13:47:45 localhost modem-manager:
Modem /org/freedesktop/ModemManager/Modems/3: state changed (enabling ->
enabled)
Sep  4 13:47:45 localhost modem-manager: CS registration state changed:
1
Sep  4 13:47:45 localhost modem-manager:
Modem /org/freedesktop/ModemManager/Modems/3: state changed (enabled ->
registered)
Sep  4 13:47:45 localhost modem-manager:
Modem /org/freedesktop/ModemManager/Modems/3: state changed (registered
-> connecting)
Sep  4 13:47:45 localhost modem-manager:
Modem /org/freedesktop/ModemManager/Modems/3: state changed (connecting
-> connected)
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 2 of 5 (Device Configure) scheduled...
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 2 of 5 (Device Configure) starting...
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> (ttyUSB0): device
state change: 4 -> 5 (reason 0)
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 2 of 5 (Device Configure) successful.
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 2 of 5 (Device Configure) complete.
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 3 of 5 (IP Configure Start) started...
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> (ttyUSB0): device
state change: 5 -> 7 (reason 0)
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> starting PPP
connection
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> pppd started with
pid 2713
Sep  4 13:47:45 localhost NetworkManager[1454]: <info> Activation
(ttyUSB0) Stage 3 of 5 (IP Configure Start) complete.
Sep  4 13:47:45 localhost NetworkManager[1454]:    SCPlugin-Ifupdown:
devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Sep  4 13:47:45 localhost NetworkManager[1454]:    SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no
ifupdown configuration found.
Sep  4 13:47:45 localhost modem-manager: (net/ppp0): could not get
port's parent device
Sep  4 13:47:55 localhost NetworkManager[1454]: <info> (ttyUSB0): device
state change: 7 -> 9 (reason 7)
Sep  4 13:47:55 localhost NetworkManager[1454]: <info> Marking
connection 'Vodafone Business' invalid.
Sep  4 13:47:55 localhost modem-manager:
Modem /org/freedesktop/ModemManager/Modems/3: state changed (connected
-> disconnecting)
Sep  4 13:47:55 localhost NetworkManager[1454]: <warn> Activation
(ttyUSB0) failed.
Sep  4 13:47:55 localhost NetworkManager[1454]: <info> (ttyUSB0): device
state change: 9 -> 3 (reason 0)
Sep  4 13:47:55 localhost NetworkManager[1454]: <info> (ttyUSB0):
deactivating device (reason: 0).
Sep  4 13:47:58 localhost avahi-daemon[1407]: Withdrawing workstation
service for ppp0.
Sep  4 13:47:58 localhost NetworkManager[1454]:    SCPlugin-Ifupdown:
devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Sep  4 13:48:00 localhost modem-manager:
Modem /org/freedesktop/ModemManager/Modems/3: state changed
(disconnecting -> registered)
Sep  4 13:49:14 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:14 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:15 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:15 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:15 localhost udevd[463]: can not read
'/lib/udev/rules.d/77-mm-usb-device-blacklist.rules'
Sep  4 13:49:15 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:18 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:18 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:18 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:21 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:21 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:22 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:24 localhost dbus-daemon: [system] Reloaded configuration
Sep  4 13:49:27 localhost modem-manager: (ttyUSB0) closing serial
device...
Sep  4 13:49:27 localhost modem-manager:
Modem /org/freedesktop/ModemManager/Modems/3: state changed (registered
-> disabled)
Sep  4 13:49:27 localhost modem-manager: Removed
modem /sys/devices/pci0000:00/0000:00:1d.2/usb7/7-1
Sep  4 13:49:27 localhost NetworkManager[1454]: <info> (ttyUSB0): now
unmanaged
Sep  4 13:49:27 localhost NetworkManager[1454]: <info> (ttyUSB0): device
state change: 3 -> 1 (reason 36)
Sep  4 13:49:27 localhost NetworkManager[1454]: <info> (ttyUSB0):
cleaning up...
Sep  4 13:49:27 localhost NetworkManager[1454]: <info> (ttyUSB0): taking
down device.

Hi,

It seems that this is still/again an issue on Debian Jessie with:
Package: network-manager
Version: 0.9.8.10-3
Package: modemmanager
Version: 1.0.0-4

If you search for the bug, several hits show up from 2010/2011, all
indicating that this issue is fixed already:
https://bugzilla.gnome.org/show_bug.cgi?id=633362
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/704123
https://bugzilla.gnome.org/show_bug.cgi?id=618532

Issue explained again:
I have a internal modem with a SIM card always inserted.
Bus 001 Device 003: ID 0bdb:193e Ericsson Business Mobile Networks BV
The connection is globally saved in
/etc/NetworkManager/system-connections/<name>
and includes the unlock PIN for the SIM card.

On every boot/network-manager restart a dialogue asks to enter the PIN
to unlock the SIM card. If you press escape it disappears. However,
connecting to the mobile network works fine! (so it probably uses the
stored pin anyway)
If you enter the PIN, you will be asked for superuser rights,
afterwards the pop-up shows up again. Also here connecting works fine.

So it seems, that the pop-up is unnecessary and annoying if the pin is
already stored, especially if you don't have superuser rights and you
are unaware of the fact that you can just ignore it then.

Thanks,
Stefan

It happens for me too since a few months, i can confirm Stefan's statement.
modemmanager    1.4.0-1
network-manager 0.9.10.0-3
here.

exactly same card in my case, also a system-connection with PIN configured.
The PIN request appears even if all the radios are disabled in network-
manager.

Txs, Ariel