Closed Bug 470451 Opened 16 years ago Closed 16 years ago

Thunderbird 3.0 Trunk crashes on startup for LDAP users (using libnss-ldap and libpam-ldap)

Categories

(Thunderbird :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 292127

People

(Reporter: meuserj, Unassigned)

Details

(Keywords: qawanted)

Attachments

(2 files)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2 Build Identifier: http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2008-12-19-03-comm-central/thunderbird-3.0b2pre.en-US.linux-i686.tar.bz2 Thunderbird 3.0 trunk on my up to date Ubuntu 8.10 system has a fatal crash on startup whenever a non-local LDAP user attempts to run it. No window comes up, no crash dialog, in fact the segfault signal doesn't even end the process, it just hangs. The only reason I know it's segfaulting is by looking at the stack trace. This doesn't happen at all under pre-3.0 builds. Reproducible: Always Steps to Reproduce: 1. Download any 3.0b1 or later build 2. untar it and run it directly from the directory Actual Results: Program never comes up, according to stack traces it is silently segfaulting without the process closing. Expected Results: I kinda expected it to run... It has something to do with the fact that I am running as an LDAP user. When I try it with a fresh local user on the same machine, it works fine. When I try it with a fresh LDAP user, the above behavior occurs. This is on an up-to-date Ubuntu 8.10 system. libldap: 2.4.11-0ubuntu6.1 libpam-ldap: 184-4ubuntu2 libnss-ldap: 260-1ubuntu2 Since the crash report dialog never comes up, I can't automatically submit the crash data, but I have the files and will attach them after the initial submission.
Attached file Extra Crash Data
Attached file Crash Data Dump
Version: unspecified → Trunk
Attachment #353846 - Attachment mime type: application/octet-stream → text/plain
Attachment #353847 - Attachment mime type: application/octet-stream → text/plain
Just tested it with the latest build, still doesn't work.
(In reply to comment #3) > Just tested it with the latest build, still doesn't work. Considering no-one has done any work in that area its not a surprise. To get any useful crash data, you would need to submit a crash report and give us the id number: http://kb.mozillazine.org/Breakpad Though this bug does seem like it could be related to bug 374731 - though bug 374731 is on a different OS.
As I said in the original bug report, the crash report dialog never comes up. I've googled and asked on IRC, but cannot find a way to submit a crash report to breakpad if the crash dialog will not come up. I was told to submit a bug report to bugzilla and manually attach the crash report files, which I have done above.
Just checked the latest build. Problem still exists. Can someone at least confirm or disconfirm the bug for me so I can know if it's only on my end? Maybe tell me how to manually submit a bug to Breakpad?
Might also be a DUPE of bug 292127.
Keywords: qawanted
meuserj. there is currently no capability to manually send breakpad dumps to crash-stats.mozilla.com
Ok, I can confirm that this is a dupe of bug 292127. The work-around in the comments for that bug suggest copying away the version of libldap which came with thunderbird and symlinking in the system's version. That seems to do the trick for me (at least I can now run it).. haven't tried doing anything LDAP related like setting up an address book.
Sorry for spamming you all.. should have verified this beforehand. Using the symlink work-around, I am unable to use an LDAP server as and address book. Shredder segfaults. This is not optimal, but I can at least use it.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: