This workaround might have worked for me. I followed it, except I didn't have a Special Occasion entry in my ~/.kde/share/config/korganizerrc file. It didn't work immediately though. I then logged out after creating a new user to test the idea a new user might not be affected. The new user was affected just the same as my usual user account. When I logged back in again to my usual account, kontact started perfectly. It sure seems to be a weird problem that seems difficult to track down. I recommend trying the suggestion below, with a logout/login as a last step. It might work. Cheers, Paul. On 11 February 2010 07:49, Eli Wapniarski <eli at orbsky.homelinux.org> wrote: > OK... Current Bug Reports. A workaround follows.... > > ?https://bugzilla.redhat.com/show_bug.cgi?id=563789 > ?https://bugs.kde.org/show_bug.cgi?id=218369 > > One thing to note: On the initial startup of Kontact Akonadi seems to freeze. > All kontact related process and akonadi related process need to be killed and > then from a console or the run command, one needs to run akonadiconsole to get > things to work with the following procedure. > > Please refer to: > > https://bugs.kde.org/show_bug.cgi?id=218369 > > It would seem that if one were to go to: > > ? ?~/.kde/share/config/kontact_summary.rc > > and remove the > > ? ?kontact_specialdatesplugin > > entry. Also... > > in: > > ? ?~/.kde/share/config/korganizerrc > > I removed the : > > ? Special Occasion > > entry > > After that ... Everything seemed to work. > > Eli > > > On Wednesday 10 February 2010 22:32:39 Eli Wapniarski wrote: >> This seems to be true also with build >> >> epimlibs-devel-4.4.0-1.fc12.x86_64 >> kdepim-4.4.0-3.fc12.x86_64 >> kdepim-runtime-libs-4.4.0-1.fc12.x86_64 >> kdepimlibs-4.4.0-1.fc12.i686 >> kdepimlibs-akonadi-4.4.0-1.fc12.x86_64 >> kdepimlibs-akonadi-4.4.0-1.fc12.i686 >> kdepimlibs-4.4.0-1.fc12.x86_64 >> kdepim-libs-4.4.0-3.fc12.x86_64 >> kdepim-runtime-4.4.0-1.fc12.x86_64 >> >> Quoting Paul Scott <paulsscott at gmail.com>: >> > Hi! >> > >> > It still isn't working in 4.4.0-1: >> > >> > % kmail >> > <unknown program name>(15694)/: Communication problem with ?"kmail" , >> > 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." " >> > >> > Tried, kontackt, kmail, kaddressbook, korganizer. >> > >> > With the following installed this morning: >> > >> > kdepimlibs-devel-4.4.0-1.fc12.x86_64 >> > kdepim-runtime-libs-4.4.0-1.fc12.x86_64 >> > kdepimlibs-4.4.0-1.fc12.x86_64 >> > kdepim-4.4.0-1.fc12.x86_64 >> > kdepimlibs-akonadi-4.4.0-1.fc12.x86_64 >> > kdepim-libs-4.4.0-1.fc12.x86_64 >> > kdepimlibs-debuginfo-4.4.0-1.fc12.x86_64 >> > kdepim-debuginfo-4.4.0-1.fc12.x86_64 >> > kdepim-runtime-4.4.0-1.fc12.x86_64 >> > >> > Cheers, >> > Paul. >> > >> > On 9 February 2010 16:54, Luk?? Tinkl <ltinkl at redhat.com> wrote: >> >> Dne P? 5. ?nora 2010 10:53:24 Christos Lazaridis napsal(a): >> >>> Hi all, >> >>> >> >>> I decided to give 4.4 a try and it does feel better than the beta that >> >>> I tried and made me go back to 4.3 but I cannot get kontact to work >> >>> for me. kmail, kaddressbook, korganizer etc all work fine standalone >> >>> but kontact refuses to start. >> >>> >> >>> I made sure that akonadi is running before starting it up, removed >> >>> ?kontactrc >> >>> >> >>> and .kde/share/apps/kontact and I get messages like these in the > console: >> >>> > <unknown program name>(2118)/: Communication problem with ?"kontact" >> >>> > , 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." " >> >>> > >> >>> > kontact(2119)/khtml (caret) DOM::Selection::moveTo: Selection[ >> >>> > Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 >> >>> > "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] Position( 0x0 "null" : 0 >> >>> > ) Position( 0x0 "null" : 0 ) >> >>> >> >>> ideas? >> >>> >> >>> thanks, >> >>> ? Christos. >> >> >> >> Known problem, our KDE will have this patched. >> >> >> >> -- >> >> Luk?? Tinkl <ltinkl at redhat.com> >> >> Software Engineer - Base Operating Systems Brno >> >> KDE developer <lukas at kde.org> >> >> Red Hat Inc. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? http://cz.redhat.com >> >> _______________________________________________ >> >> kde mailing list >> >> kde at lists.fedoraproject.org >> >> https://admin.fedoraproject.org/mailman/listinfo/kde >> >> New to KDE4? - get help from http://userbase.kde.org >> > >> > -- >> > Paul Scott >> > paulsscott at gmail.com >> > _______________________________________________ >> > kde mailing list >> > kde at lists.fedoraproject.org >> > https://admin.fedoraproject.org/mailman/listinfo/kde >> > New to KDE4? - get help from http://userbase.kde.org >> > -- >> > This message has been scanned for viruses and >> > dangerous content by MailScanner, and is >> > believed to be clean. > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > kde mailing list > kde at lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/kde > New to KDE4? - get help from http://userbase.kde.org -- Paul Scott paulsscott at gmail.com Sent from Karlstad, Sweden
