Bug 415395

Summary:	Wifi drops one in two times after waking from suspension...
Product:	[Plasma] plasmashell	Reporter:	PK <pieterkristensen>
Component:	Networking in general	Assignee:	Jan Grulich <jgrulich>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	jgrulich, lamarque, lukas.tinkl, nate
Priority:	NOR
Version First Reported In:	master
Target Milestone:	1.0
Platform:	Neon
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=397252
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description PK 2019-12-20 14:05:57 UTC

SUMMARY
After Neon "wakes" from suspension, one in two times there is no wifi connection any more. I experienced this on three different machines. It is irritating and leaves a bad impression of Neon. But the solution is in fact very simple!
In the file /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf change the line wifi.powersave = 3 
to 
wifi.powersave = 2
After I did this the problem didn't occur any more. And there is no reason for me to doubt Neon! 
It is a friendly suggestion of a happy user.


STEPS TO REPRODUCE
1. startup Neon KDE
2. bring machine in suspension state
3. wake the computer - very often there is no internet connection any more.

OBSERVED RESULT
No connection to the web


EXPECTED RESULT
Connection to the web

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE neon 5.17
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION

Comment 1 PK 2021-04-17 11:36:42 UTC

I received an email concerning this bug. Very cool! I had forgotten it. But I found a way to work around it.

I found that when I changed "wifi.powersave = 3" to "wifi.powersave =2" in the file /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf, wifi kept allways working on that system. 
To achieve this I used sed: sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/g' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

I now have an other machine. That doesn't need this tweak.

Comment 2 Ben Cooksley 2024-12-23 18:23:50 UTC

Bulk transfer as requested in T17796

Comment 3 Nate Graham 2025-08-07 16:19:28 UTC

Seems like this was ultimately a wifi driver/power management bug.