bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.
Status
()
People
(Reporter: diazbastian, Unassigned)
Tracking
(Depends on: 5 bugs, {meta})
Firefox Tracking Flags
(Not tracked)
Details
(URL)
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID: 20160512103250 Actual results: Firefox updates depend on each Linux distribution maintainers, which makes its slow deployment. Considering the importance of security updates in a web browser, this system is inefficient. Moreover, the classic tarballs are unfriendly to the end user. In the Mozilla blog, announced to use Snap to distribute Firefox on Ubuntu https://blog.mozilla.org/futurereleases/2016/04/21/firefox-default-browser-for-linux-users-ubuntu-new-snap-format-coming-soon/ Snap is package format with good intentions and has good features like sandboxing or direct update from the author, however, is a niche technology and is very hard to use a Snap application outside Ubuntu, even in previous Ubuntu versions or other Debian based systems. Expected results: It would be great to distribute Firefos as a Flatpak package (aka xdg-app) for Linux users. Flatpak (http://flatpak.org/) is a nice framework to distribute applications on Linux standalone, safely and independently of the linux distro. The Document Foundation, distribute LibreOffice as a flatpak package (https://www.libreoffice.org/download/flatpak/). Flatpak is still in active development, but it is very promising features. Currently you can use Flatpak in several distributions very easily, including Ubuntu. In addition existing graphical tools that support easy installation Flatpak applications.
| (Reporter) | ||
Updated•2 years ago
|
||
Severity: normal → enhancement
Comment 1•2 years ago
|
||
Considering the fact that this is an enhancement, I will assigned a component to this issue in order to involve the development team and get an opinion on this.
Component: Untriaged → Build Config
Updated•2 years ago
|
||
See Also: → bug 1251407
| (Reporter) | ||
Comment 2•2 years ago
|
||
(In reply to Cosmin Muntean [:CosminMCG] from comment #1) > Considering the fact that this is an enhancement, I will assigned a > component to this issue in order to involve the development team and get an > opinion on this. Thank you very much
Comment 3•2 years ago
|
||
I've created a PoC of the manifest at https://github.com/vrutkovs/firefox-flatpak
Comment 4•2 years ago
|
||
Given that Snap is now universal to Linux, is this still the correct approach?
Comment 5•2 years ago
|
||
(In reply to Paul [pwd] from comment #4) > Given that Snap is now universal to Linux, is this still the correct > approach? I don't think you're right. Snap is still Ubuntu only but flatpack is distro independent. See https://www.reddit.com/r/linux/comments/4kxbqp/appimage_snaps_flatpak_pros_and_cons_comparison/d3j3vv4 for details.
Comment 6•2 years ago
|
||
See http://lwn.net/Articles/691309/ That doesn't change there's no indication which one will win on the long run.
Comment 7•2 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #6) > See http://lwn.net/Articles/691309/ > > That doesn't change there's no indication which one will win on the long run. Sure. My point is that Snap is Ubuntu only now and other distros needs to use something else. OTOH flatpack can be distributed on all distros include Ubuntu.
Comment 8•2 years ago
|
||
The point is Snap *is* going to be available on all the major distros, according to that lwn article.
Updated•2 years ago
|
||
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Unspecified → Linux
Hardware: Unspecified → All
Version: 46 Branch → Trunk
Comment 9•2 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #8) > The point is Snap *is* going to be available on all the major distros, > according to that lwn article. I'm not aware of any effort to get Snapy on Fedora by default (but it's possible to install it from third-party repo) and I don't expect Fedora will adopt that. AFAIK there's one big problem here - you can't create third party Snapy repo which is independent on Canonical - all Snappy packages has to be distributed from there. Correct me if I'm wrong.
Comment 10•2 years ago
|
||
(In reply to Martin Stránský from comment #9) > (In reply to Mike Hommey [:glandium] from comment #8) > > The point is Snap *is* going to be available on all the major distros, > > according to that lwn article. > > I'm not aware of any effort to get Snapy on Fedora by default (but it's > possible to install it from third-party repo) and I don't expect Fedora will > adopt that. > > AFAIK there's one big problem here - you can't create third party Snapy repo > which is independent on Canonical - all Snappy packages has to be > distributed from there. Correct me if I'm wrong. It's worth noting that all of the news today states that Fedora will support snaps natively http://snapcraft.io/ http://arstechnica.com/information-technology/2016/06/goodbye-apt-and-yum-ubuntus-snap-apps-are-coming-to-distros-everywhere/ http://betanews.com/2016/06/14/ubuntu-snap-packages-linux-distros-fedora-arch-mint-opensuse/ https://insights.ubuntu.com/2016/06/14/universal-snap-packages-launch-on-multiple-linux-distros/
Comment 11•2 years ago
|
||
(In reply to Paul [pwd] from comment #10) [...] > It's worth noting that all of the news today states that Fedora will support > snaps natively > http://snapcraft.io/ > http://arstechnica.com/information-technology/2016/06/goodbye-apt-and-yum- > ubuntus-snap-apps-are-coming-to-distros-everywhere/ > http://betanews.com/2016/06/14/ubuntu-snap-packages-linux-distros-fedora- > arch-mint-opensuse/ > https://insights.ubuntu.com/2016/06/14/universal-snap-packages-launch-on- > multiple-linux-distros/ That articles comes from Ubuntu folks and are more wish than reality.
| (Reporter) | ||
Comment 12•2 years ago
|
||
(In reply to Paul [pwd] from comment #10) > (In reply to Martin Stránský from comment #9) > > (In reply to Mike Hommey [:glandium] from comment #8) > > > The point is Snap *is* going to be available on all the major distros, > > > according to that lwn article. > > > > I'm not aware of any effort to get Snapy on Fedora by default (but it's > > possible to install it from third-party repo) and I don't expect Fedora will > > adopt that. > > > > AFAIK there's one big problem here - you can't create third party Snapy repo > > which is independent on Canonical - all Snappy packages has to be > > distributed from there. Correct me if I'm wrong. > > It's worth noting that all of the news today states that Fedora will support > snaps natively > http://snapcraft.io/ > http://arstechnica.com/information-technology/2016/06/goodbye-apt-and-yum- > ubuntus-snap-apps-are-coming-to-distros-everywhere/ > http://betanews.com/2016/06/14/ubuntu-snap-packages-linux-distros-fedora- > arch-mint-opensuse/ > https://insights.ubuntu.com/2016/06/14/universal-snap-packages-launch-on- > multiple-linux-distros/ I think Canonical is using the power of marketing, because use a Copr repository created by an employee of Canonical is far from being a work with the community and provide snap natively. You may find Flatpak in the official repositories of Arch and not in a AUR repository as Snap (Copr and AUR are repositories that can be created by any user and are not safe per se).
| (Reporter) | ||
Comment 13•2 years ago
|
||
(In reply to Martin Stránský from comment #9) > (In reply to Mike Hommey [:glandium] from comment #8) > > The point is Snap *is* going to be available on all the major distros, > > according to that lwn article. > > I'm not aware of any effort to get Snapy on Fedora by default (but it's > possible to install it from third-party repo) and I don't expect Fedora will > adopt that. > > AFAIK there's one big problem here - you can't create third party Snapy repo > which is independent on Canonical - all Snappy packages has to be > distributed from there. Correct me if I'm wrong. What you mentioned is correct. It's a big problem because Canonical wants to create a centralized repository and distribute applications in their store, therefore, rather than creating an application distribution system for Linux, means something like "You can install Ubuntu applications on any distribution" and maintain the control of then. The operation will be similar to the Google Play Store, so all Snap with external repositories, they will be marked as unsafe by default. I think that's not the agnostic distribution system is expected. I prefer to download an application directly from the author's website and this without intermediaries (Canonical servers) can make any upstrean changes. Besides the size of the Snap packages they are crazy and as such can compare and unofficial Snap package (~1GB) and official Flatpak package (~160MB) of LibreOffice. As an additional note, the Flatpak runtimes are additional weight, but can be used by multiple applications.
Updated•2 years ago
|
||
See Also: → bug 1290670
Comment 14•a year ago
|
||
Also Flatpak seems more secure. They give access to the app only when needed. If a crazy user wants to open ~/.ssh in Firefox, the user will press Ctrl+O, Firefox will ask GTK to open the file, the user will browse and select the file, then GTK will offer the file as a bind mount to Firefox. If an evil addon wants to do the same, it cannot. It needs user interaction for this. Basically the GTK file open/file save dialog guards the user's file system. I really like Flatpak's security model more than any other GNU/Linux way of distributing binaries.
Comment 15•a year ago
|
||
FIY we've setup experimental unofficial Firefox Developer Edition flatpak repository there: https://firefox-flatpak.mojefedora.cz/ with some installation instructions. There are build scripts available on github: https://github.com/xhorak/firefox-devedition-flatpak Currently our package grants access to whole filesystem as long as it is experimental stuff.
Comment 16•a year ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1332404 - may be needed for bringing plugins for flatpaked Firefox
Comment 17•6 months ago
|
||
I think https://kamikazow.wordpress.com/2017/02/09/adoption-of-flatpak-vs-snap/ is worth looking. I hope to see this bug fixed, especially thinking about developer edition
Comment 18•6 months ago
|
||
Has anyone from Mozilla commented on whether this could be worked on or what is stopping them? Would be great to have the same stable / beta / nightly channels available on linux as other platforms through flatpak
Updated•5 months ago
|
||
Flags: needinfo?(mh+mozilla)
Updated•5 months ago
|
||
Flags: needinfo?(mh+mozilla) → needinfo?(catlee)
Comment 19•5 months ago
|
||
Unfortunately we're not going to be able to get to this in Q4.
Flags: needinfo?(catlee)
Comment 20•5 months ago
|
||
This is something that we have looked at (you can see by the dependent bugs), but we haven't got enough traction internally to decide exactly what the next steps are. Based on my understanding of things, we need some Firefox specific patches in order to support special app paths inside the Flatpak and that would require a Flatpak unique build of Firefox. I'd like to know if there is anything we can do to use a standard Firefox in a Flatpak or if we have to have the build changes referenced in the other bugs? I honestly don't know enough about how Flatpaks work. This is definitely something we would look to a community member to help drive.
Comment 21•5 months ago
|
||
The fedora people are shipping flatpaks of an experimental (aiui) wayland-enabled firefox, surely they can say what's needed.
Flags: needinfo?(jhorak)
Comment 22•5 months ago
|
||
Fedora provides flatpak Firefox at https://firefox-flatpak.mojefedora.cz/ for: FirefoxNightly - Firefox Nighly FirefoxDevEdition - Firefox Developer Edition FirefoxNightlyWayland - experimental Wayland port FirefoxNightlyCSD - experimental CSD port There's also official flatpak "Store" at https://flathub.org/ with registered flatpaked apps. We (Fedora folks) can surely pack and distribute Firefox at official flatpak store but we feel it would be better if the packages will be under direct Mozilla control. We're keen to help with any technical issues, provide the flatpak file etc.
Comment 23•5 months ago
|
||
What are the actual code changes to Firefox needed to make a Flatpak work?
Comment 24•5 months ago
|
||
AFAIK No code changes. See the scripts used by Fedora to build flatpak from various Mozilla releases: https://github.com/xhorak/firefox-devedition-flatpak 1) You can flatpak existing Mozilla nightly binary builds by: https://github.com/xhorak/firefox-devedition-flatpak/tree/master/org.mozilla.FirefoxUpstreamBinary 2) or do the whole build: https://github.com/xhorak/firefox-devedition-flatpak/tree/master/org.mozilla.FirefoxNightly I think the easiest start is to just place existing Nightly binary generated by Mozilla to flatpak shell. The examples at (1) may be outdated as we don't use that now but if you're interested we can surely update them for production use.
| Comment hidden (advocacy) |
Comment 26•5 months ago
|
||
I'm going to fill some bugs what is not working ATM.
| Comment hidden (offtopic) |
| Comment hidden (offtopic) |
Updated•2 months ago
|
||
Alias: flatpak
Keywords: meta
Updated•2 months ago
|
||
Comment 29•2 months ago
|
||
I am no expert with flatpa but on Debian, the following worked for me: sudo apt-get install flatpak sudo flatpak install --from https://firefox-flatpak.mojefedora.cz/org.mozilla.FirefoxNightly.flatpakref flatpak run org.mozilla.FirefoxNightly
Comment 30•2 months ago
|
||
I've a working sample: https://gitlab.com/stevendobay/flatpak-plus/tree/master/org.mozilla.Firefox It only works for x86_64 but everything seems to work with it(I'm using it for 2 days). It only gets permission to open $XDG_DOWNLOADS.
You need to log in
before you can comment on or make changes to this bug.
Description
•