Bug 1204057 - sometimes ipv4 communication completely lost for firefox after sleep (laptop, lid shut, powersave via kde menu)
Summary: sometimes ipv4 communication completely lost for firefox after sleep (laptop,...
Status: NEW
: 1214644 (view as bug list)
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Firefox (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Leap 15.4
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Factory Mozilla
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-05 14:59 UTC by andreas bittner
Modified: 2023-08-28 05:48 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andreas bittner 2022-10-05 14:59:30 UTC
vanilla leap 15.4, x64, new hp probook laptop, wifi connection, with networkmanager.

the wifi network is dhcp (dhcpv4) based, extending the details on the network manager of this wifi connection shows proper ipv4 address, ipv4 gateway, ipv4 dns servers, ipv6 address and ipv6 default gateway, the wifi speed. all reads normal. see below. only firefox affected ipv4 wise.




initially firefox running with multiple tabs an windows, all okay.

when powersaving the laptop (sleep from kde menu) or when closing the lid and waking the laptop after a while again

firefox seems to lose (deny) all ipv4 related communication features. ipv6 websites work all fine (google, many others)

ctrl+shift+i (shows only ipv6 ip address column, ipv4 only sites show unknown for ip column)

firefox is absolutely incapable to resume working on ipv4 objects.
new tabs down help
new windows dont help
new private tab/window doesnt help

only a complete shutdown of the firefox application and restarting it up help.
all firefox tabs and windows then work again fine on ipv4 stuff


disconnecting the wifi via networkmanager and reconnecting it again after such power events dont help either.

and the very same time a terminal (konsole) traceroute or ping explicitly on those malfunctioning hostnames ipv4 only work perfectly, traceroute traces away (so gateway etc. is all set), ping replies are incoming and work nicely as well.

everything in firefox seems to be limited to ipv6 stack, ipv4 stack seems unavailable for firefox in these moments.

if i am not totally wrong this bug is not always happening as it would drive me more nuts then and I would have filed this bug earlier ;(

also in the network manager I can check and uncheck the wifi symbol to make the wifi (interface or driver or whatever) start over but that does not help as well during certain times. its a combination of works and sometimes doesnt.

firefox or related libraries, listening sockets or connections or whatnot buggy?
thanks.
Comment 1 andreas bittner 2022-10-10 07:48:45 UTC
last night I deactivated the wifi checkbox in the network manager completely, before I put this laptop to sleep via kde menu.

next morning laptop woke again, reactivated the wifi checkbox, the networkmanager reestablished the machines addresses, ipv6 and ipv4 both ping, but firefox again can not browse and surf any ipv4 objects at all.

restarting firefox brings back full dualstack functionality of firefox again.
Comment 2 Andreas Stieger 2023-08-26 13:07:18 UTC
*** Bug 1214644 has been marked as a duplicate of this bug. ***
Comment 3 Martin Sirringhaus 2023-08-28 05:48:30 UTC
Might be https://bugzilla.mozilla.org/show_bug.cgi?id=1794242