Version: (using KDE KDE 3.2.1) Installed from: Debian testing/unstable Packages Note: this is a forward of the following debian bug report, I have personally not seen it: dbug:237102 Every now and then I get the following message appearing in a new error message window : "Codice d'errore MSN non gestito 715 Invia una dettagliata segnalazione di bug, se possibile con l'ultimo output di debug della console." That, translated, would be something like: "MSN unmanaged error code 715 Send a detailed bug report, with the last console debug output, if possible." But the only thing i get from running kopete from console (and thus having the chance to see the error messages) is: "MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0 MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0 QGArray::find: Index 0 out of range" at the very start of kopete. But when that MSN plugin error appears, no other message shows on the console. cheers domi
First part is duplicate of Bug 74567 (which is FIXED btw, should be in KDE 3.2.1) Second part is duplicate of Bug 77092 Now, Bugzilla can't split this bugreport in two and mark each part as duplicate :-( Closing as duplicate of 77092 because that one is still open at the moment. Dominique: please adjust the Debian bug to refer to those two KDE bugs. In the future report only one bug at the time and search for similar bugs before reporting. I know you can :-) *** This bug has been marked as a duplicate of 77092 ***
Okay, small mistake in my previous comment: Bug 77092 was closed earlier today as INVALID.
Andy Goossens writes: > First part is duplicate of Bug 74567 (which is FIXED btw, should be > in KDE 3.2.1) Second part is duplicate of Bug 77092 > Now, Bugzilla can't split this bugreport in two and mark each part > as duplicate :-( Closing as duplicate of 77092 because that one is > still open at the moment. What you're saying sounds impossible to me. If the first part of the bug was already fixed in 3.2.1, how come this guy is still getting it on his kopete with "Version: 4:3.2.1-1". We can be pretty sure this number is accurate, as it's generated by the reportbug tool. In bug:74567, can kopete not be changed to give a more useful error ? I am inclined to reopen that bug report, really :p > Dominique: please adjust the Debian bug to refer to those two KDE > bugs. In the future report only one bug at the time and search for > similar bugs before reporting. I know you can :-) I have searched for dupes, but I guess I haven't done it thoroughly enough, cause I missed the bug :( I also did not realise the second issue was something separate. Thanks for the quick help cheers domi
On Tuesday 09 March 2004 23:19, Dominique Devriese wrote: > What you're saying sounds impossible to me. If the first part of the > bug was already fixed in 3.2.1, how come this guy is still getting it > on his kopete with "Version: 4:3.2.1-1". We can be pretty sure this > number is accurate, as it's generated by the reportbug tool. Arghhh... it wasn't fixed in 3.2.1 as it would introduce a new string. Sorry, I didn't realize that when I saw the bug was closed on 2004-02-11, which was well before the tagging of the 3.2.1 release.
Andy Goossens writes: > On Tuesday 09 March 2004 23:19, Dominique Devriese wrote: >> What you're saying sounds impossible to me. If the first part of >> the bug was already fixed in 3.2.1, how come this guy is still >> getting it on his kopete with "Version: 4:3.2.1-1". We can be >> pretty sure this number is accurate, as it's generated by the >> reportbug tool. > Arghhh... it wasn't fixed in 3.2.1 as it would introduce a new > string. Sorry, I didn't realize that when I saw the bug was closed > on 2004-02-11, which was well before the tagging of the 3.2.1 > release. Ah, I see. Thanks for your help. cheers domi
Sorry, but I installed kopete 0.8.4 over a KDE 3.2.0 and the error is still there. I did an rpm -e of the kopete package previous to install from the tgz you have on your kopete.kde.org. I don't know if this makes sense at all, because I have no info about what version is the bug solved for.