Closed Bug 1593481 Opened 5 years ago Closed 4 years ago

[Wayland/KDE] Nightly 72.0a1 on Wayland stopped responding after clicking on > button (Show connection details) in Plasma on Wayland

Categories

(Core :: Widget: Gtk, defect)

Product:
Core
Component:
Widget: Gtk
Version:
72 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: matt.fagnani, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

  1. Boot Fedora 31 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. install or update to firefox nightly 72.0a1 (2019-11-02)
  4. start konsole
    5 . change directory to that where nightly was installed, then run
    MOZ_ENABLE_WAYLAND=1 ./firefox &
  5. set layers.acceleration.force-enabled to true in about:config as recommended at https://bugzilla.mozilla.org/show_bug.cgi?id=1584845#c8
  6. close firefox
  7. MOZ_ENABLE_WAYLAND=1 ./firefox &
  8. Load an https site. An example I used was https://bodhi.fedoraproject.org/updates/?releases=F31
  9. Click on the lock icon in the address bar
  10. Click on the > button (Show connection details)

Actual results:

I started Firefox Nightly 72.0a1 (2019-11-02) and earlier on Wayland with layers.acceleration.force-enabled=true in about:config. I loaded https sites. I clicked on the lock icon in the address bar. I clicked on the > button which had the popup tooltip Show connection details. Firefox stopped responding and Firefox Nightly (Not Responding) was shown in the top bar. The window colours faded as happens when a Plasma window is unresponsive. I've seen this from 71.0a1 (2019-10-01) to 72.a1 (2019-11-02) on Wayland with layers.acceleration.force-enabled=true stop responding like this each of 10+ times, and I hadn't seen that before with 71.0a1 or earlier on Wayland with layers.acceleration.force-enabled=false. I've had to close firefox when it stopped responding like that because it didn't start responding again.

Expected results:

Firefox should have kept responding normally after clicking the > button.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Blocks: wayland-kde
No longer blocks: wayland

Is this still valid, Matt?

Flags: needinfo?(matthew.fagnani)

(In reply to Robert Mader [:rmader] from comment #2)

Is this still valid, Matt?

Robert, I haven't seen this problem happen in recent Firefox Nightly versions on Wayland with WebRender enabled in Plasma. I think it was fixed. Thanks.

Flags: needinfo?(matthew.fagnani)

Thanks!

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.