Bug 854487

Summary:	[RFE] add timeout before joining the channels if auto identify is set up
Product:	[Fedora] Fedora	Reporter:	Martin Banas <mbanas>
Component:	konversation	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	17	CC:	kevin, rdieter, smparrish
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-05 11:05:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Banas 2012-09-05 07:10:07 UTC

Description of problem:

Automatic identify in konversation happens the same time as joining the channels. This means, that I'm not able to join channels which require identify (like #fedora).


Version-Release number of selected component (if applicable):
konversation-1.4-2.fc17.x86_64

How reproducible:
always

Steps to Reproduce:
1. Setup automatic identify in konversation to FreeNode channel
2. Setup automated connecting to #fedora channel
3. Restart the konversation
  
Actual results:
Unable to autojoin #fedora channel since user is not identified at this moment. Every time I need to manually join this channel.

Expected results:
If there was some timeout (or timeout option), or for example some rule to join the channels after automatic identify, this issue would be resolved.

Additional info:

Comment 1 Kevin Kofler 2012-09-05 11:05:17 UTC

Set nickname:password as your server password for Freenode, that way it will be sent immediately when connecting. That's a hack supported specifically by Freenode to work around this problem: http://freenode.net/faq.shtml#nicksetup point 7.

The next release of Konversation (1.5) will include an even cleaner solution for the problem: http://userbase.kde.org/Konversation/Configuring_SASL_authentication (Server-side support on Freenode is already there: http://freenode.net/faq.shtml#nocloakonjoin )