From: blinux-list at redhat.com (Linux for blind general discussion)
Subject: F 105 crashing, anyone else?
Date: Fri, 23 Sep 2022 17:03:16 +0300 [thread overview]
Message-ID: <mailman.2740.1663941829.6082.blinux-list@redhat.com> (raw)
In-Reply-To: <mailman.2704.1663934841.6082.blinux-list@redhat.com>
on Arch Linux we applied patch from this bug report[1]
for other distributions ff 105.1 with this fix should be released today
or tomorrow
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1786638
On Fri, Sep 23, 2022 at 12:00:15PM +0000, Linux for blind general discussion wrote:
> To me, it seems more like the tendency to crash varies.
>
> Sometimes, I can activate the save link on a page few times in a row,
> and the browser crashes every time.
>
> And sometimes, the same link causes no trouble, and the whole browsing
> is a continuous experience.
>
>
> Best regards
>
>
> Rastislav
>
>
> D?a 23. 9. 2022 o 12:27 Linux for blind general discussion nap?sal(a):
> > Not sure how or why, but it apparently fixed itself and I didn't spy a
> > FF update in pacman's list of things it updated, though I'm still trying
> > to work out why it crashed so much to begin with
> >
> >
> >
> > On 9/21/22 22:12, Linux for blind general discussion wrote:
> >> Yes, Ubuntu Mate 22.04 64-bit, Firefox 105 from Mozilla ppa.
> >>
> >> I used 104 before and don't remember it crashing on my system, but 105
> >> crashes quite frequently.
> >>
> >>
> >> Either after activating a link, when the new page is loaded, or even
> >> on-page navigation can cause crashes here and there.
> >>
> >>
> >> Best regards
> >>
> >>
> >> Rastislav
> >>
> >>
> >> D?a 21. 9. 2022 o 13:35 Linux for blind general discussion nap?sal(a):
> >>> Is it just me, or is FF 105.0 crashing more than 104.X used to?
> >>>
> >>>
> >>> Open a private window and type in a URL, crash
> >>>
> >>>
> >>> Try going to a URL in the main window? Crash
> >>>
> >>>
> >>> Currently compiling FF ESR to see if this fixes it. The only things in
> >>> the crash log are sigseg and sig faults which are not helpful, the
> >>> console only gives me a channel error to work with
> >>>
> >>> _______________________________________________
> >>> Blinux-list mailing list
> >>> Blinux-list at redhat.com
> >>> https://listman.redhat.com/mailman/listinfo/blinux-list
> >>>
> >> _______________________________________________
> >> Blinux-list mailing list
> >> Blinux-list at redhat.com
> >> https://listman.redhat.com/mailman/listinfo/blinux-list
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list at redhat.com
> > https://listman.redhat.com/mailman/listinfo/blinux-list
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
--
Sincerely, Alexander
prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
blinux-list
` blinux-list
` blinux-list
` blinux-list
` blinux-list [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.2740.1663941829.6082.blinux-list@redhat.com \
--to=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).