Version: 1.0.0 (using KDE 4.4.4) OS: Linux When i start kopete, if akonadi is already running, kopete will only show a grey window and do nothing else. To make it work i have to run the akonadi conf dialog, then click on stop akonadi, then run kopete and at this point the akonadi daemon will be automatically executed again. Reproducible: Always OS: Linux (x86_64) release 2.6.34.1-vulcano Compiler: cc
This is happening to me too: Qt: 4.7.0 Plataforma de desarrollo de KDE: 4.6.00 (4.6.0) Kopete: 1.0.80 strace -f kopete (last messages): [pid 4359] write(2, "kopete(4359): Communication prob"..., 353kopete(4359): Communication problem with "kopete" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " ) = 353 [pid 4359] exit_group(255) = ? The "Did not receive a reply. Possible causes blah blah blah" bit is, incidentally, the same error message that I get trying to get akonadi running with Google Calendar, so I think it may be related or even the same bug than https://bugs.kde.org/show_bug.cgi?id=264861 (which I'm also experiencing).
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!