[EN] [solved] Kadress not working

[Lanzi]

I am running KDE 4.10 and after my last update Kadress was not runing anylonger.
SO I checked, and found out, that it was still the 4.4 Version.
So I upgrades kadress yesterday (it came with a lot of akonadifiles, kpim, Kmail, Kcontact ecc).
and I got this errormessage when starting KDE:

http://freie-software.info/Akonadi.png

Kadressbook is starting after some minutes, but has no entries at all... (quite logical after the errormessage).

What is wrong?

[Lanzi]

nobody? Or is everybody celebrating The birth of Wheezy :-)

If you need more information, let me know

[hefee]

What version of kaddressbook do you have now? 4.4 or 4.10? the version shipped with wheezy is 4.4. And with this version kadressbook moved to akonadi. See this site:
http://userbase.kde.org/Archive:Http://userbase.kde.org/Akonadi_4.4/Troubleshooting

[Lanzi]

I have 4.10 now.

Code: [Select]


apt-cache policy kaddressbook
kaddressbook:
  Installiert:           4:4.10.2-2
  Installationskandidat: 4:4.10.2-2
  Versionstabelle:
 *** 4:4.10.2-2 0
          1 http://ftp.de.debian.org/debian/ experimental/main amd64 Packages
        100 /var/lib/dpkg/status
     4:4.4.11.1+l10n-3+b1 0
        500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
        500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
root@Siduction:/home/h#



Thanks for the link - i will study it tomorrow - today its to late :-)

[hefee]

oh, you play with experimental In this case it can eat your cats. Make a backup! It is actually the first time debian switch to kdepim > 4.4 (kdepim to 4.4, was actually the same codebase than 3.5).

Make sure you use the mysql backend for akonadi and NOT sqlite:

Code: [Select]


 dpkg -l akonadi-backend*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                        Version                    Architecture               Description
+++-===========================================-==========================-======
ii  akonadi-backend-mysql                       1.9.0-0r1                  all                        MySQL storage backend for Akonadi
un  akonadi-backend-postgresql                  <none>                                                (no description available)
un  akonadi-backend-sqlite                      <none>                                                (no description available)


[DeepDayze]

oh, you play with experimental In this case it can eat your cats. Make a backup! It is actually the first time debian switch to kdepim > 4.4 (kdepim to 4.4, was actually the same codebase than 3.5).

Make sure you use the mysql backend for akonadi and NOT sqlite:

Code: [Select]


 dpkg -l akonadi-backend*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                        Version                    Architecture               Description
+++-===========================================-==========================-======
ii  akonadi-backend-mysql                       1.9.0-0r1                  all                        MySQL storage backend for Akonadi
un  akonadi-backend-postgresql                  <none>                                                (no description available)
un  akonadi-backend-sqlite                      <none>                                                (no description available)


Sqlite backend does not work for the new kdepim? Just curious

[der_bud]

Make sure you use the mysql backend for akonadi and NOT sqlite

Would be indeed interesting to know which of those works best, because since Desperado-Reloaded

"... Another change comes from our decision to change the default setup of akonadi from mysql to sqlite, as we feel, that the full set of mysql is not mandatory for the job..."

Should be reverted if sqlite is not the best choice.

[hefee]

They switched back to mysql backend for desktop systems in KDEPIM 4.8.
http://techbase.kde.org/Projects/PIM/Akonadi/Database#Backends

[DeepDayze]

While they acknowledge the shortcomings of sqlite, for personal addressbooks a local database like sqlite would not be a bad idea though rather than having a full mysql database server running on say an old machine.

[Lanzi]

okay, a feedback...

Akondai was working right. Thanks for the links to check it

I already suspected, that an upgrade of KDE to the unstable sources (instead of experimental) may fix the problem. SO when KDE 4.10.3 arrived some days ago I waited two more days, so that is was complete and did an DU today.

Everything works fine - all the contacts are back!
Thanks for your help!