Package Details: firefox-beta-bin 70.0b7-1

Git Clone URL: https://aur.archlinux.org/firefox-beta-bin.git (read-only)
Package Base: firefox-beta-bin
Description: Standalone web browser from mozilla.org - Beta
Upstream URL: https://www.mozilla.org/en-US/firefox/channel/#beta
Keywords: gecko
Licenses: GPL, MPL, LGPL
Conflicts: firefox-beta
Provides: firefox=70.0b7
Submitter: Schnouki
Maintainer: symen
Last Packager: symen
Votes: 387
Popularity: 0.705166
First Submitted: 2010-07-07 09:05
Last Updated: 2019-09-16 21:56

Required by (217)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

Det commented on 2017-10-24 18:13

'xed in https://aur.archlinux.org/cgit/aur.git/commit/?h=firefox-beta-bin&id=ea7a85b8afd25c7f1273fdaa4b13f8ca8a25caa8

rccavalcanti commented on 2017-10-24 17:59

Hello there,

Using the launcher in KDE Plasma, the window class is set to "Firefox", instead of "Firefox Beta". Thus, it gets wrongly associated to Firefox in the task manager.

The StartWMClass line isn't taking care of it, and as far as I'm concerned, can be removed.

The issue can be fixed adding the --class argument to Exec, as in:
Exec=/opt/firefox-beta/firefox --class "Firefox Beta" %u
Exec=/opt/firefox-beta/firefox --class "Firefox Beta" --new-window %u
Exec=/opt/firefox-beta/firefox --class "Firefox Beta" --private-window %u

Or directly pointing to your wrapper:
Exec=firefox-beta %u
Exec=firefox-beta --new-window %u
Exec=firefox-beta --private-window %u

Edit: minor typo.

Det commented on 2017-10-10 16:38

> Your package firefox-beta-bin [1] has been flagged out-of-date by Atraii [2]:
>
> Firefox Beta 57.0b7 is released. Thanks for the awesome work!

You're welcome, you're welcome. ^^

symen commented on 2017-10-07 08:31

@DeathHacker
Again that's expected, you can't open the same profile simultaneously. If you want multiple instances running you must use a different profile for each of them.

@btd1337
Agreed, although another approach could be to replace the binary with a launch wrapper script that add the --class argument if not specified by the user. This is uglier than modifying the desktop script, but it has the advantage of also working when running firefox from the terminal (which is why I did it this way in my package).

btd1337 commented on 2017-10-07 04:57

Maintainer,

Please, change this lines in the .desktop file to fix duplicate icon error.

[Desktop Entry]
Exec=/opt/firefox-beta/firefox --class="firefox-beta" %u
StartupWMClass=firefox-beta

[Desktop Action new-window]
Exec=/opt/firefox-beta/firefox --new-window --class="firefox-beta" %u

[Desktop Action new-private-window]
Exec=/opt/firefox-beta/firefox --private-window --class="firefox-beta" %u



Det commented on 2017-10-06 18:48

Not just the .desktop, that's the install location.

sudoBash418 commented on 2017-10-06 17:48

@symen
You're right; I ran 'firefox-beta-bin --new-instance' and it opened Firefox Beta

However, when I tried the same while having firefox open, it complained that Firefox was already running and that it wasn't responding.

Another thing I noticed: the desktop file points to /opt/firefox-beta/firefox
It should point to /opt/firefox-beta-bin/firefox

symen commented on 2017-10-02 08:42

@DeathHacker and @luso58
You should be able to keep both browsers installed and run any of them.
However if you already have one instance of firefox running and you run the firefox (or firefox-beta) executable, the default behaviour is to open a new window of the instance currently running.

Did you make sure that firefox was completely closed when running firefox-beta (or vice-versa)?
You can force firefox to open a new instance with the "--new-instance" option.

By the way, you can have different versions running simultaneously by using different profiles. Use "-p" to open the profile manager, and "-p <profile-name>" to launch firefox with a specific profile.

sudoBash418 commented on 2017-10-01 19:57

So, I noticed some odd things about Firefox Beta when I installed it.
For example, the about page in both showed something like "Mozilla Firefox 55.<something> archlinux"
However, 'firefox -v' and 'firefox-beta -v' gave me 55.<something> and 57.0 respectively.

The original reason I wanted Beta was so I could use the new UI and WebExtensions.
Oddly enough, in both browsers the "legacy" extensions (which weren't supposed to work in 57) worked fine, and the interface looked identical.

So, for my sanity's sake, I closed Firefox completely, 'pacman -R firefox', and voila, opening firefox-beta gave me the new UI as well as breaking LastPass.

This should NOT have taken me this long to figure out!

luso58 commented on 2017-09-30 08:19

I have everything up to date and both extra/firefox and aur/firefox-beta-bin installed and both `firefox` and `firefox-beta` start firefox beta. I checked, and the firefox command starts the firefox binary of the stable firefox (55). Is this some known issue or am I doing something wrong?

Everything up to date as of the submit time of this comment, I use GNOME.