Bug 231295

Summary:	konversation locks up at start on SSL autosigned certificate confirmation
Product:	[Applications] konversation	Reporter:	p92
Component:	general	Assignee:	Konversation Developers <konversation-devel>
Status:	RESOLVED FIXED
Severity:	normal	CC:	hein
Priority:	NOR
Version:	1.2.3
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:	1.3
Sentry Crash Report:

Description p92 2010-03-19 11:44:19 UTC

Version:           1.2.3 (using 4.4.1 (KDE 4.4.1), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.31-20-generic

I have konversation with 2 IRC network configured both with SSL encryption.

When I start konversation, a dialog appears because one SSL certificate seems autosigned and not trusted so I have to either "continue" or "cancel" the log in.

If I don't answer to this dialog quick enough within a minute or 2 then all konversation application including this dialog freezes.
When this happens, hovering the mouse on the buttons of this ssl dialog does not produce any higlighting effects anymore.

I have to kill konversation and restart it, then quickly respond to the SSL confirmation to have it work properly.

Comment 1 Eike Hein 2010-04-22 13:05:29 UTC

Current git master (i.e. the latest development code, destined to be Konversation 1.3.0) has new SSL code that should hopefully take care of this problem. Are you in a position to test-drive it to confirm on your end?

Comment 2 p92 2010-04-22 15:07:41 UTC

Hello,
I only run distribution compiled versions (kubuntu), so if I have to recompile all kde it is not possible for me. I can only test when a binary package is out.

Comment 3 Eike Hein 2010-04-22 15:19:08 UTC

You wouldn't need to compile KDE, only Konversation.

Anyhow, it will be several more weeks until we release v1.3, hopefully Kubuntu will add it to their backports repo for 10.04 then.

Comment 4 Myriam Schweingruber 2013-04-14 01:44:18 UTC

Closing for lack of feedback. Please feel free to reopen if you can reproduce this with Konversation 1.4 or 1.5 RC1 and provide the requested information.

FWIW, this was implemented in Konversation 1.3.0 already.