Announcement

Collapse
No announcement yet.

Fedora Users Now Have An Experimental Firefox Wayland Package

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • JohnGalt
    replied
    Originally posted by Luke View Post

    What GTK3 version are you testing? This sounds a bit like its related to a bug in gtk 3.21.3 that was patched in master a couple days ater release. GTK devs radically changed the drawing system-and FIrefox would turn black on change of focus, updating only when each widget was moused over. I saw this in both X11 and with Xwayland with released FF47.
    That's probably the issue. I'm on the GNOME Next repo (3.21.3), and it built using system packages through rpmbuild. I'm working on getting a successful OBS build with the wayland patches and spec changes, but not quite there yet. Currently stuck at a linking error:
    Code:
     
     [ 4083s] ../../xpcom/base/Unified_cpp_xpcom_base1.o: In function `nsSystemInfo::Init()':  [ 4083s] /home/abuild/rpmbuild/BUILD/mozilla/xpcom/base/nsSystemInfo.cpp:692: undefined reference to `gtk_read_end_of_the_pipe'  [ 4083s] /usr/lib64/gcc/x86_64-suse-linux/6/../../../../x86_64-suse-linux/bin/ld: ../../xpcom/base/Unified_cpp_xpcom_base1.o: relocation R_X86_64_PC32 against undefined hidden symbol `gtk_read_end_of_the_pipe' can not be used when making a shared object  [ 4083s] /usr/lib64/gcc/x86_64-suse-linux/6/../../../../x86_64-suse-linux/bin/ld: final link failed: Bad value

    Leave a comment:


  • Luke
    replied
    Originally posted by JohnGalt View Post
    I just built for openSUSE Tumbleweed from the src package (software versions should be relatively on par with fedora rawhide).

    I created and used a new profile as outlined, and verified it is in fact running on wayland and not Xwayland. I also tested on gnome (wayland), sway, and weston, as well as radeonsi and amdgpu. However, all had the following issue: The window only updates on change of focus or window resize, which makes it unusable. Anyone else run into this or have ideas?

    Edit: I also went into settings and disabled hw accel with no change.

    Edit2: the gtk stuff (menus and whatnot) works fine without needing to resize, change focus, or move the window. The page only updates on those actions (so no change on typing or anything else).
    What GTK3 version are you testing? This sounds a bit like its related to a bug in gtk 3.21.3 that was patched in master a couple days ater release. GTK devs radically changed the drawing system-and FIrefox would turn black on change of focus, updating only when each widget was moused over. I saw this in both X11 and with Xwayland with released FF47.

    Leave a comment:


  • JohnGalt
    replied
    I just built for openSUSE Tumbleweed from the src package (software versions should be relatively on par with fedora rawhide).

    I created and used a new profile as outlined, and verified it is in fact running on wayland and not Xwayland. I also tested on gnome (wayland), sway, and weston, as well as radeonsi and amdgpu. However, all had the following issue: The window only updates on change of focus or window resize, which makes it unusable. Anyone else run into this or have ideas?

    Edit: I also went into settings and disabled hw accel with no change.

    Edit2: the gtk stuff (menus and whatnot) works fine without needing to resize, change focus, or move the window. The page only updates on those actions (so no change on typing or anything else).
    Last edited by JohnGalt; 24 June 2016, 02:26 AM.

    Leave a comment:


  • microcode
    replied
    Originally posted by starshipeleven View Post

    Hmm, I'm suspecting that direct-rendering programs cannot go through broadway. Or run on Wayland unless the parts relying on Xorg are rewritten.

    On FIrefox the gtk+ is only for windows decoration afaik.
    It's also used for input method integration in text fields(ibus and friends), context menus, buttons, checkboxes, dropdowns... a few other things. Chrome has its own native-level toolkit, but it doesn't have support for all the input method frameworks and rendering engines on their different platforms yet; so they're in a similar situation.

    Leave a comment:


  • starshipeleven
    replied
    Originally posted by unixfan2001 View Post
    Curious.

    Has anyone managed to run any other XUL based applications on Wayland or Broadway? Launching Firefox with Broadway for the backend, I'm presented with a (no doubt beautiful and tear free) crash reporter.
    Hmm, I'm suspecting that direct-rendering programs cannot go through broadway. Or run on Wayland unless the parts relying on Xorg are rewritten.

    On FIrefox the gtk+ is only for windows decoration afaik.

    Leave a comment:


  • unixfan2001
    replied
    Curious.

    Has anyone managed to run any other XUL based applications on Wayland or Broadway? Launching Firefox with Broadway for the backend, I'm presented with a (no doubt beautiful and tear free) crash reporter.

    Leave a comment:


  • Luke
    replied
    Here's an interesting use case for Firefox on Wayland: Firefox on separate user without X, isolated from your session. With Wayland (at least from weston-launch), you can have GUI sessions on more than one TTY and one of them can be your X session. If a website does something nasty but can't break root, your main home directory is safe. You can even trash and remake this whole directory for every session as an powerful antitracking tool.

    Set up another user account and put copies your locked-down and customized .mozilla and .cache/mozilla directories there and chown them to that account. Now you can ctrl-alt-F2 to another TTY, log in as that account, run weston-launch and then run Firefox as that user. To fetch a file you want to upload, ctrl-alt-F7 back to your X session and login, it's still there. You can set move files between the directories via Sudo from your main account and chown them to match. Setting up the Firefox user account without sudo priviliges closes another attack vector, BTW. Your home directory should not be writable or even listable from the Firefox user account.

    Leave a comment:


  • marco-c
    replied
    Looks like OpenGL acceleration will work, after switching to EGL from GLX.

    Leave a comment:


  • LinAGKar
    replied
    Originally posted by CrystalGamma View Post
    "currently relies upon Wayland" → "relies upon X11"
    Probably supposed to say XWayland.

    Leave a comment:


  • Daktyl198
    replied
    Originally posted by ElectricPrism View Post
    What I learned from this article:
    up till now Firefox didn't work on wayland.
    Firefox works on XWayland. 95% of graphical programs don't run natively on Wayland yet, especially not ones with very large, very old codebases like Firefox.

    Leave a comment:

Working...
X