On Sun, 2024-06-30 at 18:17 -0700, Samuel Sieb wrote:
> On 6/30/24 2:41 PM, Roger Heflin wrote:
> > For me when an update happens for firefox (not sure if it is a
> > firefox
> > update or just some libraries it uses, or both) it does not crash
> > (that I notice) but simply stops working (web page
On 6/30/24 2:41 PM, Roger Heflin wrote:
For me when an update happens for firefox (not sure if it is a firefox
update or just some libraries it uses, or both) it does not crash
(that I notice) but simply stops working (web page refresh and other
things don't work anymore).
You shouldn't update
Once upon a time, Roger Heflin said:
> So maybe something similar (update breakage) is happening for chromium also.
No, it's not an update vs. existing profile issue, since it happens in
mock.
I notice that when it happens, I get SELinux denials (which don't happen
when it runs okay) for exechea
For me when an update happens for firefox (not sure if it is a firefox
update or just some libraries it uses, or both) it does not crash
(that I notice) but simply stops working (web page refresh and other
things don't work anymore).
So in the firefox case something extreme enough is happening tha
Once upon a time, Jeffrey Walton said:
> On Sun, Jun 30, 2024 at 12:52 PM Chris Adams wrote:
> > After some recent updates, I seem to get an illegal instruction the
> > first time or two I start Chrome/Chromium after boot. If I close it and
> > reopen it a time or two, it'll work like normal fro
Once upon a time, Tom Horsley said:
> On Sun, 30 Jun 2024 11:52:06 -0500
> Chris Adams wrote:
> > Not sure if this is a problem with Chrome/Chromium, some library
> > dependency, or even the kernel.
>
> Don't discount memory or disk problems either, though int3 seems like
> something deliberate (
On Sun, Jun 30, 2024 at 12:52 PM Chris Adams wrote:
>
> After some recent updates, I seem to get an illegal instruction the
> first time or two I start Chrome/Chromium after boot. If I close it and
> reopen it a time or two, it'll work like normal from that point on,
> until I reboot again. It's
On Sun, 30 Jun 2024 11:52:06 -0500
Chris Adams wrote:
> Not sure if this is a problem with Chrome/Chromium, some library
> dependency, or even the kernel.
Don't discount memory or disk problems either, though int3 seems like
something deliberate (usually used as a breakpoint by debuggers).
--
__
After some recent updates, I seem to get an illegal instruction the
first time or two I start Chrome/Chromium after boot. If I close it and
reopen it a time or two, it'll work like normal from that point on,
until I reboot again. It's the weirdest thing, I can't think of
anything I've ever seen a
