Ask Ubuntu is a question and answer site for Ubuntu users and developers. It only takes a minute to sign up. This seems to be going to be default in next Fedora, so it should be stable enought.
I'd rather avoid yet another package manager on my system, so apt or snap would be prefered to flatpack Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top. Home Questions Tags Users Unanswered. Asked 1 year, 1 month ago.
Active 1 year, 1 month ago. Viewed 1k times. Any pointer will be appreciated. Thanks, Franck. Soon, maybe. Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.
The Overflow Blog. Featured on Meta. Feedback on Q2 Community Roadmap.
Subscribe to RSS
My first approach was just installing the firefox package using pacman. And the applications starts fine but with font rendering issues. The font is very blurry I tried several ttf fonts and sizes but it seems to be a general rendering problem.
After some research I found the AUR package firefox-wayland and installed that instead. I took a very long time to compile almost 1. However now the performace is really really bad! Scrolling is very slow and stuttery, mouseover effects of hyperlinks have a delay of seconds and so on.
Practically it's unuseable. I tried setting several environtment variables I found during my research. This is what I have set right now:. After all I tried using chromium instead which does not start at all: "Gtk-Warning: cannot open display: :1".
But I guess that's a different story. I would be very glad about some hints how to fix at least my Firefox issues. This is bugging me for hours now. Which version of sway are you using? The version in the repos is old and no longer supported. Instead, you should install the betas from the AUR sway-git, wlroots-git. For what it's worth, I'm running the beta version and the regular firefox works fine for me. I forgot to mention it but I'm using sway-git and wlroots-git.
Do you have some Wayland specific environment variables set? And do you use HiDPI scaling? Maybe I then should give the regular Firefox another shot and experiment with the settings. I have no Wayland environment variables set. Even though the buttons and whatnot are very small, the text is nice and clear on my monitor, and firefox actually works better under sway than it does under X.
I'd say to try the regular firefox without the environment variables and see if you can just adjust the text zoom to get something working. Unfortunately even though Sway allows you to set a scaling factor, I have seen some issues on their bugtracker saying that the scaling doesn't always work properly with all programs.Red Hat Associate. Red Hat Customer. Browse Requests Reports Product Dashboard.
Version-Release number of selected component if applicable : Run a Gnome Wayland session. On a virtual terminal, run weston using drm-backend. Run firefox-wayland from there 5. Switch to the Gnome display; the firefox window will have been opened there.
Actual results: Firefox window opens on wayland-0 display. Expected results: Firefox window should open on wayland-1 display. Not sure why weston does not work. Logged in from gdm 2. Switched to a virtual terminal Ctrl-Alt-F3 3. On the virtual terminal run weston-launch 4.
Its value is 'wayland-1' also for me, but firefox-wayland appears to ignore it and to use 'wayland-0' instead. Are you sure that you used firefox-wayland and not firefox X11 under Xwayland? I do not know about mutter, so it may be a good idea to try to replicate my test case exactly by creating the very setup I described. As I said, I do not know about mutter.Firefox on Linux have suffered by poor WebGL performance for long, long time.
It was given by missing general acceleration on Linux as there are always broken gfx drivers on X11, various hacks and different standards, closed source drivers and so on. Fortunately situation was changed with Wayland.
Wayland (display server protocol)
Working gfx acceleration is a sort of prerequisite to even start a decent Wayland compositor like Mutter or Plasma so when Firefox is launched on Wayland we can pretty much expect working GL environment.
Also dmabuf is widely supported by Wayland compositor so we finally have all pieces together to build fully accelerated browser on Linux which is equal to its Windows siblings. Firefox supports two acceleration modes — WebRender and GL compositor.
All those pieces are tied together in recent nightly where we finally have full WebGL support on Wayland and it will be shipped as Firefox Just grab latest nightly from Mozilla, enable HW accelerationset widget. Like Like. You also need to enable GL compositor by layers. Like Liked by 1 person. Hardware is not an issue. Wayland itself have no requirement on hardware, on other side, compositors implementing Wayland rely on OpenGL by their choice.
Like Liked by 2 people. Just gnome developers are integrating Wayland. The other ones stuck on legacy X Ehm… Is it really true? Regarding fglrx, it has been discontinued and died in preference of Mesa. Thanks for the great work! One question: I assume FF 75 will get the features, but not the defaults? Where is this log located. Firefox It seems in pretty good shape now to me. Sometimes even firefox itself crashes. Still, i want to thank you for your excellent work!
It means a lot to us all Linux users! Thanks for your report, please test latest nightly. Firefox 75 is missing some important dmabuf fixes which needs to be backported by distros. I tested the latest nightly Seems dmabuf-vaapi and dmabuf-webgl can be enabled now for me without crashing, though dmabuf-textures still crash every tab almost instantly if enabled.
How can i be sure? By the way when dmabuf-textures is enabled and tabs insta-crush i am getting similar failed to load messages plus i am getting a ton of these:.Wayland is a communication protocol that specifies the communication between a display server and its clients, as well as a C library implementation of that protocol. As part of its efforts, the Wayland project also develops a reference implementation of a Wayland compositor called Weston.
Starting aroundLinux desktop graphics has moved from having "a pile of rendering interfaces This will be "a much-simplified graphics system offering more flexibility and better performance". For many things we've been able to keep the X.
With Wayland we can move the X server and all its legacy technology to an optional code path. Wayland consists of a protocol and a reference implementation named Weston. Most applications are expected to gain support for Wayland through one of these libraries without modification to the application.
Wayland protocol follows a client—server model in which clients are the graphical applications requesting the display of pixel buffers on the screen, and the server compositor is the service provider controlling the display of these buffers. The Wayland reference implementation has been designed as a two-layer protocol: .
While the low-level layer was written manually in Cthe high-level layer is automatically generated from a description of the elements of the protocol stored in XML format. The reference implementation of Wayland protocol is split in two libraries : a library to be used by Wayland clients called libwayland-client and a library to be used by Wayland compositors called libwayland-server.
The Wayland protocol is described as an "asynchronous object-oriented protocol". Each object implements an interface which has a name, a number of methods called requests as well as several associated events. Every request and event has zero or more arguments, each one with a name and a data type. The protocol is asynchronous in the sense that requests do not have to wait for synchronized replies or ACKsavoiding round-trip delay time and achieving improved performance.
The Wayland clients can make a request a method invocation on some object if the object's interface supports that request. The client must also supply the required data for the arguments of such request.
This is the way the clients request services from the compositor. The compositor in turn sends information back to the client by causing the object to emit events probably with arguments too. These events can be emitted by the compositor as a response to a certain request, or asynchronously, subject to the occurrence of internal events such as one from an input device or state changes.
The error conditions are also signaled as events by the compositor. For a client to be able to make a request to an object, it first needs to tell the server the ID number it will use to identify that object. Global objects are advertised by the compositor to the clients when they are created and also when they are destroyedwhile non-global objects are usually created by other objects that already exist as part of their functionality.
The interfaces and their requests and events are the core elements that define the Wayland protocol. Each version of the protocol includes a set of interfaces, along with their requests and events, which are expected to be in any Wayland compositor.
Optionally, a Wayland compositor may define and implement its own interfaces that support new requests and events, thereby extending functionality beyond the core protocol. Each Wayland compositor exposes not only what interfaces are available, but also the supported versions of those interfaces. This set of interfaces is the minimum required to be implemented by any Wayland compositor. Some of the most basic interfaces of the Wayland protocol are:  : This is a special local object that represents the connection and does not live within the server.
A Wayland compositor can define and export its own additional interfaces. Certain compositors can choose to add custom interfaces to provide specialized or unique features.
XDG-Shell protocol see freedesktop. The traditional way to manipulate maximize, minimize, fullscreen, etc. An implementation of the xdg-shell protocol, on the contrary, is supposed to be provided by the Wayland compositor.
So you will find the xdg-shell-client-protocol. Each Wayland compositor is supposed to provide its own implementation. It starts as a non-stable API, aimed to be used as a development place at first, and once features are defined as required by several desktop shells, it can be finally made stable.Command line options are used to specify various startup options for Mozilla applications.
For example, if you have multiple profiles you can use command line configuration options to bypass the Profile Manager and open a specific profile. You can also control how Mozilla applications open, which components open initially, and what the components do when they open. This page describes the commonly used options and how to use them.
If the option contains arguments, enter the argument after the option.Mozilla Firefox Hangs Or Is Not Responding FIX
Multiple command line options can be specified. In general, the syntax is as follows:. The following examples show the use of the "-ProfileManager" command, which will open the profile manager prior to starting Firefox or Thunderbird:. The example above invokes the "-ProfileManager" command line option with Mozilla's Thunderbird mail client. Depending on changes between the two versions, some files in a profile may not be downwards compatible. Adding this option bypasses downgrade protection.
Create a new profile in the default directory, but do not start the application.
Command line options
You can use the - no - remote option to avoid connecting to a running instance. Open new instance, not a new window in running instance, which allows multiple copies of application to be open at a time. Note: Since Firefox 9, this does really mean what its name implies on all platforms, i.
That means that such instances won't be re-used. Also when using this argument a new instance is created in any case. Load the specified override. This can be used to suppress the migration wizard at startup by loading the following override. Firefox only. Useful for dealing with multiple profiles. If you don't specify a profile name then the profile manager is opened instead. You must use an upper case P on Linux with versions older than 7. Other platforms accept both upper and lower case.
Start with the profile with the given path. FirefoxThunderbird and SeaMonkey2. Runs Firefox in headless modewhich is very useful for purposes such as debugging and automated testing. Open URL in a new tab. Firefox and SeaMonkey2. Open URL in a new window. May not be applicable in older Ubuntu for Firefox 20 and later, confirmed to work in Opens a new private browsing window in an existing instance of Firefox.
Popup window sometimes grayed out when clicking repeatedly and rapidly. Add an attachment proposed patch, testcase, etc.
This will not work on non-X backends. Anyway, firefox in broadway is not necessarily very important, but it is a good preparation for generic multi-backend handling, which will be required for wayland support later. Fedora has stopped maintaining and issuing updates for Fedora It is Fedora's policy to close all bug reports from releases that are no longer maintained.
Approximately 4 four weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events.
Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Any idea here? Comment 6 Jaroslav Reznik UTC This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'. Because I can open only X display by such way. Comment 10 Martin Stransky UTC Looks like there's a problem with some signals connected to the window. I see some bugs new windows painted behind the main application for instance which works on broadway backend. Actually Firefox works very well on broadway backend now with some extra patches of courseso can I take the broadway backend a reference and expect Wayland will be fixed for it?