Hi, Description of problem: Since the update of FF to v 60, kmozillahelper seems to have stopped working : the file select dialog is back to default GTK one (not Plasma one anymore). Version-Release number of selected component (if applicable): - kmozillahelper v 0.6.5 - Firefox v 60.2.1 How reproducible: Every time. Steps to Reproduce: 0- user Plasma 1- Install both packages 2- Open Firefox 4- Try to save as any webpage : the file selector is the GTK one and not the plasma one
Assignee: bugsquad => kdeCC: (none) => marja11
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) => FIXEDStatus: NEW => RESOLVED