Bug 2118137 - Wifi won't auto connect after wake up from suspend, Only on Kernel 5.19
Summary: Wifi won't auto connect after wake up from suspend, Only on Kernel 5.19
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-14 13:39 UTC by plumlis
Modified: 2023-05-25 17:41 UTC (History)
29 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 17:41:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Log from gnome-log, from suspend waking up (18.90 KB, text/plain)
2022-08-14 13:39 UTC, plumlis
no flags Details

Description plumlis 2022-08-14 13:39:20 UTC
Created attachment 1905442 [details]
Log from gnome-log, from suspend waking up

Created attachment 1905442 [details]
Log from gnome-log, from suspend waking up

Description of problem:


After upgraded kernel to 5.19, And I found that my laptop won't autoconnect to wifi after resume from suspend.

I can connect to wifi manually by click to menu. Or I have to wait a looong time to see it autoreconnecting.

It's okay on Kernel 5.18 and Only effected in Kernel 5.19.


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

Fedora 36 64bit Gnome 43

Thinkpad X1 Carbon 2021 9th


How reproducible:


Steps to Reproduce:
1. Make laptop to suspend
2. Wake up laptop from suspend
3. You will see wifi is still not auto reconnect for a long time. About 3 min later it may autoreconnectd.

Actual results:

Won't connect to wifi ater suspend immediately


Expected results:

Connect to wifi after suspend immediately


Additional info:

Comment 1 plumlis 2022-08-14 13:45:05 UTC
I'm not sure if is Network-manager related.
But can confrim this issue is only on Kernel 5.19

Comment 2 Ben Cotton 2023-04-25 17:46:13 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ludek Smid 2023-05-25 17:41:08 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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


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