I used LocalFolders to setup additions folders w/i TB, e.g. /nas/myNetShare/LocalMail. /nas/myNetShare is the mountpoint for the NAS server file system with contains the actual mail files. Additionally the mountpoint is not static, that is, it is not permanently mounted, but dynamically mounted via automount process whenever /nas/myNetShare/LocaMail is accessed. That worked well not only for TB but also for other programs like xfe, shell, etc.
Now I upgraded to ubuntu 24.04 recently and increased the kernel version from 5.15 to 6.9. This triggered a new installation of TB to 128 via snap. After that, TB would not connect to the above path, instead it produced an error message "The Local Directory path /nas/myNetShare/LocalMail is invalid." and generated a pathname by itself "/run/user//doc//LocalMail ... ". Then I get the meassage "Thunderbird needs to restart now to apply the change to the Local directory setting." Once restarted, which takes ages, I can see and work with my files on the NAS server.
However, this only works for one startup of TB. Once I terminate TB session and restart the computer this generated path is no longer valid since it apparently links to a runtime link instead of the original path! And in addition the startup time for TB is outrageous and I have to put in the path /nas/myNetShare/LocalMail again every time! This sucks big time!
Can anybody help me how to fix this so that TB accepts and keeps the actual path "/nas/myNetShare/LocaMail", PLEASE!
Update: I de-installed the snap version and reinstalled the deb package. Now local folders residing on NAS servers works again. Still interested in some feedback pertaining to the TB snap code.
System: OS: Linux ubuntu 24.04 kernel 6.9.3-060903-generic (64-bit) #202405300957 / 16 core 32 GB mem Thunderbird (snap): 128.2.0esr-1 509 latest/stable/… canonical✓ - TB extensions: LocalFolders. v4.1.0 / Lightning Calendar Tabs, v3.3 / CardBook, v94.5 NAS Server: Synology 1512+
I used LocalFolders to setup additions folders w/i TB, e.g. /nas/myNetShare/LocalMail. /nas/myNetShare is the mountpoint for the NAS server file system with contains the actual mail files. Additionally the mountpoint is not static, that is, it is not permanently mounted, but dynamically mounted via automount process whenever /nas/myNetShare/LocaMail is accessed. That worked well not only for TB but also for other programs like xfe, shell, etc.
Now I upgraded to ubuntu 24.04 recently and increased the kernel version from 5.15 to 6.9. This triggered a new installation of TB to 128 via snap. After that, TB would not connect to the above path, instead it produced an error message "The Local Directory path /nas/myNetShare/LocalMail is invalid." and generated a pathname by itself "/run/user//doc//LocalMail ... ". Then I get the meassage "Thunderbird needs to restart now to apply the change to the Local directory setting." Once restarted, which takes ages, I can see and work with my files on the NAS server.
However, this only works for one startup of TB. Once I terminate TB session and restart the computer this generated path is no longer valid since it apparently links to a runtime link instead of the original path! And in addition the startup time for TB is outrageous and I have to put in the path /nas/myNetShare/LocalMail again every time! This sucks big time!
Can anybody help me how to fix this so that TB accepts and keeps the actual path "/nas/myNetShare/LocaMail", PLEASE!