** Changed in: firefox
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921931
Title:
Opening links results in "Firefox is already running, but is not
** Branch linked: lp:firefox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921931
Title:
Opening links results in "Firefox is already running, but is not
responding"
To manage notifications
This bug was fixed in the package firefox - 87.0+build3-0ubuntu4
---
firefox (87.0+build3-0ubuntu4) hirsute; urgency=medium
* Ensure that opening links from XWayland apps still works (LP:
#1921931)
-- Olivier Tilloy Tue, 13 Apr 2021
15:59:44 +0200
** Changed in: firefox
ok that makes sense, I think opening links from slack (electron/x11) was
likely the culprit that "poisoned" the running firefox instance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921931
Title:
** Changed in: firefox (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921931
Title:
Opening links results in "Firefox is already running, but is not
https://mastransky.wordpress.com/2020/03/16/wayland-x11-how-to-run-
firefox-in-mixed-environment/ is useful to understand the problem.
As suggested there, exporting MOZ_DBUS_REMOTE=1 when running in a
wayland session works around the problem.
I can observe the problem in a wayland session if I
Launchpad has imported 19 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1508803.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Thanks Olivier. That bug report looks related but seems more like it
never works, vs/ works for a little while and then stops working? But
adding the MOZ_DBUS_REMOTE flag that it mentions seems to fix the issue
when running with MOZ_ENABLE_WAYLAND in limited testing so far.
--
You received
This appears to be a known upstream bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1508803
** Bug watch added: Mozilla Bugzilla #1508803
https://bugzilla.mozilla.org/show_bug.cgi?id=1508803
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1508803
Importance:
Yes, commenting out the MOZ_ENABLE_WAYLAND line appears to fix the
issue. With MOZ_ENABLE_WAYLAND=1, initial link requests work, but after
a short while start getting the firefox is running but not responding
dialog. Without it, link requests work even after a while.
** Changed in: firefox
Thanks for the report Joe. If I understand correctly, you're saying that
it looks like a very recent regression, introduced by
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.hirsute/revision/1476
?
If so, could you hand-edit /usr/bin/firefox to comment out the line that
exports
11 matches
Mail list logo
