code logs -> 2023 -> Fri, 03 Nov 2023< code.20231102.log - code.20231104.log >
--- Log opened Fri Nov 03 00:00:40 2023
00:56 panzerfaus [uid279771@Nightstar-l49s2t.irccloud.com] has joined #code
03:06 panzerfaus [uid279771@Nightstar-l49s2t.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
03:49 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
04:13 himi [sjjf@Nightstar-1drtbs.anu.edu.au] has quit [Ping timeout: 121 seconds]
04:31 Degi_ [Degi@Nightstar-sqan4d.pool.telefonica.de] has joined #code
04:32 Degi [Degi@Nightstar-t2pppi.pool.telefonica.de] has quit [Ping timeout: 121 seconds]
04:32 Degi_ is now known as Degi
05:52 himi [sjjf@Nightstar-o4k.pal.170.103.IP] has joined #code
05:52 mode/#code [+o himi] by ChanServ
13:54 Vornotron [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
13:54 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
13:54 mode/#code [+qo Vornicus Vornicus] by ChanServ
13:55 Vornotron [Vorn@ServerAdministrator.Nightstar.Net] has quit [[NS] Quit: Leaving]
15:31 panzerfaus [uid279771@Nightstar-l49s2t.irccloud.com] has joined #code
16:44
< abudhabi>
Bloody hell. Firefox just refused to work in new tabs until I restarted it. Explicitly so! Restart required. 😐
17:17
<&ToxicFrog>
Installed an FF update when it was running, I take it?
17:17
< abudhabi>
Probably.
17:19
<&ToxicFrog>
AIUI, this is because opening new tabs may require spawning new sandbox processes, which requires exec()ing or ldopen()ing stuff on disk that was just replaced by the update, which -- in the case of an ABI mismatch -- can flat crash your firefox session
17:19
<&ToxicFrog>
So they force a restart to prevent that from happening
17:20
<&ToxicFrog>
(I suspect that this is not an issue on nixos, but haven't tested it there yet)
17:20
< abudhabi>
I see.
17:21
< abudhabi>
Chromium doesn't do this for some reason.
17:25
<@gnolam>
It's specifically Firefox on Linux.
17:25
<@gnolam>
It's weird that it doesn't warn you.
17:29
< abudhabi>
I was surprised.
17:39
<&ToxicFrog>
Firefox on windows can't swap out the files while they're in use anyways, and Chrome does something different, AFAICT, where it stages the files and installs them properly on next startup (and constantly whines about how you need to restart to install updates until then)
17:39
<&ToxicFrog>
gnolam: warn you how? FF's first clue that you're installing system updates is when the files on disk change.
17:40
<&ToxicFrog>
If they want to make this a smoother user experience I think they'd have to do something similar to what Chrome does.
17:57
< abudhabi>
Well, what Chrome does is a warning, I suppose.
18:45 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
18:47
<&ToxicFrog>
Chrome's approach is "you can update without interference with your current session, but none of the updates actually take effect until you restart"
18:47
<&ToxicFrog>
FF is "updating effectively forces you to restart to apply the update"
21:28 Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has joined #code
21:41 panzerfaus [uid279771@Nightstar-l49s2t.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
22:03 panzerfaus [uid279771@Nightstar-l49s2t.irccloud.com] has joined #code
23:11 Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has quit [Ping timeout: 121 seconds]
--- Log closed Sat Nov 04 00:00:41 2023
code logs -> 2023 -> Fri, 03 Nov 2023< code.20231102.log - code.20231104.log >

[ Latest log file ]