[Konversation-devel] [Bug 147976] New: "lost" chans when bouncer miau plays backlog and reaches an own disconnect/reconnect

[Nils Kneuper]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=147976         
           Summary: "lost" chans when bouncer miau plays backlog and reaches
                    an own disconnect/reconnect
           Product: konversation
           Version: unspecified
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: konversation-devel kde org
        ReportedBy: crazy-ivanovic gmx net


Version:           1.0.1+ #3210 svn-rev: 689476 (using KDE KDE 3.5.7)
Installed from:    Gentoo Packages
Compiler:          gcc-Version 4.1.2 (Gentoo 4.1.2) CXXFLAGS=-march=nocona -O2 -pipe -g
OS:                Linux

My bouncer is on a normal DSL line with a 24h disconnect. When I connect to the bouncer after such a reconnect has happened, the backlog is replayed until the disconnect, most of the chans vanish and are not "recreated". Only the "last" chan in the list stays there and is not lost. Eg i have this list of chans: #wesnoth, #wesnoth-de, #wesnoth-dev and #konversation active on my bouncer, when connecting to it in the morning shortly all open, then alls but #konversation are closed again, in #konversation the complete backlog of the night is available, when looking at the plain logfiles I see that logging for all the other chans stopped when reaching the disconnect in the backlog.
The chan #konversation is just one example in this case, when not connected to #konversation, too, then #wesnoth-dev is the only one "active" after the reconnects.

This problem did already exist in 1.0.1, too, there it sometimes came together with a crash (cf bug #145614) but that crash seems to have been solved in svn.

There is no real problem when being logged in into the bouncer when the reconnect happens, only when the backlog is replayed.

Some system/bouncer data:
I am running konversation from svn rev 689476 (that is version 1.0.1+ #3210).
My bouncer is miau, version 0.6.4 running on a slug/nslu2 (version from the unslug package manager ipkg: miau 0.6.4-1).

Do you need any more information?