[Konversation-devel] [Bug 241648] New: konversation log in next server if the previous couldn't be accessed

marcela maslanova marcela.maslanova at gmail.com
Sun Jun 13 14:40:51 CEST 2010


https://bugs.kde.org/show_bug.cgi?id=241648

           Summary: konversation log in next server if the previous
                    couldn't be accessed
           Product: konversation
           Version: 1.3-beta1
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: konversation-devel at kde.org
        ReportedBy: marcela.maslanova at gmail.com


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.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the Konversation-devel mailing list