About:support was very interesting. I wasn't aware of it, but have used
about:performance, about:config, and about:memory in the past. It told me that the error
was in CanvasRenderer, which doesn't help a lot. I tried dumping and refreshing
various things, but the issue still persisted.
Then I rebooted in troubleshooting mode. Seems stable. At least I've done the things
that made it crash before and it hasn't crashed yet.
So it looks good.
Thanks!
I'll just run this way for now.
I had installed Devian 12 and Firefox under it. I used their 102esr version of Firefox.
It seems the focus of the esr releases is different that what I was lead to believe when I
first encountered them using the rPi. Regardless, it still crashed.
This caused me to believe that this is a Firefox issue and I had started to go over to
using Chrome, which was working just fine. But, after entering troubleshooting mode,
I'm back using Firefox and we'll see how it goes. I'll have to find the
actual culprit at some point, but I have time and can get my business done for now.
Interestingly, Debian gave me a 1600x900 display that works very nicely for me, but is not
available through Fedora 38. This strikes me as really odd, since these options are
supposed to be driven off of what the hardware will support. It must be some X probing or
database weirdness, but it is too bad, since I'm back running fedora with the buttons
at the bottom slightly cut off LOL.
-Gary
\
On Tue, Jul 25, 2023 at 11:16:41PM -0700, Charles Polisher wrote:
On 7/25/23 13:40, Gary wrote:
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?
Firefox 102.13.0esr (64-bit) on Slackware Linux 15.0.
Stable as a rock. You didn't say what your "finance"
VM is running. Try posting contents of /etc/os-release
(or, /etc/redhat-release) and the output of
ldd /usr/lib64/firefox/firefox-bin.
$ cat /etc/os-release
NAME=Slackware
VERSION="15.0"
ID=slackware
VERSION_ID=15.0
PRETTY_NAME="Slackware 15.0 x86_64"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:slackware:slackware_linux:15.0"
HOME_URL="http://slackware.com/"
SUPPORT_URL="http://www.linuxquestions.org/questions/slackware-14/&quo…
BUG_REPORT_URL="http://www.linuxquestions.org/questions/slackware-14/&…
VERSION_CODENAME=stable
$ ldd /usr/lib64/firefox/firefox-bin
linux-vdso.so.1 (0x00007ffd5d32c000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1488e56000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f1488e51000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f1488c3d000)
libm.so.6 => /lib64/libm.so.6 (0x00007f1488af5000)
libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f1488ada000)
libc.so.6 => /lib64/libc.so.6 (0x00007f14888fb000)
/lib64/ld-linux-x86-64.so.2 (0x00007f1488f75000)
Doesn't Firefox have an elaborate crash reporting / bug
reporting system built in? Does it activate?
Any error messages? Have you tried enabling core dumps?
How about run it from the command line and look for output
to stderr?
_______________________________________________
Lug-nuts mailing list -- lug-nuts(a)bigbrie.com
To unsubscribe send an email to lug-nuts-leave(a)bigbrie.com