Post APYrF88JVFPCR9hs3M by th@social.v.st
 (DIR) More posts by th@social.v.st
 (DIR) Post #APYrF88JVFPCR9hs3M by th@social.v.st
       2022-11-12T08:45:07Z
       
       0 likes, 0 repeats
       
       why I don't like firefox
       
 (DIR) Post #APYrF8Wm2IyHf19PBA by partly@cathode.church
       2022-11-12T08:46:55Z
       
       0 likes, 0 repeats
       
       @th I've never seen this before! what a terrible decision they made forcing this
       
 (DIR) Post #APYrF91GCxMFBZPkhM by js@mstdn.io
       2022-11-13T12:41:57Z
       
       0 likes, 0 repeats
       
       @partly @th It happens when you change the binaries while it’s running. The alternative is that it would outright crash. However, if you use Flatpak, this gets handled better and you won’t see this message.
       
 (DIR) Post #APYvHH3FiPX8UbcJqy by partly@cathode.church
       2022-11-13T13:27:09Z
       
       0 likes, 0 repeats
       
       @js oh! that'll be why I've not seen it because I'm on windows
       
 (DIR) Post #APYvmNT7uDoXNAYCrA by js@mstdn.io
       2022-11-13T13:32:23Z
       
       0 likes, 0 repeats
       
       @partly Yeah, it only happens when the package manager literally removes the files Firefox is using right now to replace them with new versions. :) If you use any kind of updater, e.g. on macOS or Windows or Flatpak, it doesn't happen.