Version: 0.12.1 (using KDE 3.5.3, Gentoo) Compiler: Target: i686-pc-linux-gnu OS: Linux (i686) release 2.6.17-gentoo-r3 Hi, using the mentioned kopete version, I'm sometimes having problems starting kopete. As soon as it starts up (I used ALT+F2) the system no longer accepts keyboard input. Other applications like kontact don't start up either (I can still use the mouse and start kontact with it). Clicking around reveils that CTRL seems to be send by the keyboard. It isn't another program but kopete, sshing into the machine and killing kwalletmanager etc didn't help. Only killing kopete gives me the system back, kontact starts, kwalletmanager asks about my password and everything works again. I still don't know how to reproduce this behaviour reliable. But it already appeared several times - also with an older version of kopete.
What are your loaded plugin ? Try to disable each plugin, and seeif it is a plugin which is causing this.
Installed are only "KopeTex", "cryptography" and "history". All three were active. I just deactivated them and kopete crashed after getting a new message... Well, after restarting it, the system showed the behaviour above. Restarted KDE. Starting Kopete again didn't bring it up but also didn't block the system. But killing the kopete process in the background immediatly showed the kwalletmanager-inputwindow for the waiting kontact. Again starting kopete showed again the behaviour above. :-( Only after starting kopete for the fourth time (again: always without any modules/plugins activated) it worked. Can it be that it has something to do with kwallet?
I've experienced the same things a few times with Kopete 0.11.3 and the history and statistics modules activated. Kopete grabs all keyboard input and prevents some apps to start (Kmail for example). Killing kopete gives the hand back. I don't know how to reproduce it for the moment.
This could be related to kwallet, yes. are you configured to connect automatically ? Try to see if this is hapenning at connect time, or at startup time.
No, I'm not connecting automatically. But I just experienced another effect. Kopete was already running in the systray after booting (therefore offline) and I already worked for some time. Then I wanted to go online and pressed "CTRL+SHIFT+S" to get kopete in the foreground and immediatly my keyboard was grabbed and unuseable. Killing kopete and restarting it worked and I was able to go online and also got my keyboard back.
It seems to be impossible to restart kopete within this KDE session. I quit kopete since I was leaving this network. After beeing again inside a network I started kopete. It didn't appear in the systray and after pressing CTRL-SHIFT-S the keyboard was grabbed but kopete didn't show. It doesn't matter if I'm starting it by ALT+F2 or with the konsole. No messages are printed onto the {k|c}onsole. I have to restart KDE to get kopete to work again. :-(
@Olivier/Kopeteteam: Can I do sth. to help you identifying this problem? @Vincent/Users: Anybody who can confirm this, too? Vincent: do you still have this problem?
Still valid in 0.12.2
Marcel: Are you using the KAddressbook Integration by chance? We've seen some weird DCOP issues with that stuff. Also, a log from strace might help here as well, if you could attach that to the bug report, that'd be great.
Hi Matt, thanks for answering. Meanwhile I'm using 0.12.5 and the problem seems to be gone away... At least the problem didn't show up for some time. And indeed, I tried to integrate kopete and kadressbook (hoping, some day everything will work automagically ;) ). But currently I'm still using this linkage - I didn't change anything within my contact list. Since I'm not able to provoke this error and reproduce the behaviour I'm marking this bug as RESOLVED. As soon as it occurs again I will try to get a strace and reopen, ok?