Nearly a year later, this is still an immediate problem. For people
finding this bug via Google, the only fix I've found that cares about
security is to use Debian GNU/Linux instead of Ubuntu and `apt install
firefox-esr`. This works because the stable (Stretch) version of Debian
uses Firefox-ESR
** Changed in: firefox (Ubuntu)
Assignee: Canonical Security Team (canonical-security) => Ubuntu Security
Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697800
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697800
Title:
Seth writes, "running a known-insecure webbrowser is probably a bad
idea."
Agreed. Except I would say "definitely".
It's important that Ubuntu gets some sort of a fix soon. I've already
seen a person asking on a forum how to downgrade and being told to
install a third party package by hand. This
By the way, since this problem is already causing Ubuntu LTS systems to
break, it may make sense to implement a quick stopgap solution. One
possibility is to change the version of Firefox in 16.04 to "firefox-
esr" (Extended Support Release). While this release will only be
supported by Mozilla
None of the upgrade tools are in a position to check architecture
features before installing a package. There may not be a happy solution
here.
Once you downgrade to a working version of Firefox you can use
sudo apt-mark hold firefox
to try to keep the updating tools from replacing it.
Note
It looks like this has been in the works for awhile and Mozilla had
intended for Firefox to detect SSE2 support in the installer and in the
automatic updates. Of course, Ubuntu is skipping both of those.
https://bugzilla.mozilla.org/show_bug.cgi?id=1308167
It's urgent that this gets fixed. The
You can trigger a crash immediately on a machine without SSE2 by
running firefox 54 like so:
firefox https://www.quirksmode.org/html5/videos/big_buck_bunny.mp4
(Note that it must be an mp4 video. VP8 and Vorbis still work fine.)
--
You received this bug notification because you are a
Spoke too soon. Firefox does still die of SIGILL, it just doesn't die
immediately. It is still choking on an SSE2 instruction, though, so
this is the same bug.
Thread 1 "firefox" received signal SIGILL, Illegal instruction.
0xb20eab29 in ?? () from /usr/lib/firefox/libxul.so
=>
I tried the version the version just released,
54.0+build3-0ubuntu0.16.04.1, and it appears Firefox is working again
on a machine without SSE2. Thank you!
I don't see anything in 'apt changelog firefox' describing what was
done to fix it, though. Was it recompiled with different flags?
This isn't
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Canonical Security Team (canonical-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697800
Title:
[regression] firefox dies
Looks like it would be intentional according to https://www.mozilla.org
/en-US/firefox/53.0/releasenotes/ :
"Ended Firefox Linux support for processors older than Pentium 4 and AMD
Opteron"
Also, for Windows, they require SSE2 since Firefox 49.
--
You received this bug notification because you
12 matches
Mail list logo
