I realize now that gdb was catching SIGPIPE before evolution had a
chance to handle it. I've changed how I start gdb to ignore SIGPIPE. I
will file a different bug if I uncover the real problem. This bug is
invalid.
** Changed in: evolution-exchange (Ubuntu)
Status: New = Invalid
**
I realize now that gdb was catching SIGPIPE before evolution had a
chance to handle it. I've changed how I start gdb to ignore SIGPIPE. I
will file a different bug if I uncover the real problem. This bug is
invalid.
** Changed in: evolution-exchange (Ubuntu)
Status: New = Invalid
**
** Changed in: openldap2.3 (Ubuntu)
Status: Incomplete = New
--
evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2
https://bugs.launchpad.net/bugs/239184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: openldap2.3 (Ubuntu)
Status: Incomplete = New
--
evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2
https://bugs.launchpad.net/bugs/239184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: openldap2.3 (Ubuntu)
Importance: Undecided
Status: New
--
evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2
https://bugs.launchpad.net/bugs/239184
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Which version of libldap are you using?
Thanks
chuck
** Changed in: openldap2.3 (Ubuntu)
Status: New = Incomplete
--
evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2
https://bugs.launchpad.net/bugs/239184
You received this bug notification because you are a
libldap-2.4-2 2.4.9-0ubuntu0.8.04 from hardy updates.
--
evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2
https://bugs.launchpad.net/bugs/239184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap2.3 in
Happened again. I'll attach a new backtrace.
** Changed in: evolution-exchange (Ubuntu)
Status: Invalid = New
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2008-0658
--
evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2
Here's the top of my /usr/share/doc/libldap-2.4-2/changelog.Debian.gz
file:
openldap2.3 (2.4.9-0ubuntu0.8.04) hardy-proposed; urgency=low
* New upstream version: (LP: #237688)
This verison fixes a number of bugs including syncrepl issues,
assertion errors, and segmentation faults found
So. I believe this bug is defiantly not a duplicate of #215904.
I've looked at the code and there's something that puzzles me and that's
how sb_debug_write is in the stack trace 6 times like it is recursively
calling itself. Is this what his happening in the macro
LBER_SBIOD_WRITE_NEXT()?
**
I agree, this is not a duplicate. Although the stack trace is similar,
that bug dies in the assert() showing an invalid sockbuf while this one
gets past there and dies in the write somewhere. Plus, this appears to
be failing with a SIGPIPE, which means some kind of unexpected pipe
failure. I
** Also affects: openldap2.3 (Ubuntu)
Importance: Undecided
Status: New
--
evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2
https://bugs.launchpad.net/bugs/239184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Which version of libldap are you using?
Thanks
chuck
** Changed in: openldap2.3 (Ubuntu)
Status: New = Incomplete
--
evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2
https://bugs.launchpad.net/bugs/239184
You received this bug notification because you are a
libldap-2.4-2 2.4.9-0ubuntu0.8.04 from hardy updates.
--
evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2
https://bugs.launchpad.net/bugs/239184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I haven't crashed in a while. I believe the update finally got applied
correctly. I must have done something wrong when trying to pull in the
update from hardy-proposed.
** Changed in: evolution-exchange (Ubuntu)
Status: New = Invalid
--
evolution-exchange-storage crash in
To see whether you have the right stuff, look at the changelog file:
/usr/share/doc/libldap-2.4-2/changelog.Debian.gz
You should see that the first entry in the changelog is either
openldap2.3 (2.4.7-6ubuntu4.2) which contains this reference: Fix
ber_flush2 assertion error. (LP: #215904)
Or, the
Still having these crashes once or twice per day. Likely I'm not the
only one seeing these crashes. BTW, don't know if it matters, but I'm on
x86_64.
--
evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2
https://bugs.launchpad.net/bugs/239184
You received this bug
** Attachment added: backtrace of evolution-exchange-storage
http://launchpadlibrarian.net/15198121/gdb-evolution-exchange-storage.txt1
--
evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2
https://bugs.launchpad.net/bugs/239184
You received this bug notification
Yes, this is an instance of that bug. Compare that stack trace to the
one in the Gnome bug report attached to the LP bug.
Can you please be clearer about what you mean by hardy with updates?
Do you have the -proposed repository enabled? Also please provide the
version of your libldap-2.4-2
I had enabled hardy-proposed and upgraded libldap-2.4-2 and tested for
bug #215904. At the time I tested it really seemed to help reduce
crashing, but still crashed from time to time. After the update it
crashed much less often, maybe 2 times per day rather than once every 30
min.
My
20 matches
Mail list logo
