Sounds like maybe this is actually resolved?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263014
Title:
fails to run when built with FORTIFY_SOURCE
To manage notifications about this bug go to:
*** Bug 1680439 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835024
Title:
firefox fails to use the default profile from classic snaps
To manage
I vaguely recall some plan to distribute devedition as a separate snap
at some point which this would break but it looks like that hasn't
happened so this is fine. I really wish there was a sane API to detect
this though, environment variable detection always seemed likely to be
flakey.
--
You
I think this falls under a coding error. When implementing the sync
localization support in bug 1509609 the API chosen to load the flt file
did not support language packs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I filed bug 1588550 on getting the URLPreloader to support language
packs properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846371
Title:
firefox 70.0 beta 11 isn't fully translated
To
Comment on attachment 9099938
Bug 1586216: Fallback to a synchronous channel load if the url preloader cannot
load the ftl file. r=kmag
### Beta/Release Uplift Approval Request
* **User impact if declined**: Users with langpacks will see parts of the UI
not translated into their preferred
Figured this out. Having some unrelated build issues right now but
should have a patch up tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846371
Title:
firefox 70.0 beta 11 isn't fully
Created attachment 9099938
Bug 1586216: Fallback to a synchronous channel load if the url preloader cannot
load the ftl file. r=kmag
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846371
Title:
(In reply to Axel Hecht [:Pike] from comment #22)
> Ah, another one of those. Is this also gonna fix bug 1557713 ?
Looks like it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846371
Title:
So the main problem here is that as things stand synchronously loading
ftl files from langpacks fail. Synchronous loads use
[`Cu.readUTF8URI`](https://searchfox.org/mozilla-
central/rev/05a22d864814cb1e4352faa4004e1f975c7d2eb9/intl/l10n/L10nRegistry.jsm#754)
which underneath uses the
That said ... we don't flush the startup cache when the locales change,
but we do flush the xul prototype cache: https://searchfox.org/mozilla-
central/source/chrome/nsChromeRegistryChrome.cpp#201 which means
whatever this is caching is not getting flushed (thought -purgecaches
would flush it so
(In reply to Zibi Braniecki [:zbraniecki][:gandalf] from comment #7)
> Mossop - I remember you saying that we do purge XUL cache on language change,
> I think this bug indicates that we don't? Or is there something else in play?
If starting with -purgecaches isn't helping then I don't think the
(In reply to Olivier Tilloy from comment #17)
> Dave, I have submitted https://phabricator.services.mozilla.com/D37722 for
> review, I hope you and other build config experts can comment.
>
> I have tested this with Ubuntu packages, setting the build ID to e.g.
> "build3". Your suggestion of
*** Bug 1555986 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830096
Title:
Firefox 67 in Ubuntu 18.10 thinks it's an older version
To manage
*** Bug 1557014 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830096
Title:
Firefox 67 in Ubuntu 18.10 thinks it's an older version
To manage
Based on this needing an ubuntu change at this point I'm going to close
this out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830096
Title:
Firefox 67 in Ubuntu 18.10 thinks it's an older
Ok so it looks like bug 1554029 has landed and stuck and will be rolling
out in a 67.0.1 soon. During testing of that I found that the suggestion
I made in comment 6 would have actually only worked on some platforms
due to a bug in the version comparator code. It probably would have
worked on
(In reply to Olivier Tilloy from comment #3)
> It seems unfortunate that firefox uses MOZ_BUILD_DATE as its build ID (if I
> followed correctly the code path, see
> https://hg.mozilla.org/mozilla-central/file/tip/build/variables.py#l15).
My apologies, I hadn't noticed that this was the case.
>
(In reply to Olivier Tilloy from comment #8)
> I am testing this suggestion, and it appears to work as expected.
Ok, so the patch looks ok to me, though it would really need a build
config peer to look at it. But we've discovered another issue related to
how we compare the compatibility versions
The startup method is called early in startup, before chrome for non-
restartless add-ons is registered. That is the problem here.
There are really only two solutions. One is to move the startup call to
later in startup, the other is to have JSONovich fixed so it doesn't
initialize nsHttpHandler
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #75)
(In reply to a_geek from comment #73)
They are not visible in the addons manager. I've reinstalled most of them in
the meantime because I needed them, but they were present in the
addons.sqlite file. For those that I
I don't see it explicitly called out, did we also verify the steps in
comment 48? I want to be sure we've fixing the problem for people that
already saw it as well as for new updaters
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(In reply to David McNamara [:mackers] from comment #14)
(In reply to Brian King (Briks) [:kinger] from comment #11)
David, could you post the code you tried. Maybe there is a minor error or
oversight.
In essence the code is the following:
(In reply to David McNamara [:mackers] from comment #3)
r94029 has a potential fix for this.
When ACR detects that a major application upgrade has occurred, it will
*uninstall* all locales, and then restart the browser. This will mean that
Firefox can at least start with a working UI.
For
Yeah, disabling the locale packs is the only thing I can think of, maybe
if you do that early enough in startup it'll work, not sure though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/677815
25 matches
Mail list logo
