Bug 1583536

Summary: [wayland] firefox not responding to requests from other apps
Product: [Fedora] Fedora Reporter: Zbigniew Jędrzejewski-Szmek <zbyszek>
Component: firefoxAssignee: Martin Stransky <stransky>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: alexl, gecko-bugs-nobody, jhorak, john.j5live, kengert, pjasicek, rastus.vernon, rhughes, rstrode, sandmann, stransky
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-30 10:23:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dialog window none

Description Zbigniew Jędrzejewski-Szmek 2018-05-29 08:13:03 UTC 
Description of problem:
When I do a ctrl-click in gnome-terminal to open a link, after a short delay I get the message "Firefox is not responding...". 
I first noticed that ctrl-click in terminal and other applications does not work.

I get the same result when I click on the "firefox" (non-wayland version) in gnome-shell.

I see that "firefox-wayland https://url" work fine (a new tab pops up), but "firefox https://url" gives the same error as above. So it seems that the apps are trying to communicate with the non-wayland version.

Version-Release number of selected component (if applicable):
firefox-60.0.1-3.fc28.x86_64

How reproducible:
100% in this run of firefox. I haven't restarted it yet.

Steps to Reproduce:
1. start firefox using the "Firefox on Wayland" icon in gnome
2. ctrl-click on an url in gnome-terminal
Comment 1 Zbigniew Jędrzejewski-Szmek 2018-05-29 08:14:15 UTC 
Created attachment 1445225 [details]
dialog window
Comment 2 Rastus Vernon 2018-05-29 23:53:23 UTC 
Changing your default web browser to Firefox on Wayland (in the Settings application if you are using GNOME) fixes this, so I would not consider it a bug.
Comment 3 Zbigniew Jędrzejewski-Szmek 2018-05-30 05:50:05 UTC 
Even though it can be worked around, it's an annoying usability issue. For the user it's like "I started the browser with different options and some related functionality broke".
Comment 4 Martin Stransky 2018-05-30 10:23:08 UTC 
Moving upstream - https://bugzilla.mozilla.org/show_bug.cgi?id=1465371