Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1770897 - Firefox on Wayland shows blank drop-down menu for LastPass add-on
Summary: Firefox on Wayland shows blank drop-down menu for LastPass add-on
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 31
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Jan Horak
QA Contact: Fedora Extras Quality Assurance
: 1766818 (view as bug list)
Depends On:
Blocks: ffwayland
TreeView+ depends on / blocked
Reported: 2019-11-11 13:05 UTC by Steven Bakker
Modified: 2020-11-24 20:07 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-11-24 20:07:14 UTC
Type: Bug

Attachments (Terms of Use)

Description Steven Bakker 2019-11-11 13:05:56 UTC
Description of problem:

With the LastPass add-on installed, when clicking on the LastPass icon, most of the time (~98%) the drop down menu shows seems to "flicker" and display as a blank rectangle.

This problem does not occur on firefox-x11

Version-Release number of selected component (if applicable):


How reproducible:

Nearly always when Firefox is run with the Wayland backend. Never when run with the X11 backend.

Steps to Reproduce:

1. Run Firefox with "MOZ_DISABLE_WAYLAND=0"
2. Install Lastpass add-on
3. Click on Lastpass icon to get drop-down menu

Actual results:

Possible "flicker" then white rectangle.

Expected results:

Drop down menu with text.

Additional info:

As said, this does not occur when Firefox is run with the X11 backend (MOZ_DISABLE_WAYLAND=1).

For some reason this only seems to affect the Lastpass add-on. Others (e.g. uBlock Origin, Privacy Badger, FoxyProxy, ColorZilla) do not have this problem.

Still, the fact that this happens on Wayland, but not on XWayland makes me think it's not so much a bug in the add-on.

Comment 1 Martin Stransky 2019-11-11 20:51:47 UTC
Jan, can you look at it please? Thanks.

Comment 2 Jan Horak 2019-11-14 13:55:34 UTC
Upstream bug:

Comment 3 Jan Horak 2019-11-14 14:39:54 UTC
*** Bug 1766818 has been marked as a duplicate of this bug. ***

Comment 4 Ben Cotton 2020-11-03 17:05:13 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

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 31 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.

Comment 5 Ben Cotton 2020-11-24 20:07:14 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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