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
Created attachment 1445225 [details] dialog window
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.
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".
Moving upstream - https://bugzilla.mozilla.org/show_bug.cgi?id=1465371