Bug 1029881

Summary: After wake up the WiFi connection is lost
Product: [Fedora] Fedora Reporter: Miro Hrončok <mhroncok>
Component: NetworkManagerAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: angiolucci, dcbw, kevin, mhroncok
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 03:02:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Miro Hrončok 2013-11-13 13:07:02 UTC
Description of problem:
When I wake up from supend, the nm-applet shows "in progress" icon and it takes a while to connect back to the WiFi. VPN connection is lost.

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


How reproducible: Always


Steps to Reproduce:
1. Be connected to WiFi via nm-applet
2. Connect to VPN if possible
3. Suspend the system via # systemctl suspend
4. After suspend, wake up ASAP
5. Suspend the system via Xfce logout option
6. After suspend, wake up ASAP

Actual results:
After 4. the WiFi is connected as well as VPN. Right after suspend.
After 6. the WiFi is disconnected and reconnects. VPN connection is lost.

Expected results:
Both acts as after 4.

Additional info:
It has always been like that. But now I see it has not to be that way.

Comment 1 Miro Hrončok 2013-11-13 13:08:11 UTC
I forgot to say: xfce4-session-4.10.1-3.fc20.x86_64
But that's not relevant IMHO anyway.

Comment 2 Kevin Fenzi 2013-11-13 16:50:31 UTC
Xfce just calls systemd here, so not sure what the difference could be. 

Moving over to NetworkManager to see if they know what could be causing this.

Comment 3 Miro Hrončok 2013-11-13 17:16:37 UTC
Could you at least reproduce the behavior, Kevin?

Comment 4 Dan Williams 2013-11-13 20:03:09 UTC
system journal logs from NetworkManager would be helpful here to see if NetworkManager is getting the right messages from upower or systemd on suspend/resume.

Comment 5 Miro Hrončok 2013-11-13 20:32:56 UTC
(In reply to Dan Williams from comment #4)
> system journal logs from NetworkManager would be helpful here
And those are located where exactly?

Cause `locate NetworkManager | grep log` brings up nothing.

Comment 6 Miro Hrončok 2013-12-02 07:46:26 UTC
Could you please help me with that a bit?

Comment 7 Kevin Fenzi 2013-12-02 15:14:08 UTC
'journalctl -u NetworkManager' should have them.

Comment 8 Miro Hrončok 2013-12-02 15:52:19 UTC
Thanks.

Here you go: http://paste.fedoraproject.org/58411/99460138

Comment 9 Miro Hrončok 2013-12-02 15:54:02 UTC
Oh, this one is actually better: http://paste.fedoraproject.org/58412/99619138

Comment 10 Fedora End Of Life 2015-05-29 09:44:58 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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 11 Fedora Admin XMLRPC Client 2015-08-18 14:57:15 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 12 Fedora End Of Life 2015-11-04 10:01:06 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

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 21 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 13 Fedora End Of Life 2015-12-02 03:02:18 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.