Since 121.0.1 update Apple Mail can't open links when Firefox is default browser
Categories
(Toolkit :: Application Update, defect)
Tracking
()
People
(Reporter: github, Unassigned, NeedInfo)
Details
Attachments
(1 file, 1 obsolete file)
|
156.89 KB,
image/png
|
Details |
Screenshot 2024-01-19 at 11.48.34.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:121.0) Gecko/20100101 Firefox/121.0
Steps to reproduce:
I have Firefox set as my default browser.
I clicked on https links in several messages in Apple Mail.
Actual results:
I got a pop-up error dialog as shown in the attached "Screenshot 2024-01-19 at 11.48.34.png" saying "The application can't be opened. -600".
This started happening with the update to 121.0.1. I did not have this problem with 121.0. There have been no macOS updates between working and broken. I am running macOS 13.6.3 and Apple Mail 16.0
Expected results:
The browser should be opened to display the link or raised and with a new tab added displaying the link.
I restarted Apple Mail. No change. Then I quit Firefox and attempted to run it again via clicking on the icon in the dock and by clicking on the icon in Launchpad. In both cases I got a pop up error dialog, in similar style to the one whose image I posted, that said something like "the application is no longer running." Nothing further happened. I tried many times with the same result. I then rebooted my Mac after which Firefox is working as usual.
I've never seen a problem like this before. Given that the only thing that changed on my system was the Firefox update, it is tempting to say the problem is related even though it took a reboot to clear it up.
|
||
Comment 2•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Application Update' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 3•1 year ago
|
||
Hmm, if the problem went away after a reboot, it sounds like some kind of transient error. Maybe this could be caused by a shutdown hang? I'm not sure what debugging information would still be around at this point, so there may not be anything we can do to investigate this further. But I'll try and see if I can think of something.
|
||
Updated•1 year ago
|
|
||
Comment 5•1 year ago
|
||
I can't seem to be able to reproduce your issue in a MacOS11, however, it may have been a very uncommon edge case.
Did this issue happen to reproduce again in the meantime? If yes, is there any more information that you can provide for us to investigate it further? If not, then I am inclined to close this report as worksforme due to the one-time reproduction.
Thank you for your report!
|
||
Comment 6•1 year ago
|
||
Hi! It is now more than 5 month since this error was reported and we have no signs that it ever happened again. We have also no way to reproduce it and no other bugs have been linked to this one. For these reasons I am following comment 5 to close this bug as WORKSFORME, because I assume that this bug was an uncommon edge case, probably caused by some kind of transient error as described in comment 3.
Description
•