I love the obscure problems. I can’t seem to web search myself out of this one. I’m not even sure if this is Fedora specific, but it’s happening on Fedora 35. I’m hoping someone smarter than me cares enough about Epiphany and Fedora to help me out.
I’m trying to use a webkit browser to do debug testing for what would most likely be Safari related problems. I have a KVM with MacOS setup, but to hell if I want to start MacOS every time something that might be a webkit issue crops up.
The minute I opened Epiphany or Midori, I get multiple timeouts and failed DNS resolutions. Sometimes I can resolve this with a reboot/resetting my network/systemd-resolved, but it always comes back and it’s super annoying. It gets so bad that I can’t even load duckduckgo.com.
This doesn’t happen in FireFox or Blink based browsers. I’m not even sure where to start with useful debug info, I apologize.
Sure looks like systemd-resolved is working fine. That’s good.
In your bug report you proved that something is going very wrong with DNS. I’ve attached a test script there to see if GResolver is working properly. As long as systemd-resolved is happy, GResolver should be too… but this is weird, so maybe not.
We further narrowed down the issue to the setting org.gnome.system.proxy mode being erroneously toggled to “auto”. This was probably a mistake I made at some point that reared its ugly head only while using Epiphany. No proxy was configured and the discovery process tied things up.
Set that to “none” (or “Off” in the GUI) and Epiphany works as intended.