Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Цей вебсайт матиме обмежену функціональність, доки ми проводимо його обслуговування для поліпшення роботи. Якщо прочитана стаття не розв'язала вашу проблему і ви хочете поставити питання, наша спільнота підтримки з радістю допоможе вам на @FirefoxSupport у Twitter та /r/firefox на Reddit.

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

Thunderbird 68.3.1 for mac that profiles on NAS via SMB shows empty window

  • 12 відповідей
  • 1 має цю проблему
  • 9 переглядів
  • Остання відповідь від LazyMonkey

more options

Hello,

I'm using Thunderbird 68.3.1(64bit) for mac and I put on my profile directory on NAS via smb mount. After I was upgrade from 60.9 to 68.3.1, Thanderbird show empty window. It's can use nomally from Thundervird 68.3.1(32bit) on Windows10. And also move to profile directory to local hdd on mac, I can use nomarry.

I was tried to "Rebuilding Global Database", but I was not work for me. https://support.mozilla.org/en-US/questions/1273989

How can I fix the problem?

Thank you for your help,

Hello, I'm using Thunderbird 68.3.1(64bit) for mac and I put on my profile directory on NAS via smb mount. After I was upgrade from 60.9 to 68.3.1, Thanderbird show empty window. It's can use nomally from Thundervird 68.3.1(32bit) on Windows10. And also move to profile directory to local hdd on mac, I can use nomarry. I was tried to "Rebuilding Global Database", but I was not work for me. https://support.mozilla.org/en-US/questions/1273989 How can I fix the problem? Thank you for your help,
Прикріплені знімки екрана

Усі відповіді (12)

more options

what is the contents of your profiles.ini file?

more options

Hi Matt,

Tahnk you for yor reply. I posts "prifiles.ini".

"old-profiles.ini" was used by ver60.9.1. Then, I was reinstall Thunderbird and create new profiles.ini as "cur-profiles.ini".


old-profiles.ini

[Profile1] Name=default IsRelative=0 Path=/Volumes/user01$/Documents/Thunderbird/Profiles/81fw7nv6.default Default=1

[Profile0] Name=default-release IsRelative=1 Path=Profiles/p5hrvrir.default-release

[General] StartWithLastProfile=1 Version=2

[Install712DAF5A23ABECDC] Default=/Volumes/user01$/Documents/Thunderbird/Profiles/81fw7nv6.default Locked=1

cur-profiles.ini

[Profile1] Name=default IsRelative=0 Path=/Volumes/user01$/Documents/Thunderbird/Profiles/81fw7nv6.default Default=1

[Profile0] Name=default-release IsRelative=1 Path=Profiles/p5hrvrir.default-release

[General] StartWithLastProfile=1 Version=2

[Install712DAF5A23ABECDC] Default=/Volumes/user01$/Documents/Thunderbird/Profiles/81fw7nv6.default Locked=1


And here is my mount information on mac.

>$ mount | grep /Volumes >/user01@192.168.1.100/user01$ on /Volumes/user01$ (smbfs, nodev, nosuid, mounted by user01)


Any more information needed? Thank you for your help,

more options

Visit help > troubleshooting > about:profiles Then where you see "Profile: default" do "launch profile ..."

more options

Hi Mery,

Thanks for your response, and I'm sorry it took so long to reply.

I tried troubleshooting avobe, but TB does nothing response. When I tried default profile, It was responsed. So I could not try to "launch profile.." this way.

Змінено LazyMonkey

more options

I was set up my mail account for newly and check mail has receive. Next, I was moved profiles directory to NAS, and modify "profiles.ini". Then I can see Thunderbird empty window that I was post 1st.

So I think this probrem does not associeate my old-profile, but Thunderbird 68.3.1 mac with profiles put on NAS.... (It seems to be work Thunderbird 68.3.1 on Windows10 as similar "profile.ini".)

more options

Is anybody have the solution or similor situation? Any Information is helpflu.

more options

I have emails some people, and I have had one suggestion. I don't know if it will do anything, but it is worth a try.

Apparently there has been a change in the NTLM version ised to access serer file systems. Try using the config editor to change the setting network.auth.force-generic-ntlm-v1 to true.

This change really dates from around the V30 time frame, but it might help by forcing an old method if the newer one has recently been changed (I can't find that, but I am starting to think it may have happened)

more options

Hi Matt,

Thank you for your help. But this solution did not work for me.

I could not understand correctly, but does it have relation with NTLM version on macOS? (Because, I can use same way on Windows 10.)

If I configure the profiles.ini as non exist directory, Thunderbird pop up the error. There is no error in my case. And I realize that I also cannot open "Thunderbird > Preferences".

If there is no people with likely same problem, may be this has just occur my environment only.

more options

I tried with AFP(Apple File Protocol) instead SMB, but It looks same. It could used by AFP before. (TB version was not remember.)

Perhaps, It is nothing associate with which File-Share-Protocol was used.

more options

Have you tried: Exit Thunderbird. Use 'profile manager' to create a new profile, navigate to the profile location in the NAS and tell Thunderbird to use this profile.

more options

This one is truly left field I more hopeful than knowledgeable..... In preferences change the proxy to none. Preferences> Advanced > Network and disk space Settings button.

This just something that came up in a connectivity to mail server thread. Wondered if it might be related as both a sort of networking.

more options

Hi, Grateful thanks for your advice.

I tried uninstall TB and reinstall, then newly create profile and move to nas. But It not work for me. It was same result.

And I tried to choose "proxy-none". But I could not find the change. :-(