Bug 75138 - imaps repeatedly crashes or locks
Summary: imaps repeatedly crashes or locks
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: kssl (show other bugs)
Version: 3.2
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: George Staikos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-13 10:58 UTC by Anno V. Heimburg
Modified: 2004-02-14 16:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anno V. Heimburg 2004-02-13 10:58:58 UTC
Version:           1.6 (using KDE 3.2.0, Gentoo)
Compiler:          gcc version 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)
OS:          Linux (i686) release 2.4.22-gentoo-r4

imaps often crashes, yielding a "Verbindung unterbrochen" (Connection interrupted?) message. Alternatively, imaps will eat any CPU it can get without doing anything, displaying 0% in the progress bar. Unencrypted imap and imap/TLS seem to work.

Qt: 3.3.0
OpenSSL: 0.9.7c

Below is a snip of .xsession-errors... Some trouble with SSL, it seems:
---
kdecore (KLibLoader): WARNING: KLibrary: /usr/kde/3.2/lib/libkdecore.so.4: undefined symbol: PKCS7_content_free
kdecore (KLibLoader): WARNING: KLibrary: /usr/kde/3.2/lib/libkdecore.so.4: undefined symbol: OpenSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/kde/3.2/lib/libkdecore.so.4: undefined symbol: OpenSSL_add_all_algorithms_conf
kdecore (KLibLoader): WARNING: KLibrary: /usr/kde/3.2/lib/libkdecore.so.4: undefined symbol: OpenSSL_add_all_algorithms_noconf
kio (KIOConnection): ERROR: Could not write data
---
And then boom.

The curious thing is that TLS works, and that I have no SSL problems with other apps - be it mozilla thunderbird or konqueror. So how do I introduce imaps to my SSL library? Thanks,
Anno.
Comment 1 Anno V. Heimburg 2004-02-13 11:05:25 UTC
Correction: https has that problem, too. 
Comment 2 Ingo Klöcker 2004-02-13 13:33:48 UTC
Seems to be an installation problem, i.e. your version of the OpenSSL library seems to be incompatible with KDE.
Comment 3 Anno V. Heimburg 2004-02-13 14:06:24 UTC
Is this a bug? I mean, it states OpenSSL >= 0.9.6 in the prerequisites. I 
have 0.9.7c.

Comment 4 George Staikos 2004-02-13 16:50:10 UTC
On Friday 13 February 2004 08:06, Anno V.Heimburg wrote:
> ------- Is this a bug? I mean, it states OpenSSL >= 0.9.6 in the
> prerequisites. I have 0.9.7c.

   Do you have a different OpenSSL installed than the one used to compile KDE, 
or perhaps more than one installed?

Comment 5 Anno V. Heimburg 2004-02-13 17:07:41 UTC
# locate libssl
/usr/lib/libssl.so.0.9.7
/usr/lib/libssl.so
/usr/lib/libssl.so.0
/usr/lib/mozilla/libssl3.so
/usr/lib/mozilla/libssl.a
/usr/lib/MozillaFirebird/libssl3.so
/usr/lib/libssl.a

I removed /usr/lib/mozilla from ld.so.config, ran ldconfig and restarted KDE. Mozilla doesn't seem to mind, but ssl isn't any less broken under KDE. The maneuver seems to have broken TLS, though - do I need to recompile (I'ld try, but it takes a good hour or so). (If the entry in ld.so.config proves to be the problem, I'll take this over to gentoo)
Comment 6 Anno V. Heimburg 2004-02-13 17:50:21 UTC
FWIW, recompiling kdelibs did nothing to change the situation
Comment 7 George Staikos 2004-02-13 17:57:03 UTC
On Friday 13 February 2004 11:50, Anno V.Heimburg wrote:
> ------- FWIW, recompiling kdelibs did nothing to change the situation

   Please build a debugging version of kdelibs and base and get a backtrace of 
it when it crashes or freezes.  There is a trick to get the debugger 
attached, which you can read about in kdebase/kioslaves/HOWTO.DEBUG (or 
something like that).

Comment 8 Anno V. Heimburg 2004-02-13 20:47:39 UTC
Attached gdb to imaps. Output below.
--
Program received signal SIGTERM, Terminated.
0x4166e082 in select () from /lib/libc.so.6
(gdb) bt
#0  0x4166e082 in select () from /lib/libc.so.6
#1  0x4037faf0 in __JCR_LIST__ () from /usr/kde/3.2/lib/libkio.so.4
(gdb) cont
Continuing.

Program exited normally.
(gdb) bt
No stack.
(gdb)
--
Comment 9 George Staikos 2004-02-13 21:13:04 UTC
On Friday 13 February 2004 14:47, Anno V.Heimburg wrote:
> --
> Program received signal SIGTERM, Terminated.
> 0x4166e082 in select () from /lib/libc so 6
> (gdb) bt
> #0  0x4166e082 in select () from /lib/libc so 6
> #1  0x4037faf0 in __JCR_LIST__ () from /usr/kde/3 2/lib/libkio so 4
> (gdb) cont
> Continuing.
>
> Program exited normally.
> (gdb) bt

  I need more than that.  You have to keep playing with it like this until it 
crashes due to SSL, then show me the trace.  Other than that there is nothing 
I can do, sorry...

Comment 10 Anno V. Heimburg 2004-02-14 12:03:51 UTC
It's getting weird - or good, depending on your point of view. Since the recompile, SSL is actually stable if the connection isn't maxed out (which is to be expected). impa/TLS is still a bit flaky, but just "connection lost", no "protocol died unexpectedly" - and I think my imap server is having TLS issues, anyway.

I have no idea what exactly fixed this, but seems like its gone. Once I have recompiled KDE w/o debug and the situation stays stable, I'll close this bug.

Thanks a lot for your time and help, and sorry for wasting it.
Comment 11 Anno V. Heimburg 2004-02-14 16:24:36 UTC
Seems okay now. Closing.