Bug 144279 - Connect command should be performed before joining channels on reconnect
Summary: Connect command should be performed before joining channels on reconnect
Status: RESOLVED DUPLICATE of bug 132608
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.0.1
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-15 23:57 UTC by Diogo Galvão
Modified: 2007-04-16 00:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Diogo Galvão 2007-04-15 23:57:30 UTC
Version:           1.0.1 (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

When I got disconnected and it reconnects automatically, the Command for identifying is sent after joining the already opened channels (See that these are different than Auto Join).

The current scenario:

 1 - Open Konversation for the first time; it connects to Freenode, identify using the configured Command and join the channels in Auto Join. Fine;

 2 - Then I got disconnected due to an ISP problem (I was talking in some channels that keep opened);

 3 - It reconnects;

 4 - It re-joins the already opened channels;

 5 - I'm not identified yet so I'm moved to ##overflow, because one of the channels require registered nicks.

 6 - Perform that command;

And since my actual command is "/msg NickServ recover MyNick MyPassword ; /msg NickServ release MyNick MyPassword ; /nick MyNick ; /msg NickServ identify MyPassword" it fails because ##overflow is +m so I get the message "[438] MyNick ##overflow Cannot send to channel so cannot change nicks".

Thus I think that, on reconnect, the Connect command should be performed before joining the channels that were openened when I got disconnected.
Comment 1 Eike Hein 2007-04-16 00:28:26 UTC

*** This bug has been marked as a duplicate of 132608 ***