Arch Linux User Repository

If you have issues with this package visit gitlab and read the readme first.

upstream git repo:* (https://gitlab.com/Thaodan/firefox-kde-opensuse)

repo in /etc/pacman.conf:

[home-thaodan]
Server = https://thaodan.de/public/archlinux/home-thaodan/x86_64/

import the key

sudo pacman-key --recv-keys BBFE2FD421597395E4FC8C8DF6C85FEE79D661A4
pacman-key --finger BBFE2FD421597395E4FC8C8DF6C85FEE79D661A4
sudo pacman-key --lsign-key  BBFE2FD421597395E4FC8C8DF6C85FEE79D661A4
sudo pacman-key --refresh-keys

fingerprint:

gpg: enabled debug flags: memstat
gpg: keydb: handles=1 locks=0 parse=0 get=1
gpg:        build=0 update=0 insert=0 delete=0
gpg:        reset=0 found=1 not=1 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=2 cached=2 good=2 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
           outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0
gpg: secmem usage: 0/32768 bytes in 0 blocks
pub   rsa2048 2015-02-13 [SC]
       BBFE 2FD4 2159 7395 E4FC  8C8D F6C8 5FEE 79D6 61A4
uid        [ ultimativ ] Björn Bidar <theodorstormgrade@gmail.com>
sub   rsa2048 2015-02-13 [E]

If you have issues with this package visit gitlab and read the readme first.

mozilla-common was removed since MOZ_PLUGIN_PATH is no longer used/supported.

@perfi: Why it has been removed?

pacman -Ql mozilla-common mozilla-common /etc/ mozilla-common /etc/profile.d/ mozilla-common /etc/profile.d/mozilla-common.csh mozilla-common /etc/profile.d/mozilla-common.sh

anyway all it does is setting one env var:

cat /etc/profile.d/mozilla-common.csh setenv MOZ_PLUGIN_PATH "/usr/lib/mozilla/plugins"

cat /etc/profile.d/mozilla-common.sh export MOZ_PLUGIN_PATH="/usr/lib/mozilla/plugins"

There's a mirror of package: https://eu.mirror.archlinuxarm.org/aarch64/extra/mozilla-common-1.4-6-any.pkg.tar.xz

mozilla-common has been removed from the official arch repos, so this won't build atm :(

The binary package in home-thaodan needs a rebuild, as icu as updated.

@gschwarz: you've inspired me to check it again and it's all f* as always

Under X11 Both plasma widgets "Window AppMenu" and "Global Menu" somehow worked. Sometimes one of segaulted with Konsole, while other worked with Firefox and sometiems one worked with Konsole, but other didn't show menu from Firefox. It was generally problematic.

Under Wayland both plasma built-in "Global Menu 2.0" and "Window Appmenu 0.6.0" works with Konsole, but any of them works with Firefox running as wayland native client (not default)

I haven't tested it, but on reddit somebody stated that firefox-appmenu works identically like firefox-kde-opensuse: https://www.reddit.com/r/kde/comments/h13s53/global_menu_when_using_plasma_wayland_kind_of/

Hey please ask for bigger questions like these on gitlab. It is hard to have conversation here. Short questions are ok but bigger issues are hard to follow.

It should work without MOZ_DBUS_REMOTE, for me it just works on X11. On Wayland howvever it does not work at all since it is unsupported/buggy (https://bugs.kde.org/show_bug.cgi?id=424485).

Using the KDE globalmenu applet works just fine for me. All implementations work over DBus and proxy the menu over their respective toolkit. Firefox needs patches that add linux support to the existing menubar also used on macOS.

@gschwarz: at leat we know it works in dolphin, but still now if you've tried doing it under X11 session(not wayland). If firefox's menu show in menu applet, then you can simply try magic sequence to make it responsive: https://www.reddit.com/r/kde/comments/8xox43/firefox_global_menu/

If id doesn't show at all in applet, they read info below

1. install appmenu-gtk-module (I also recommend installing appmenu-qt4 for Qt4 apps)

run 'MOZ_DBUS_REMOTE=1 firefox' and see if it helps on wayalnd and X11. New wayland-compatible appmenu implementation uses dbus and it was needed in the past

if you want to make it permament you can run: echo export MOZ_DBUS_REMOTE=1 >> ~/.bash_profile or sudo echo MOZ_DBUS_REMOTE=1 >> /etc/profile

Thanks for the reply. In fact global menus are my only motivation to look consider firefox-kde-opensuse. I am using KDE's built-in global menu support (via a panel at the top of the screen) and it works nicely with KDE apps as well as with e.g. vlc and Chromium. Did not install additional software to get a global menu.

@gschwarz: I've temporarily disabled global menu, because firefox with thousand o tabs became CPU hog(it worked under plasma few months ago), but:

• there are different Global Menu implementations (applets) and I remember that some were not working with firefox or not working at all.

• global menu haven't worked in the past under wayland, but there were some changes inside kde in recent released, I haven't tested.

Other thing is that Firefox and LibreOffice always got buggy implementations. Some time ago you needed to open global menu from firefox(it was in the panel, but unresponsive), switch to other virtual_workspace)/desktop, click on another app(without deselecting global menu, switch back and click on firefox window of gliobal menu(not sure, but you can google this procedure. But after doing it once, global menu worked until you've restarted firefox)

Generally Firefox always got buggy iplemetation and sometimes needed quirks to start working. Global Menu were always buggy, especially in the past were there were different approaches to achieve it, so applets needed dierent codebases for different ...hmmm...let's call it 'standards'. In the past (after some upgrades) some applets started working and soem got broken and sometimes were bringing whole plasma down (especially firefox). you can also try firefox-appmenu (it's in the chaotic-aur and archlinuxcn), it's more recent, but doesn't provide kde patches [but with gtk portal it lacks probably only activities and taskbar integration, but not sure about them])

Btw, write down applet you are using and if other apps (like dolphin/konsole) works with it, because problem may be related not to firefox, but to broken applet or badly written Qt plugins(all these chinese crapware like Deepin or UKUI installs them and causes sometiems not working global menu or segfaulting Qt apps under plasma(or viceversa) with some scaling factor(global envs) set] you can check it by running such applications and plasmashell from terminal and look over warning/errors qbout Qt plugins and find them latter by running: pacman -Qo /usr/lib/qt/plugins/*