Clicking on links in an email body fails if Firefox (set as default browser) is already running. Thunderbird is starting a new process instead of using the already-running one. The new process fails to start with an error popup stating that Firefox is already running. Opening links when FF is not running works, but Firefox is already running on the desktop in the vast majority of the time. Reproducible: Always Steps to Reproduce: 1. Links were opening without issue under 115.9.0-1.fc39. 2. Updated just Thunderbird to 115.10.0-1.fc39. 3. Tried to open a link with FF running; Failed, got the "Firefox is already running" popup. 4. Downgraded back to 115.9.0-1.fc39. 5. Opening links works again, Actual Results: Thunderbird apparently invokes FF with --no-remote or --new-instance Expected Results: Should be invoking Firefox such that the existing process is used, with a new window/tab opened in it for the clicked link.
Info I missed before: This is all under GNOME on Wayland.
A diff of the /proc/:pid/environ between .9 and .10 shows only this added in .10: MOZ_APP_REMOTINGNAME=mozilla-thunderbird Other than that the only other env differences are DESKTOP_STARTUP_ID, GIO_LAUNCHED_DESKTOP_FILE_PID and XDG_ACTIVATION_TOKEN which seem normal to change per run.
Not sure what MOZ_APP_REMOTINGNAME does. For watever it may be worth I tried to "unset" it with a user .desktop file: Exec=env -u MOZ_APP_REMOTINGNAME thunderbird %u did not work (env var still present in /proc/:pid/environ) because the /usr/bin/thunderbird script checks the variable for being set. Exec=env MOZ_APP_REMOTINGNAME=" " thunderbird %u did seem to take effect based on /proc/:pid/environ but the behavior didn't change.
Happens on my machine as well (F39 Wayland).
Removing that export MOZ_APP_REMOTINGNAME=mozilla-thunderbird from /usr/bin/thunderbird actually fixed things for me.
Unfamiliar with Mercurial so haven't been able to track the reasoning for that MOZ_APP_REMOTINGNAME addition upstream, any pointers would be welcome.
Wait it's not upstream; https://src.fedoraproject.org/rpms/thunderbird/c/eb739a214337749db56fc2a3275f398411bd55b5
BTW I also installed thunderbird-wayland.x86_64-115.10.0-1.fc39 and started from the Wayland-specific desktop file, same issue persists. Confirming that building a locally patched 115.10.1-1 with the setting of MOZ_APP_REMOTINGNAME removed: diff --git a/thunderbird.sh.in b/thunderbird.sh.in index db5e171..3299b30 100644 --- a/thunderbird.sh.in +++ b/thunderbird.sh.in @@ -83,12 +83,6 @@ fi __WAYLAND_X11_PLACEHOLDER__ -# We need to link Firefox with desktop file name -if [ -z "$MOZ_APP_REMOTINGNAME" ] -then - export MOZ_APP_REMOTINGNAME=__APP_NAME__ -fi - ## ## Automatically installed langpacks are tracked by .fedora-langpack-install ## config file. Resolves this.
Is MOZ_APP_REMOTINGNAME something that's needed, at least in F39? Removing it form the script with the patched build doesn't seem to have any negative effect on my (GNOME/Wayland) desktop. Web links from email content open correctly in the already-running browser, and mailto: links from web pages open new message windows in Thunderbird as expected.
@Eike I see you've changed to MOZ_APP_REMOTINGNAME=firefox. I haven't had a chance to test the new build yet, so just thinking aloud here, apologies if this is noise: Would this work if the default browser is not Firefox? Would it need to instead be set to e.g. xdg-open to work for any default browser?
That was a misunderstanding of what that variable would accomplish. Also, it does not determine what browser is called, but then affecting the firefox runtime if set overriding its remoting name.
This should be fixed by https://koji.fedoraproject.org/koji/buildinfo?buildID=2442624
FEDORA-2024-15b892ebd3 (thunderbird-115.10.1-4.fc38) has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-15b892ebd3
FEDORA-2024-81c9a3fe50 (thunderbird-115.10.1-4.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-81c9a3fe50
FEDORA-2024-81c9a3fe50 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-81c9a3fe50` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-81c9a3fe50 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-15b892ebd3 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-15b892ebd3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-15b892ebd3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-81c9a3fe50 (thunderbird-115.10.1-4.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-15b892ebd3 (thunderbird-115.10.1-4.fc38) has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-3e35153569 (thunderbird-115.11.0-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-3e35153569
FEDORA-2024-3e35153569 (thunderbird-115.11.0-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.