Bug 1753751 - firefox 69.0-4 to 69.0-7 and 69.0.1-1 on Wayland don't refresh or respond properly on Plasma on Wayland in F31
Summary: firefox 69.0-4 to 69.0-7 and 69.0.1-1 on Wayland don't refresh or respond pro...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ffwayland
TreeView+ depends on / blocked
 
Reported: 2019-09-19 18:14 UTC by Matt Fagnani
Modified: 2019-11-05 13:47 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 13:47:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1584845 0 None None None 2019-09-29 17:55:07 UTC

Description Matt Fagnani 2019-09-19 18:14:33 UTC
Description of problem:

I was using firefox 69.0-2 on Wayland on Plasma on Wayland in F31 which was running normally. I used MOZ_ENABLE_WAYLAND=1 firefox since the normal firefox menu option and icon started firefox on X in Plasma. I updated to firefox-69.0-7 from koji using dnf. firefox-69.0-7 on wayland hasn't been refreshing the window below the menu bar or responding properly in Plasma on Wayland. When I select a bookmark, the site isn't shown. After resizing the window, the site was shown. I scrolled up and down, but that didn't move the site's display. I clicked on links, but firefox didn't show the new site. Entering text in the address bar didn't show the text in the bar, but it was shown for the search function popup sometimes. When I clicked on the + button, a new tab wasn't shown. However, when I closed firefox, the pop-up box had "You are about to close 2 tabs." The tab might have been created, but firefox wasn't refeshed to show the tab.

I tested 69.0-3 from koji which ran normally on Wayland in Plasma on Wayland.
All of 69.0-4, 69.0-5, 69.0-6, 69.0-7, and 69.0.1-1 have the Wayland refeshing and response problems. The changelog for 69.0-4 indicates a fix for Wayland video playback which might be involved.

* Wed Sep 11 2019 Martin Stransky <stransky> - 69.0-4
- Added fix for mozbz#1579794 - Flickering on video playback on
  4k/HiDPI displays.


Version-Release number of selected component (if applicable):
firefox-69.0-4 to 69.0.1-1.fc31.x86_64
kf5-kwayland-0:5.61.0-1.fc31.x86_64
plasma-desktop-0:5.16.4-1.fc31.x86_64
qt5-qtwayland-0:5.12.4-7.fc31.x86_64

How reproducible:
Each of 10+ times I've tried using firefox 69.0-4 to 69.0.1-1 on Wayland in Plasma on Wayland

Steps to Reproduce:
1. Boot F31 KDE Plasma spin installation with kwin-wayland and its dependencies installed, fully updated with updates-testing enabled
2. Log in to Plasma on Wayland from sddm
3. update to firefox-69.0-7 or 69.0.1-1
4. MOZ_ENABLE_WAYLAND=1 firefox (in konsole)
5. try to enter an address in the address bar 
6. select a bookmark to a site for example, https://bodhi.fedoraproject.org/updates/?releases=F31
7. resize firefox 
8. try to click on a link
9. click + to open a new tab
10. close firefox

Actual results:
firefox 69.0-4 to 69.0-7 and 69.0.1-1 on Wayland don't refresh or respond properly on Plasma on Wayland in F31

Expected results:
firefox on wayland refreshes and responds properly on Plasma on Wayland

Additional info:
Firefox 69.0-4 to 69.0.1-1 on X in Plasma on Wayland aren't affected by this problem. The issue may be related to the use of Plasma on Wayland. I haven't tried Firefox on Wayland in GNOME on Wayland.

Comment 1 Martin Stransky 2019-09-20 10:48:53 UTC
Hi, this is a regression from 69.0 line which was partially fixed by fedora builds and should be fixed completely by https://bodhi.fedoraproject.org/updates/FEDORA-2019-7f7bace5b4
Can you please test this update?
Thanks.

Comment 2 Matt Fagnani 2019-09-20 18:16:29 UTC
(In reply to Martin Stransky from comment #1)
> Hi, this is a regression from 69.0 line which was partially fixed by fedora
> builds and should be fixed completely by
> https://bodhi.fedoraproject.org/updates/FEDORA-2019-7f7bace5b4
> Can you please test this update?
> Thanks.

Martin, 69.0.1-3 on Wayland from koji has had the same refresh/response problems in Plasma on Wayland that I reported. I rebooted after installing and testing 69.0.1-3 just in case that mattered. The problem might be different from that fixed by 69.0.1-3. Thanks.

Comment 3 Martin Stransky 2019-09-23 08:16:35 UTC
Can you please try latest nightly from Mozilla? How-to is here:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Testing_Mozilla_binaries
Thanks.

Comment 4 Matt Fagnani 2019-09-23 16:31:31 UTC
(In reply to Martin Stransky from comment #3)
> Can you please try latest nightly from Mozilla? How-to is here:
> https://fedoraproject.org/wiki/
> How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Testing_Mozilla_binaries
> Thanks.

Firefox Nightly 71.0a1 (2019-09-23) run with MOZ_ENABLE_WAYLAND=1 ./firefox -ProfileManager -no-remote as suggested at the link you gave
had the same refresh/response problems on Plasma on Wayland that I reported. The selection of a profile in ProfileManager didn't highlight the profile correctly though Nightly did start after with the profile I clicked on. I noticed in testing 69.0-4 and 69.0-5 briefly that sites I selected from bookmarks were displayed without having to resize the window though they didn't respond correctly, whereas in 69.0-6 and later including 71.0a1 firefox needed to be resized before they showed up. There might've been further changes in 69.0-6 that led to that additional refreshing issue. Thanks.

Comment 5 Matt Fagnani 2019-09-29 17:55:08 UTC
These problems have been present with Nightly 71.0a1 (2019-09-23 to 2019-09-28) on Wayland in Plasma on Wayland. I reported the issues at https://bugzilla.mozilla.org/show_bug.cgi?id=1584845

Comment 6 Martin Stransky 2019-11-05 13:47:08 UTC
Let's track it upstream then, Thanks.


Note You need to log in before you can comment on or make changes to this bug.