Bug 1313836 - broadband PIN dialog wont appear
broadband PIN dialog wont appear
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager (Show other bugs)
7.2
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Beniamino Galvani
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-02 07:29 EST by Tomas Pelka
Modified: 2016-11-03 15:08 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-03 15:08:25 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tomas Pelka 2016-03-02 07:29:39 EST
Description of problem:
PI dialog fro broadband devices won't appear unless nm-applet is running.

Version-Release number of selected component (if applicable):
NetworkManager-1.0.6-27.el7
network-manager-applet-1.0.6-2.el7

How reproducible:
100%

Steps to Reproduce:
1. insert broadband modem with PIN locked SIM
2.
3.

Actual results:
PIN dialog for unlocking SIM wont appear unless nm-applet is running 

Expected results:
PIN dialog should be rewritten for standard gnome-shell NM dialogues

Additional info:
Comment 1 Vladimir Benes 2016-03-02 07:50:55 EST
Entering PIN into profile (aka gsm.pin) and upping it should result in connected device not:
Error: Connection activation failed: No suitable device found for this connection.

[vbenes@trautenberg ~]$ nmcli connection up id O2\ Default 
Error: Connection activation failed: No suitable device found for this connection.
[vbenes@trautenberg ~]$ nm-applet
[vbenes@trautenberg ~]$ nmcli connection up id O2\ Default 
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/19)

so from above mentioned I would say we need to have nm-applet (network-manager-applet rpm) to be installed as a dependency of NetworkManager-wwan and when upping gsm type connection we should be able to start nm-applet prior, right? Not sure how this behave in non-gui mode but that's kind of step 2.

Stopping nm-applet after shutting down the connection would be nice too :-)
Comment 2 Beniamino Galvani 2016-07-21 04:14:03 EDT
(In reply to Tomas Pelka from comment #0)
> Description of problem:
> PI dialog for broadband devices won't appear unless nm-applet is running.

Tested on RHEL 7.3, a Gnome-shell dialog is displayed asking for
PIN/password upon connection to a modem device.

(In reply to Vladimir Benes from comment #1)
> Entering PIN into profile (aka gsm.pin) and upping it should result in
> connected device not:
> Error: Connection activation failed: No suitable device found for this
> connection.

This seems to work now in RHEL 7.3.

> so from above mentioned I would say we need to have nm-applet
> (network-manager-applet rpm) to be installed as a dependency of
> NetworkManager-wwan and when upping gsm type connection we should be able to
> start nm-applet prior, right? Not sure how this behave in non-gui mode but
> that's kind of step 2.

NM can either use system-stored secrets or other agents as gnome-shell
or even nmcli itself. For example you can use:

 nmcli --ask connection up O2

to use the built-in secret agent. Or also start a agent with:

 nmcli agent

that will receive the secret requests for new activations. So the
dependency to nm-applet is not needed.


Can you please confirm everything works as expected and this can be closed?
Comment 3 Tomas Pelka 2016-07-26 05:35:43 EDT
Works for me, feel free to move to MODIFIED and add to https://errata.devel.redhat.com/advisory/22920

Thanks
-Tom
Comment 5 Vladimir Benes 2016-08-31 03:53:30 EDT
This works well now with both GS agent and nmcli as an agent with --ask option.
Comment 7 errata-xmlrpc 2016-11-03 15:08:25 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2581.html

Note You need to log in before you can comment on or make changes to this bug.