Bug 677344

Summary: nm-applet 0.8.1 fails DSL connect until manual restart
Product: [Fedora] Fedora Reporter: Vladimir Vinogradov <vladimirvgv>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 13:38:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Strace and console logs where nm-applet 0.8.1 fails DSL connect until manual restart.
none
Part of /var/log/messages where nm-applet 0.8.3.996 fails DSL connect until manual restart. none

Description Vladimir Vinogradov 2011-02-14 13:01:45 UTC
Created attachment 478620 [details]
Strace and console logs where nm-applet 0.8.1 fails DSL connect until manual restart.

Description of problem:

When trying to connect to preconfigured DSL connection (PPPoE, CHAP) with nm-applet, in following cases:
1. If in first attempt was suddenly typed wrong password.
2. If within first attempt Gnome keyring asked for a password to unlock it.
3. If first attempt not succeed with any other reason (other side's temporary malfunction, that was immediately fixed),
nm-applet fails at second and next attempts to connect even if typed password is correct.

Version-Release number of selected component (if applicable):

Linux version 2.6.35.10-74.fc14.i686 (mockbuild.fedoraproject.org) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #1 SMP Thu Dec 23 16:17:40 UTC 2010

NetworkManager-gnome-0.8.1-10.git20100831.fc14.i686

How reproducible:
Always, until manual restart with
$ killall nm-applet
$ nm-applet &
After manual restart nm-applet forgets about failures and connects on click without prompting a password.

Steps to Reproduce:
1. Reproduce one of conditions listed in Description above.
2. Try to repeat a connect clicking on nm-applet UI, type correct password when asked.
3.
  
Actual results:
Re-asking a password without obvious reasons. Fails to connect.
But after manual restart all is ok.

Expected results:
Successful connect at next attempt when correct credentials are provided (or technical problems definitely resolved) without necessity of manual restart.

Additional info:

It looks like nm-applet had already saved the correct password in previous run. But it definitely don't used it properly until manual restart.

Logs attached in nm-applet-logs.tgz, comments included.
($ strace -tt -s99 -f -onm-appl.st.log  2>&1 | tee nm-appl.st-msg.log) - before restart
($ strace -tt -s99 -f -onm-appl.st.log-1  2>&1 | tee nm-appl.st-msg.log-1) - after restart

Comment 1 Dan Williams 2011-02-25 22:32:45 UTC
can you grab /var/log/messages from a failed connect attempt like you describe?  We need to see whether NM thinks it's getting secrets from the applet.

Comment 2 Vladimir Vinogradov 2011-03-02 11:41:55 UTC
Created attachment 481842 [details]
Part of /var/log/messages where nm-applet 0.8.3.996 fails DSL connect until manual restart.

Comment 3 Vladimir Vinogradov 2011-03-02 11:47:06 UTC
(In reply to comment #1)
> can you grab /var/log/messages from a failed connect attempt like you describe?
>  We need to see whether NM thinks it's getting secrets from the applet.

Please take relevant part of /var/log/messages with "USER:" additional comments added by hand.

Comment 4 Fedora End Of Life 2013-04-03 14:21:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 5 Fedora End Of Life 2015-01-09 16:34:06 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-02-17 13:38:16 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.