The only thing I found in settings was tracking. I changed it to custom and unchecked
everything. It always fails at the login screen. Either before or after I enter my
credentials.
Other pages work fine.
Anyone using Firefox?
On Tue, Jul 25, 2023 at 01:01:04PM -0600, Linus Sphinx wrote:
Upgrade to a 64 bit virus. Anything in F12/errors?
Maybe it's the web page
cross domain or something and firefox has upgraded their security model.
Sandwich menu button->settings->security and put it in stupid mode, scary
but it might work.
On Tue, Jul 25, 2023 at 12:35 PM Gary <saclug(a)garymcglinn.com> wrote:
> I don't really get on the upgrade treadmill. I've been running Firefox 84
> on Fedora 23 or something for awhile. Its in a VM I had a system issue
> with the host and had to do a reinstall and upgraded to fc 36. Everything
> was fine, running my fc 23 VM's on a fc 36 host. I'm on a different VM,
my
> "fun" VM as I write this, which also runs Firefox 84 on fc 23 with no
> problems. I'll upgrage at some point.
>
> The VM with the issues is my "finance" VM. I use it for my credit cards
> and banking and all that. Banks started to complain about my Firefox 84,
> so I tried to upgrade to 113. It crashes. A lot. So, I built a new VM
> with fc 38. And installed Firefox 115. It crashes almost immediately.
> But I was able to get some forensics. Its complaining that it is sending a
> 64 bit code to a subsystem that "doesn't support it". Implying that
there
> is a 32 bit library somewhere.
>
> I sort of do need to log in to banks and all that. Any thoughs or
> suggestions? It seems really unlikely that there would be a 32 bit library
> somewhere.
>
> Desktop browsers and Firefox are getting increasingly less mindshare. Is
> this just EOL thrashing?
>
> Any thoughts?
>
> As you may have guessed, the hardware is pretty old, but I don't see where
> that would be an issue with this.
>
> -Gary
> _______________________________________________
> Lug-nuts mailing list -- lug-nuts(a)bigbrie.com
> To unsubscribe send an email to lug-nuts-leave(a)bigbrie.com
>