Bug 241648

Summary: konversation log in next server if the previous couldn't be accessed
Product: [Applications] konversation Reporter: marcela maslanova <marcela.maslanova>
Component: generalAssignee: Konversation Developers <konversation-devel>
Status: RESOLVED INTENTIONAL    
Severity: normal CC: hein
Priority: NOR    
Version: 1.3-beta1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description marcela maslanova 2010-06-13 14:40:48 UTC 
Version:           1.3-beta1 (using Devel) 
OS:                Linux

I set on three servers with different channels. One of servers is accessible only with vpnc. When I haven't vpnc on, then konversation try channels from not accessible server on other servers, until it finds some. Every server has defined server and channels in configuration file, therefore konversation try to be smarter than it should be. I suppose this bug is caused by automatic connection, but it shouldn't be happening on different server.

Reproducible: Always

Steps to Reproduce:
1. not accessible server1
2. accessible server2
3. add into server1 channel which could be found on server2
4. reconnect

Actual Results:  
join the channel on wrong server

Expected Results:  
don't try to join a channel on different server than it was defined.
Comment 1 Eike Hein 2010-06-13 16:43:47 UTC 
The auto-join channel list is for all servers in a network. To keep separate auto-join channel lists, set up separate networks.