Version: 0.7.2 (using KDE 3.1.0) Installed from: Mandrake Linux Cooker i586 - Cooker Compiler: gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk) OS: Linux (i686) release 2.4.21-0.13mdk kopete is almost completely unusable for me. most of the functions work, EXCEPT receiving and sending instant messages (the main function), when I push the enter key (instead of pushing the "send" button.
I also crash when I type ... in a message
Needless to say it doesn't crash for us. Can you provide us a backtrace, preferrably with debugging symbols?
Subject: Re: kopete crashes on simply sending a message Here's the backtrace. I mean, it's weird...kopete crashes a lot for me....always when I push the ENTER key to send (that's what this backtrace is from). I think it's agreat tool, and we computer 'users' are sorely in need of such a thing. Don't know why I'm having such trouble with it. Thanks. Created an attachment (id=2667) backtrace
start by disabling ALL plugins (not the protocols, just the plugins!). I bet it's the spellchecking crap. Also your backtrace is totally useless because you're missing debug-symbols. Kopete needs to be compiled with --enable-debug=full passed to configure, otherwise backtraces are empty like yours.
Subject: Re: kopete crashes on simply sending a message the spell-check sounds like a good bet. unfortuantely, kopete always crashes when i try to uncheck a plugin. where is the config file where i can disable it manually? thanks.
run kopete from commandline: kopete --noplugins
Also updating to a more recent KDE and QT would be a good idea. Problems with unloading plugins shouldn't happen anymore (it's not a kopete bug either, you would have the same problem with noatun too due to buggy libraries).
> run kopete from commandline: kopete --noplugins That will disable all the protocols, too. > where is the config file where i can disable it manually? ~/.kde/share/config/kopeterc The config file is very straightforward. Try a search for 'Plugin' if it's not immediately apparent.
I'll mark this as resolved, with the following summary: 1) the cause of one crash was pushing the <ENTER> key, instead of the gui send button. Solution: use the send button. Suggestion: Enable the <ENTER> key for sending. 2) The cause for the second crash was the spell-checker. Solution: turn off the spell-checker. Also, update KDE libraries, which are "buggy." Suggestion: please indicate, when you create the rpm, the level dependencies, so that we can tell from the output where we're deficient. 3) No backtrace. Solution: Kopete needs to be compiled with --enable-debug=full passed to configure. Suggestion: maybe you could create a "talkback" installation version, like with the mozilla alpha's, that just does the debugging compile. This is a great project, and I hope it survives. The fate of everybuddy was too bad, and we definitely need this kind of tool. Thanks!
> 1) the cause of one crash was pushing the <ENTER> key, instead of the gui > send button. Solution: use the send button. Suggestion: Enable the <ENTER> > key for sending. I think this is a serious problem if it's reproducible, and needs to be investigated further. However it's impossible to backtrace further without a backtrace. You could instead reproduce the problem when running with valgrind, which I think might locate the problem even without recompiling (can somebody confirm/deny this?). Workarounds are not a solution. > Suggestion: maybe you could create a "talkback" installation version, like > with the mozilla alpha's, that just does the debugging compile. That's what --enable-debug=full and kcrash combined essentially *are*. That will give you a full backtrace and providing that to the developers will provide them the same information. Only it leaves the talking back up to you, the user, instead of spamming the developers (which is also invasive to your privacy).
Subject: Re: kopete crashes on simply sending a message let me clarify: kopete crashes on pressing <ENTER> because of the spell-checker - so, it IS a serious problem, but just with the spell-checker plugin. i totally agree that workarounds are not a solution. which leads me to my second point: of course, we can enable the tracing functionality by compile time options, but we want this tool to be made available, and used by, the masses (don't we?). one of the hardest pills to swallow for Linux developers has always been the computer-ignorant public, but this has held Linux back, more than furthered the cause - and the cause is more important: open-source, alternative to Winders.. so, with an app like kopete, I think we nee to aim for simple, brainless, install options, which take care of the backtracing functionality under the covers - just like mozilla has done. it's just my opinion...
OK...then this is just a bug with that horrendous spellchecker plugin that causes problems for everyone...the plugin has been removed AFAIK. If you want something easy, then encourage the packagers to make versions of the packages with debug symbols compiled. Kopete supports only the source version, and makes available contributed packages. That's the responsibility of the packagers, not the Kopete team. The functionality to provide debug output is already there. Mozilla spams the developers with thousands of useless backtraces, and is still a horrid unstable product, so I don't think it's a very good comparison ;-).
I closed this wrong.
*** This bug has been marked as a duplicate of 63636 ***