141–150 of 410 posts
audit: type=1400 audit(1642063521.864:246): apparmor="DENIED" operation="ptrace" profile="snap.firefox.firefox" pid=9868 comm="Shutdow~minator" requested_mask="trace" denied_mask="trace" peer="snap.firefox.firefox"
I really don't like it, but turning off Apparmor worked for me. Not sure what caused AppArmor to start complaining all of a sudden.
What worked for me was disabling HTTP3 support with the 'network.http.http3.enabled' key in about:config and then restarting Firefox. Seems like it's stuck in the 'SocketThread', repeatedly doing this: 2022-01-13 08:20:53.075936 UTC - [Parent 4106991: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=333 state=4 [this=7f6e295623a0]
Earlier quoted context omitted.
Oh wow, thank you so much for this. I've been trying to troubleshoot this for hours but because my browser didn't work I never thought of checking HN to see if other people had this as well. Another score for automatic updates I guess.
I'm thankful to work in a team. As my IT dept has a habit of breaking stuff with AV and other crap-ware, I already asked if anyone else was having problems with Firefox after 5 minutes of trying to figure out what was wrong, after which someone pointed me to this thread
Very frustrating this. Fortunately it isn't a Tuesday or I would have been ready for murder by now.
What worked for me was disabling HTTP3 support with the 'network.http.http3.enabled' key in about:config and then restarting Firefox. Seems like it's stuck in the 'SocketThread', repeatedly doing this: 2022-01-13 08:20:53.075936 UTC - [Parent 4106991: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=333 state=4 [this=7f6e295623a0]
And here I go explaining my friends and family I helped switch to Firefox that the browser I've installed on their computers got broken at the beginning of a new day while Edge and Chrome work fine... personally, I know very well bugs happen and I'm not mad, but this certainly hurts the confidence in it for the non-tech people.
Weird data point. Firefox on my laptop borked as per this thread all of a sudden. I spent like 30 min trying to troubleshoot it and failed, then i moved to my desktop and there it was, working Firefox. I'm posting this from it. Have they already fixed the problem and it was remote?
Read the thread.
So what's strange here is that these hangs are weeks after Firefox 95.0.2 was released. That points to either DoH provider or some HTTP 3 server triggering the buggy behavior at scale. Either is fairly scary.
It is time for Mozilla to stop messing around. They are losing user trust extremely fast. A silent FireFox update that cripples the browser? No active update was done since yesterday and this morning: a broken browser. Please stop non-browser development and let me pay a monthly fee for a decent browser! I don’t want a VPN service, bookmark readers or other crap. I want Mozilla to defend the open web and create an op…
Have you any idea how complex a browser needs to be? I hope this team of plucky, idealistic coders can keep up with all the latest and greatest web developments devised by the thousands of engineers at Google et al.
The web as an open, human-sized system is dead.
Earlier quoted context omitted.
Which wasn't present in previous versions. So this is still a consequence of updates. But now, to make it extra hard to troubleshoot we put in timebombs in your automatic updates that will go off some fine Thursday morning without any warning or indication that something has just changed. Idiots.
> Which wasn't present in previous versions. So this is still a consequence of updates. Looks like HTTP/3 has been in Firefox for around a year
This is a great way to bypass continuity testing, I really pity all those people working the desks in hospitals right now using FireFox who are typically less savvy than your average HN'er in trying to get their work done.
If you ship a browser with a time-bomb you are utterly irresponsible.
Reddit Thread with tons of comments already: https://old.reddit.com/r/firefox/comments/s2u7eg/is_firefox_... I have the same issue, a different profile worked edit: Twitter feed https://twitter.com/search?q=firefox&src=typed_query&f=live There better be some hell of a post mortem edit2: `network.http.http3.enabled` in about:config to false fixed it for me. Source: https://old.reddit.com/r/firefox/comments/s2u7eg/is_f…