| Summary: | kmozillahelper don't work with Firefox ESR 60 (Quantum) anymore | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bertrand Marne <mageia> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | geiger.david68210, jan-bugs, lists.jjorge, marja11, ouaurelien, thierry.vignaud |
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Bertrand Marne
2018-10-04 18:23:48 CEST
Marja Van Waes
2018-10-06 09:48:05 CEST
Assignee:
bugsquad =>
kde For the record, this doesn't work for me on Cauldron either, with: - kmozillahelper-5.0.2-2.mga7.x86_64 - firefox-62.0.3-1.mga7.x86_64 The kmozillahelper binary is not launched when Firefox is launched, like it used to do back in the day. No idea how that's supposed to work. CC:
(none) =>
jan-bugs I have submitted latest version 5.0.2 to updates testing hoping it fixes this bug, so it seems it won't. Please test, and report upstream as it seems that have to adapt their code... RPM: kmozillahelper-5.0.2-2.mga6.i586.rpm SRPM: kmozillahelper-5.0.2-2.mga6.srpm CC:
(none) =>
lists.jjorge You were right v5.0.2 did not solve the issue. I reported upstream and the answer is available here: https://github.com/openSUSE/kmozillahelper/issues/21 Firefox needs to be patched as in https://www.rosenauer.org/hg/mozilla/file/tip/mozilla-kde.patch Specific patch for FF 60 (same as ESR?) is here: https://www.rosenauer.org/hg/mozilla/rev/bf0d08380dcf These 2 patches are needed on firefox: https://www.rosenauer.org/hg/mozilla/raw-file/tip/mozilla-kde.patch https://www.rosenauer.org/hg/mozilla/raw-file/tip/firefox-kde.patch CC:
(none) =>
geiger.david68210, thierry.vignaud Is this still valid in Cauldron? Mageia 7 only? CC:
(none) =>
ouaurelien Not reproduced on Cauldron (Mageia 8 B1) We will assume has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as FIXED. Resolution:
(none) =>
FIXED |