Bug 671018

Created attachment 474368 [details]
File: backtrace

Thanks for a bug report. This seems to me like some corner-case in libsoup, but I would rather ask libsoup maintainer first. Meanwhile, what is your libsoup version, please?

Dan, what do you think, please?


Thread 1 (Thread 8805):
#0  0x0000003911834085 in raise () from /lib64/libc.so.6
No symbol table info available.
#1  0x0000003911835a36 in abort () from /lib64/libc.so.6
No symbol table info available.
#2  0x000000392200e208 in _gcry_fips_noreturn () at fips.c:875
No locals.
#3  0x0000003922006ff6 in gcry_create_nonce (buffer=0x7fd8c6ffc76f, length=1) at visibility.c:1251
        __FUNCTION__ = "gcry_create_nonce"
#4  0x000000392663d337 in wrap_gcry_rnd_init (ctx=<value optimized out>) at rnd-libgcrypt.c:39
        c = 0 '\000'
#5  0x000000392663b5dc in _gnutls_rnd_init () at random.c:39
No locals.
#6  0x000000392662cb16 in gnutls_global_init () at gnutls_global.c:240
        result = 0
        res = 0
#7  0x0000003927228568 in soup_gnutls_init () at soup-gnutls.c:586
        inited_gnutls = 0
#8  0x0000003927228dce in soup_ssl_get_client_credentials (ca_file=0x0) at soup-gnutls.c:612
        creds = <value optimized out>
        status = <value optimized out>
#9  0x0000003927237b49 in soup_session_get_connection (session=0x2bf7320 [SoupSessionSync], item=0x1a25110, try_pruning=0x7fd8c6ffc8dc) at soup-session.c:1351
        priv = 0x2bf7340
        conn = <value optimized out>
        host = 0x2e3e400
        remote_addr = 0x7fd8c80256a0 [SoupAddress]
        tunnel_addr = 0x0
        ssl_creds = <value optimized out>
        conns = <value optimized out>
        num_pending = <value optimized out>
        uri = <value optimized out>
        __PRETTY_FUNCTION__ = "soup_session_get_connection"
#10 0x000000392723b513 in get_connection (item=0x1a25110) at soup-session-sync.c:188
        session = 0x2bf7320 [SoupSessionSync]
        msg = 0x2539350 [SoupMessage]
        try_pruning = 0
        status = <value optimized out>

(In reply to comment #2)
> #2  0x000000392200e208 in _gcry_fips_noreturn () at fips.c:875
> No locals.
> #3  0x0000003922006ff6 in gcry_create_nonce (buffer=0x7fd8c6ffc76f, length=1)
> at visibility.c:1251

From a quick reading of the sources, it looks like this should only happen if gcrypt is forced into FIPS mode (qv http://www.gnupg.org/documentation/manuals/gcrypt/Enabling-FIPS-mode.html), and then its internal self-tests fail. I had never realized libgcrypt even had a FIPS mode until now, so I don't know anything more. It doesn't seem to be libsoup's fault though (and probably not evolution's fault unless some other part of evolution [or some plugin?] is making libgcrypt calls). It *might* be caused by memory corruption somewhere causing gcrypt's internal FIPS flag to get turned on when it wasn't supposed to be, although that seems pretty unlikely.

Forgive the late reply.

I am running:
libsoup-2.32.2-1.fc14.x86_64

Louis, are you able to reproduce this (or maybe similar) crash intentionally, please? Because if you can, then we can try to check whether any memory corruption is involved here or not, by running evolution under valgrind, which will be awfully slow (due to all the memory checking), but with a bit of luck, may bring us a pointer where to look.

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping