Suddenly I am not able to use contact in my mail personality. I do not understand why. In terminal the message is: kontact Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kontact(7548) KDirWatch::removeDir: doesn't know "/home/hermes/.kde4/share/apps/messageviewer/themes/" kontact(7548) KDirWatch::removeDir: doesn't know "/usr/share/kde4/apps/messageviewer/themes/" json_parser - syntax error found, forcing abort, Line 1 Column 0 kontact(7548)/kdeui (kdelibs): No such XML file "/home/hermes/.kde4/share/apps/kontact/default-.rc" I can start all single components, included kmail. All mails in kmail are visible. Also organizer opens per itself. Bug when I try to start kontact, you get only the above (although kwallet askes for the password, so it comes up to that point at least (this is the working kmail component I think). Suggestions? Reproducible: Always Steps to Reproduce: 1. try to open kontact 2. does not open 3. open in terminal will give you the above. Actual Results: The start of Kontact aborts although the single coponents are startable. Expected Results: Kontact should start. This is apparently limited to this personality. But it is also true that it is this personality that receives all mail.
Created attachment 89586 [details] old kontactrc I tried to rename the kontactrc and kontact restarts again. But it appears my diaries that I did set up are gone. The kontactrc that did not start any more is the one in the attachment. In fact it seems that setting up a diary was responsible for kontact not to be able to start any more.
kontact Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) json_parser - syntax error found, forcing abort, Line 1 Column 0 kontact(31721)/kdeui (kdelibs): No such XML file "/home/hermes/.kde4/share/apps/kontact/default-.rc" I have the same Problem again. I do not understand what Kontact is complaining about as "default-.rc does not exist in any of the computers with opensuse I have. i tried to rename the whole Kontact folder to start from scratch. Still the same error. What could be the reason for this reproducible error? I found out it happened this time when i used the "task" function of Kontact. So one function does trigger it is diary, the other is task. How can I get Kontact to start again, since even with a completely new folder Kontact, the same error appears, while very single component works perfectly. Calender work, notes work, kmail works. Everything. But Kontact has this error.
This error is not only constant and repeatable, it also makes kontact completely unusable with the very same error message once you export the settings and emails to a complete new account ID. So usage of Konact is not possible any more if I do not want to loose all my data. Because of course, an empty instance of kontact without any mail and data works. (BTW, the datamigration of kontaktdata (PIM migration) is works only half way, you loose easily address book, passwords of accounts and face some other issues. If the question is: is kontact 4.14.6 complete in this sense I can give now an answer. Not yet, at least that function you will have to look at it I fear). There is not default-.rc missing in appearance. In fact, everything actually works as long as you do not shut down kontact after having adjusted the calender. I think the problem started with the import of calendar settings? But this is a guess. However, the calendar.rc is there. Defaulttodo.rc too. I have at least 5 or 6 defaultrcs in the hidden folder. So I do not understand where the issue originates. But it voids immediately any new installation. Technical help in debugging this would be really appreciated.
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.