Bug 390149 - Nm cant reconnect after standby
Summary: Nm cant reconnect after standby
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasma-nm
Classification: Plasma
Component: general (show other bugs)
Version: 5.12.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-09 13:24 UTC by info
Modified: 2018-02-28 09:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description info 2018-02-09 13:24:16 UTC
I have openSUSE Tumbleweed installed with newest KDE Plasma 5.12. Since this update the network manager cant connect to the internet after waking the computer up again from standby.

I have already written to KDE IRC to get confirmations, that this bug is not a openSUSE bug but a plasma bug. One user told me, he has the same problem with antergos.

How to reproduce:
1. Put computer in standby
2. Wake computer up
3. (bug) No internet connection. Networkmanager doesnt show any connections.

I already tried to switch the networkmanager into planemode and off again. Still same problem. I also already tried to switch to opensuse's own network manager (wicked) and back again because this procedure boots the network manager up again. Still same problem.

Thanks
Comment 1 Jan Grulich 2018-02-23 10:35:08 UTC
Do you see any networks with "nmcli device wifi list"?
Comment 2 info 2018-02-23 11:30:19 UTC
I have a desktop computer without wifi. It is connected via ethernet.

so nmcli device wifi list shows no response. Also no response when executing the command before standby.
Comment 3 Jan Grulich 2018-02-23 11:33:19 UTC
I see, in that case what's the output from "nmcli -f all device show enp0s25". Replace enp0s25 with your device name.
Comment 4 info 2018-02-23 15:48:57 UTC
The log can be found here: https://pastebin.com/ACi4rUdn

I created two sections for you. The first before standby and the second after standby.
Comment 5 Jan Grulich 2018-02-26 13:26:14 UTC
From the log I see that even NetworkManager doesn't show there is available connection for your device, which means that the problem is in NetworkManager as we rely on information it provides. Please report this problem to NetworkManager bugzilla [1].

[1] - https://bugzilla.gnome.org/page.cgi?id=browse.html&product=NetworkManager
Comment 6 info 2018-02-26 14:58:29 UTC
Thanks Jan Grulich for your help. After your answer I posted my problem in the opensuse kde IRC. One user had the same problem and fixed it with adding the parameters "pci=nomsi,noaer" to his boot options. This also fixed my problem.

Maybe it is a bug in the driver for some network chips. So this bug can be closed.