After TB (auto-)update: Opening TB shows error message about default mail program (Win10)
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: harald_scheidl, Unassigned)
Details
(Keywords: dupeme)
Attachments
(1 file)
|
5.01 KB,
image/png
|
Details |
Unbenannt.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0
Steps to reproduce:
- TB did an auto-update to to 91.2.1 (64-Bit)
- This introduced an error on Windows 10
- I opened TB (after the update), which since then shows the error message when opening: "There is no email program associated to perform the requested action. Please install an email program or, if one is already installed, create an association in the Default Programs control panel." (see attachment)
What I tried:
I also checked the default programs in Win10, where TB is still the selected app. I also tried re-installing it (but without overwriting the profile). I did the default-program check inside TB. It seems that the error comes from TB and not Windows.
I attached the error message - it's in German, the translation should be the one I wrote above.
Seems that this user reports the same issue: http://forums.mozillazine.org/viewtopic.php?f=39&t=3079833
Actual results:
Running TB 91.2.1 (64-Bit) in combination with Win10 gives the error "There is no email program associated to perform the requested action. Please install an email program or, if one is already installed, create an association in the Default Programs control panel." when starting TB. After closing the message box, TB works as usual.
Expected results:
Should start without this error message.
seems to have something to do with the following lines inside prefs.js:
user_pref("ldap_2.servers.eds.description", "EDS Address Book Bootstrapper");
user_pref("ldap_2.servers.eds.dirType", 3);
user_pref("ldap_2.servers.eds.filename", "eds.mab");
user_pref("ldap_2.servers.eds.position", 1);
user_pref("ldap_2.servers.eds.uri", "moz-abedsdirectory://");
After deleting them (found this hint somewhere on reddit) the error disappeared.
However, I would like to know what's going on here - what did I just delete - and why does it work after deleting these lines? And does this have some negative impact on something?
And why does it happen in the first place that this error occurs after an auto-update?
|
||
Comment 2•3 years ago
|
||
Reporter, do you still see this issue when using version 102?
Resolved per whiteboard
Description
•