Thunderbird does not startup after upgrade to 38.3.0
I had problems before and I tried the same solution: Making sure that all in the ~/.thunderbird directory was correctly 'owned'. I also renamed this directory but no new one was created when I start Thunderbird. The crash must be before it needs to access this directory.
I searched the Internet and came to a page where they suggested to run strace to see what was done. Here are the last 20 lines of the 6025:
Code: Select all
read(6, "127.0.0.1\tlocalhost\n127.0.1.1\tfa"..., 4096) = 220
read(6, "", 4096) = 0
close(6) = 0
munmap(0x7ff08fa01000, 4096) = 0
open("/etc/ldap/ldap.conf", O_RDONLY) = 6
fstat(6, {st_mode=S_IFREG|0644, st_size=332, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ff08fa01000
read(6, "#\n# LDAP Defaults\n#\n\n# See ldap."..., 4096) = 332
read(6, "", 4096) = 0
close(6) = 0
munmap(0x7ff08fa01000, 4096) = 0
geteuid() = xxxx
getuid() = xxxx
open("/homes/username/ldaprc", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/homes/username/.ldaprc", O_RDONLY) = -1 ENOENT (No such file or directory)
open("ldaprc", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/etc/ldap.conf", {st_mode=S_IFREG|0644, st_size=9155, ...}) = 0
geteuid() = 20000
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
+++ killed by SIGSEGV +++
Searching further on problems with LDAP I came upon an old bug. The solution was:
Effectivly, I read the bugs report and follow the instructions : touch /var/lib/libnss-ldap/bind_policy_soft
Correct. Until the libnss-ldap maintainer (or upstream) comes to his senses, you might want to set bind=soft in your /etc/libnss-ldap.conf config explicitly.
This did not help. Thunderbird still did not start. Only when I renamed the libnss-ldap.conf I was able to start Thunderbird but then I have nothing since my home directory is on a NAS and the mounting and user authentication is done with OpenLDAP so I gave the libnss-ldap.conf file its original name. Now Thunderbird no longer starts up but I am able to query the OpenLDAP server. It does not look that this is the real problem. Somewhere Thunderbird accesses OpenLDAP in a different way.
The service nscd is not running. If I start it then I am able to start Thunderbird but I cannot fetch my mail nor see the mails I already received. I can however access my address book and agenda. In the mean time 'Mint' has stopped nscd.
I use Mint version is 17.2 XFce with all the updates done and Thunderbird is also at the last version 1:38.3.0+build1-0ubuntu0.14.04.1.
Modificadas por Marco el
Todas las respuestas (4)
I don't think I can follow all the different things you tried. Also it sounds like you're trying to mix up multiple problems, which may or may not be related.
The crash must be before it needs to access this directory.
What crash?
I had problems before and I tried the same solution: Making sure that all in the ~/.thunderbird directory was correctly 'owned'.
Not sure what problems you where trying to fix with that. But I doubt that file ownership in your profile folder has got anything to do with a Thunderbird update.
Other issues mentioned above:
Thunderbird does not startup
Only when I renamed the libnss-ldap.conf I was able to start Thunderbird
The service nscd is not running. If I start it then I am able to start Thunderbird
I cannot fetch my mail nor see the mails I already received.
Please pick one issue at a time.
The problem is that I start Thunderbird and it crashes before it seems to do anything with my profile. All the other things were done during my search on WHY it did this.
In the mean time it looks like the nscd service is running again. Now I am busy to create my accounts again and to put all my 'old' mails back in the 'new' accounts.
I still do not know why all of this happens. I am not even sure if it is nscd or Thunderbird :-(
Do you have a crash ID? https://support.mozilla.org/en-US/kb/mozilla-crash-reporter-tb#w_viewing-crash-reports
When it crashes it does not give a message. It crashes silently. Now that it is running I have no trace of a crash either since when it crashes Thunderbird has no access to my profile.