| Summary: | "lost" chans when bouncer miau plays backlog and reaches an own disconnect/reconnect | ||
|---|---|---|---|
| Product: | [Applications] konversation | Reporter: | Nils Kneuper <crazy-ivanovic> |
| Component: | general | Assignee: | Konversation Developers <konversation-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | hein |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
configuration file for miau (the bouncer in question)
A ralog where I forced to create such a problem Rawlog of Konversation having the problem corresponding debug log from miau, including all traffic (in and out) |
||
|
Description
Nils Kneuper
2007-07-18 14:50:03 UTC
Okay, today I had 5 instead of only 4 chans open and all beside the servertab were lost. So it seems to not be possible to tell exactly which chans might be lost... what's chandiscon set to in your miaurc? If it's set to part try setting it to something else. It was set to the default value, I will now try to set it to "nothing", I hope this works nicely. If it does I will tell the miau dev to change to comment to not only mention mirc but also konversation in that list. (Of course I will report back in here if it does work nicely then) No, this change did not help, still exactly the same problem even though I did change chandiscon from 'part' to 'nothing'. Created attachment 21220 [details]
configuration file for miau (the bouncer in question)
This bouncer config might help to reproduce the problems. I have the impression
that quite some traffic has to take place after a disconnect of the bouncer so
that the chans are lost when attaching to the bouncer.
I did change all nickname/passwddata, the rest is identical to my config.
Created attachment 21348 [details]
A ralog where I forced to create such a problem
Okay, I did now "force" the problem to occur. This is what I have done:
*Detach the bouncer
*Force a reconnect to the server but "resetting" my dsl line which results in a
serverdisconnect because of a changed IP
*Create some traffic in the chans I was in (some chat was taking place in
#wesnoth-dev, some in #konversation)
*After about 1:30 after the server reconnect: reattach the bouncer in
konversation with active rawlog and copy the rawlog to a file that is now
attached in here
In the file I only changed the passwords, the rest is an unchanged rawlog.
Forgot to mention: The last line of log konversation has in it's own "normal" log files is that one, everything afterwards is not in there: [15:45:19] >> :Ivanovic!n=ivanovic@pD9EC3CD9.dip0.t-ipconnect.de QUIT :[14:27:26] Read error: 110 (Connection timed out) Created attachment 21363 [details]
Rawlog of Konversation having the problem
I will attach two corresponding logs, one of Konversation while replaying the
backlog (and have the tabs vanish) and one from miau including all the traffic
it had that night.
Created attachment 21364 [details]
corresponding debug log from miau, including all traffic (in and out)
Is this still an issue for you with current versions of miau and Konversation? Nope, the issue is fixed by now. Thanks for getting back to us! |