Bug 2211654

Summary:	No network connectivity after suspend/resume cycle: "The specified configuration cannot be used."
Product:	[Fedora] Fedora	Reporter:	ValdikSS <iam>
Component:	qt5-qtbase	Assignee:	Than Ngo <than>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	37	CC:	jgrulich, jreznik, kde-sig, rdieter, than
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 ValdikSS 2023-06-01 11:05:09 UTC

Description of problem:

Many Qt5 software can't access the network after suspend/resume cycle of the PC, forcing the user to restart such programs.
Error string is: "The specified configuration cannot be used."

This issue applies since at least Qt5 5.15.2 in Fedora 35, still affecting in Fedora 37 at least:

QuiteRSS https://github.com/QuiteRSS/quiterss/issues/1517
QuteBrowser https://github.com/qutebrowser/qutebrowser/issues/129
Crow-translate https://github.com/crow-translate/crow-translate/issues/383


Version-Release number of selected component (if applicable):
qt5-qtbase-5.15.9-3.fc37.x86_64


How reproducible:
100%


Steps to Reproduce:
1. Install QuiteRSS or crow-translate (not packaged in Fedora, present in COPR)
2. Suspend the laptop, wait a minute
3. Resume the laptop


Actual results:
The software mentioned can't access the network anymore, while network connection is present and working.


Expected results:
Software continue to work after resume.


Additional info:
I tried to debug the issue in 2022 (with QuietRSS bug report), and the  	presumably this is either of those:
https://bugreports.qt.io/browse/QTBUG-84907
https://bugreports.qt.io/browse/QTBUG-46542


Workaround:
Disable "networkbearer" plugin of Qt5

$ sudo mv /usr/lib64/qt5/plugins/bearer /usr/lib64/qt5/plugins/bearer.mv

Comment 1 ValdikSS 2023-06-18 19:31:48 UTC

Added QTBUG: https://bugreports.qt.io/browse/QTBUG-114666

Simpliest workaround: start the affected applications without the network, connect to the network later.

Comment 2 ValdikSS 2023-06-18 22:56:25 UTC

Please consider packing /usr/lib64/qt5/plugins/bearer/libqnmbearer.so as a separate package, so it could be just not installed to prevent the issue.

Both Qt developer and KDE developer told this is the best workaround.