Announcement

Collapse
No announcement yet.

Firefox 75 Released With Flatpak Support, Wayland Improvements

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

  • #61
    Originally posted by TemplarGR View Post

    Dude, Wayland is not troublefree (neither is X11), but it is far from unusuable like you claim. Attempting to find corner cases that it doesn't work is just that: Corner cases. "Not usuable"= Most of the cases don't work, not just corner cases. Your bogus claim that you need to wait 5 more years is stupid, and besides, if people aren't using it then things won't get fixed quickly anyway...
    Please point me to where I said it's unusable. I only said it's not ready for primetime yet. As in a great deal of people (not all) are going back to Xorg because they have issues of some kind. Here and there, more or less annoying, but enough (not corner cases) to move away, especially if you don't want to lose valuable time geeking/hacking to make it work.

    I initially thought I would switch 8 to 5 years ago and here I am, still on Xorg (with which I barely have any issue, except for 4k60Hz that you need to hack).
    These things take time, please don't take the 5 years as a hard deadline. It just means it's taking so much time getting there history tells me one shouldn't rush estimations anymore.

    I'm happy you're extensively beta testing it though. We need more brave pioneers like you. And I'll thank you deeply once I feel like it's ready for me to take the leap.

    Comment


    • #62
      Originally posted by TemplarGR View Post
      Been using it since yesterday on Archlinux. It is great, it seems the Wayland mouse focus issues have been fixed. Though the Arch package seems to be missing some important upstream patches for dmabuf, it crashes for me when i enable vaapi and webgl on amdgpu and mesa. I commented on Martin Stranky's blog about it and he said he is going to write a blog post about it.
      The mouse focus issues were gnome/gtk issues:
      When Firefox is switched by Alt+Tab, ALT remains pressed for mouse scroll event. That causes regression on background scrolling when history is scrolled instead of content (

      https://gitlab.gnome.org/GNOME/gtk/issues/2511 (workaround: https://bugzilla.mozilla.org/show_bug.cgi?id=1615098)

      Regarding the crash with dmabuf, I had the same one arch, try installing libva-intel-driver (or libva-intel-driver-hybrid) and start FF with
      LIBVA_DRIVER_NAME=i965 (https://bugzilla.mozilla.org/show_bug.cgi?id=1619585)

      Comment


      • #63
        Originally posted by Britoid
        The Canonical one, however just lets Canonical relicense the project in the future, which puts other companes and individuals off contributing, you don't see Red Hat requiring a CLA and Red Hat is opposed to them.
        Uhh yes they do. Red Hat doesn’t want to be exposed to legal liability any more than Canonical does.

        Comment


        • #64
          Wayland works well in my experience on Intel/AMD. The only issue I have is the lack of a hardware cursor.

          Comment


          • #65
            Originally posted by fguerraz View Post

            The mouse focus issues were gnome/gtk issues:
            When Firefox is switched by Alt+Tab, ALT remains pressed for mouse scroll event. That causes regression on background scrolling when history is scrolled instead of content (

            https://gitlab.gnome.org/GNOME/gtk/issues/2511 (workaround: https://bugzilla.mozilla.org/show_bug.cgi?id=1615098)

            Regarding the crash with dmabuf, I had the same one arch, try installing libva-intel-driver (or libva-intel-driver-hybrid) and start FF with
            LIBVA_DRIVER_NAME=i965 (https://bugzilla.mozilla.org/show_bug.cgi?id=1619585)
            I doubted this would work because i have an AMD gpu, but i tried it anyway, it still crashes as soon as i try to play a video file.

            Comment


            • #66
              Originally posted by bug77 View Post

              Even RHEL needs a GUI in 2020, so a buttery smooth one won't hurt.
              But contributions to Firefox are to be commended regardless, the Internet would be in a much worse shape if FIrefox went away.
              No, because people use RHEL in the cloud without a GUI. People work remotely with tools such as SSH, Chef, Puppet, etc. If there were a need for a UI people could use a poor desktop environment because there is it much need for a hardware-accelerated, modern UI. It's not where Red Hat makes their money.

              Comment


              • #67
                Originally posted by bug77 View Post

                Well, I disagree. Nobody has ever been forced to contribute to a CLA project. You don't like the terms (which is your own right) you don't contribute. Let it die, if the license is that draconian.
                Without centralization, what do you have? [...]
                One of the main reason the CLA is needed is due to the agreement with the Free-Qt Foundation, that says that if Qt is ever closed sourced, or stops being maintained, the last released versions becomes available under a BSD license. It wouldn't be possible to do that re-licensing without the CLA.

                -- Adapted from what Carewolf wrote in https://www.phoronix.com/forums/foru...873#post945873

                Comment


                • #68
                  Originally posted by bug77 View Post

                  Well, I disagree. Nobody has ever been forced to contribute to a CLA project. You don't like the terms (which is your own right) you don't contribute. Let it die, if the license is that draconian.
                  Without centralization, what do you have? [...]
                  Qt's innovation and features outpaces GTK+'s as far as it does, in large part *because* the CLA allows them to offer a closed-source licensing option.

                  Where did someone think they get the money to hire so many people to work on it full-time?

                  -- Adapted from what ssokolow wrote in https://www.phoronix.com/forums/foru...874#post945874
                  Last edited by Nth_man; 08 April 2020, 04:28 AM.

                  Comment


                  • #69
                    Originally posted by tildearrow View Post
                    Ugh, look. 144Hz turns the thread again into a pro-GNOME flamewar.
                    He is succeeding at trolling and destroying the rest with his crusade.
                    Resistance is futile. You will be assimilated.

                    Comment


                    • #70
                      Originally posted by cynical View Post
                      Wayland works well in my experience on Intel/AMD. The only issue I have is the lack of a hardware cursor.
                      It -is- a hardware cursor. Wayland is just simply incapable of syncing output on input, so it has no way to keep the rendering lag of the mouse cursor smooth. Or for that matter any input, even joystick and gamepads. Under CPU load there can be multiple -seconds- of input lag because of it. Wayland simply wasn't designed for desktops and you can just forget gaming totally.
                      Last edited by duby229; 08 April 2020, 09:38 AM.

                      Comment

                      Working...
                      X