On Friday 27 October 2006 15:57, Matt Seitz wrote: > Martijn Klingens wrote: > > Are you able to confirm that the bug is still present in more recent > > Kopete versions? > > I am running Kopete 0.12.2. I thought that was the most recent version.
Oh, sorry, I missed that :) > > The Kopete developers unfortunately don't have enough manpower to > > maintain the old version, which is why Bugzilla refused the report > > That's understandable, although in this case I am running the current > version of Kopete, just on an older version of KDE. In that case, just cheat the wizard, specify the newest KDE version and mention in the report that the kopete version and the kdelibs version are different. > > In case the problem is still there with 3.5.x, things get more > > interesting. > > I'll see if I can set up another machine with 3.5.x for testing. Well, your version should be good enough, probably, it doesn't *seem* to be kdelibs-related, I entirely missed that you are running 0.12 :P > > The maintainers of the Yahoo plugin may be interested in a backtrace from > > Valgrind (instead of GDB), as it's usually more accurate with memory > > debugging. > > OK, I'll give that a try. Please do. I'm sure the Yahoo ppl can use the extra data it produces. -- Martijn Build a system that even a fool can use and only a fool will want to use it. _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
