Akonadi Server Probleme

Hallo,

ich habe mir vorgestern OpenSuse 11.3 mit KDE zum ersten Mal auf meinem Computer installiert. *Bin also noch ein kompletter Frischling. *Eigentlich komme ich aber gut mit allen Programmen und auch den Einstellungen klar.

Für die Verwaltung wollte ich nun Kontact benutzen und dort Adressen und E-Mail Konten einrichten.

Leider meldet sich dort der Akonadi Server (von dem ich nicht weiß, was er genau macht und wozu ich ihn brauche) mit folgender Fehlermeldung:

Akonadi Server Self-Test Report

Test 1: SUCCESS

Database driver found.
Details: The QtSQL driver ‘QMYSQL’ is required by your current Akonadi server configuration and was found on your system.

File content of ‘/home/yentl/.config/akonadi/akonadiserverrc’:
%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

[QMYSQL]
Name=akonadi
Host=
User=
Password=
Options=“UNIX_SOCKET=/home/yentl/.local/share/akonadi/db_misc/mysql.socket”
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null

Test 2: SUCCESS

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3: SUCCESS

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server ‘/usr/sbin/mysqld’.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called ‘mysqld’; its location varies depending on the distribution.

Test 4: SUCCESS

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.46 for suse-linux-gnu on i686 (SUSE MySQL RPM)

Test 5: SUCCESS

MySQL server log contains no errors.
Details: The MySQL server log file ‘<a href=’/home/yentl/.local/share/akonadi/db_data/mysql.err’>/home/yentl/.local/share/akonadi/db_data/mysql.err</a>’ does not contain any errors or warnings.

File content of ‘/home/yentl/.local/share/akonadi/db_data/mysql.err’:
101121 12:18:19 [Note] Plugin ‘ndbcluster’ is disabled.
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
101121 12:18:20 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait…
101121 12:18:20 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 64 MB
InnoDB: Database physically writes the file full: wait…
101121 12:18:22 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 64 MB
InnoDB: Database physically writes the file full: wait…
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
101121 12:18:24 InnoDB: Started; log sequence number 0 0
101121 12:18:25 [Note] /usr/sbin/mysqld: ready for connections.
Version: ‘5.1.46-log’ socket: ‘/home/yentl/.local/share/akonadi/db_misc/mysql.socket’ port: 0 SUSE MySQL RPM

Test 6: SUCCESS

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href=‘/etc/akonadi/mysql-global.conf’>/etc/akonadi/mysql-global.conf</a>.

File content of ‘/etc/akonadi/mysql-global.conf’:

Global Akonadi MySQL server settings,

These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf

Based on advice by Kris Köhntopp <kris@mysql.com>

[mysqld]
skip_grant_tables
skip_networking

strict query parsing/interpretation

TODO: make Akonadi work with those settings enabled

#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables

use InnoDB for transactions and better crash recovery

default_storage_engine=innodb

case-insensitive table names, avoids trouble on windows

lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0

error log file name, relative to datadir

log_error=mysql.err
log_warnings=2

log all queries, useful for debugging but generates an enormous amount of data

#log=mysql.full

log queries slower than n seconds, log file name relative to datadir (for debugging only)

#log_slow_queries=mysql.slow
#long_query_time=1

log queries not using indices, debug only, disable for production use

#log_queries_not_using_indexes=1

maximum blob size

max_allowed_packet=32M
max_connections=256

makes sense when having the same query multiple times

makes no sense with prepared statements and/or transactions

query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M

messure database size and adjust

SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in (“mysql”, “information_schema”);

innodb_buffer_pool_size=80M

size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like “inno%”, show global variables)

innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2

Do not drop the connection to the DB after 8 hours of inactivity

wait_timeout=1296000

Test 7: SKIP

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 8: SUCCESS

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href=‘/home/yentl/.local/share/akonadi/mysql.conf’>/home/yentl/.local/share/akonadi/mysql.conf</a> and is readable.

File content of ‘/home/yentl/.local/share/akonadi/mysql.conf’:

Global Akonadi MySQL server settings,

These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf

Based on advice by Kris Köhntopp <kris@mysql.com>

[mysqld]
skip_grant_tables
skip_networking

strict query parsing/interpretation

TODO: make Akonadi work with those settings enabled

#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables

use InnoDB for transactions and better crash recovery

default_storage_engine=innodb

case-insensitive table names, avoids trouble on windows

lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0

error log file name, relative to datadir

log_error=mysql.err
log_warnings=2

log all queries, useful for debugging but generates an enormous amount of data

#log=mysql.full

log queries slower than n seconds, log file name relative to datadir (for debugging only)

#log_slow_queries=mysql.slow
#long_query_time=1

log queries not using indices, debug only, disable for production use

#log_queries_not_using_indexes=1

maximum blob size

max_allowed_packet=32M
max_connections=256

makes sense when having the same query multiple times

makes no sense with prepared statements and/or transactions

query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M

messure database size and adjust

SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in (“mysql”, “information_schema”);

innodb_buffer_pool_size=80M

size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like “inno%”, show global variables)

innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2

Do not drop the connection to the DB after 8 hours of inactivity

wait_timeout=1296000

Test 9: SUCCESS

akonadictl found and usable
Details: The program ‘/usr/bin/akonadictl’ to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.3.1

Test 10: SUCCESS

Akonadi control process registered at D-Bus.
Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational.

Test 11: SUCCESS

Akonadi server process registered at D-Bus.
Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational.

Test 12: ERROR

Nepomuk search service not registered at D-Bus.
Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 13: SKIP

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

Test 14: SUCCESS

Resource agents found.
Details: At least one resource agent has been found.

Directory listing of ‘/usr/share/akonadi/agents’:
birthdaysresource.desktop
contactsresource.desktop
icalresource.desktop
imapresource.desktop
kabcresource.desktop
kcalresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mtdummyresource.desktop
nepomukcalendarfeeder.desktop
nepomukcontactfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to ‘/usr/share:/etc/opt/kde3/share:/opt/kde3/share’

Test 15: SUCCESS

No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.

Test 16: SUCCESS

No previous Akonadi server error log found.
Details: The Akonadi server did not report any errors during its previous startup.

Test 17: SUCCESS

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

Test 18: SUCCESS

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.

Leider sind das für mich noch böhmische Dörfer und ich würde mich freuen, wenn jemand sich in diesem Fall meiner annehmen würde.

Danke,

Yentl

P.S. Habe versucht akonadi-runtime 1.40 zum Herunterladen zu finden, denn ich habe in einem andren Thread gelesen, dass könne eventuell helfen, aber ich wurde nicht fündig.

Wieso wunderst Du Dich ueber so viele “SUCCESS” Meldungen? Ist doch alles in Ordnung.

Nein, ist es leider nicht, denn wenn ich KAddressBook aufrufen möchte, dann erhalte ich einen grauen Hintergrund und die Meldung, dass der Akonadi Server-Dienst nicht einwandfrei arbeitet und ich kann auf das Adressbuch nicht zugreifen. Bei dieser Fehlermeldung erscheint ein zweiter Link über die Details, die ich hier noch einmal hinterlegen möchte - ausserdem sind nicht alle Meldungen Success in der obigen Meldung (z.B. Test 12)

Akonadi Server Self-Test Report

Test 1: SUCCESS

Database driver found.
Details: The QtSQL driver ‘QMYSQL’ is required by your current Akonadi server configuration and was found on your system.

File content of ‘/home/yentl/.config/akonadi/akonadiserverrc’:
%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

[QMYSQL]
Name=akonadi
Host=
User=
Password=
Options=“UNIX_SOCKET=/home/yentl/.local/share/akonadi/db_misc/mysql.socket”
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null

Test 2: SUCCESS

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3: SUCCESS

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server ‘/usr/sbin/mysqld’.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called ‘mysqld’; its location varies depending on the distribution.

Test 4: SUCCESS

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.46 for suse-linux-gnu on i686 (SUSE MySQL RPM)

Test 5: SUCCESS

MySQL server log contains no errors.
Details: The MySQL server log file ‘<a href=’/home/yentl/.local/share/akonadi/db_data/mysql.err’>/home/yentl/.local/share/akonadi/db_data/mysql.err</a>’ does not contain any errors or warnings.

File content of ‘/home/yentl/.local/share/akonadi/db_data/mysql.err’:
101121 12:18:19 [Note] Plugin ‘ndbcluster’ is disabled.
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
101121 12:18:20 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait…
101121 12:18:20 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 64 MB
InnoDB: Database physically writes the file full: wait…
101121 12:18:22 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 64 MB
InnoDB: Database physically writes the file full: wait…
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
101121 12:18:24 InnoDB: Started; log sequence number 0 0
101121 12:18:25 [Note] /usr/sbin/mysqld: ready for connections.
Version: ‘5.1.46-log’ socket: ‘/home/yentl/.local/share/akonadi/db_misc/mysql.socket’ port: 0 SUSE MySQL RPM

Test 6: SUCCESS

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href=‘/etc/akonadi/mysql-global.conf’>/etc/akonadi/mysql-global.conf</a>.

File content of ‘/etc/akonadi/mysql-global.conf’:

Global Akonadi MySQL server settings,

These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf

Based on advice by Kris Köhntopp <kris@mysql.com>

[mysqld]
skip_grant_tables
skip_networking

strict query parsing/interpretation

TODO: make Akonadi work with those settings enabled

#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables

use InnoDB for transactions and better crash recovery

default_storage_engine=innodb

case-insensitive table names, avoids trouble on windows

lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0

error log file name, relative to datadir

log_error=mysql.err
log_warnings=2

log all queries, useful for debugging but generates an enormous amount of data

#log=mysql.full

log queries slower than n seconds, log file name relative to datadir (for debugging only)

#log_slow_queries=mysql.slow
#long_query_time=1

log queries not using indices, debug only, disable for production use

#log_queries_not_using_indexes=1

maximum blob size

max_allowed_packet=32M
max_connections=256

makes sense when having the same query multiple times

makes no sense with prepared statements and/or transactions

query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M

messure database size and adjust

SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in (“mysql”, “information_schema”);

innodb_buffer_pool_size=80M

size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like “inno%”, show global variables)

innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2

Do not drop the connection to the DB after 8 hours of inactivity

wait_timeout=1296000

Test 7: SKIP

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 8: SUCCESS

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href=‘/home/yentl/.local/share/akonadi/mysql.conf’>/home/yentl/.local/share/akonadi/mysql.conf</a> and is readable.

File content of ‘/home/yentl/.local/share/akonadi/mysql.conf’:

Global Akonadi MySQL server settings,

These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf

Based on advice by Kris Köhntopp <kris@mysql.com>

[mysqld]
skip_grant_tables
skip_networking

strict query parsing/interpretation

TODO: make Akonadi work with those settings enabled

#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables

use InnoDB for transactions and better crash recovery

default_storage_engine=innodb

case-insensitive table names, avoids trouble on windows

lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0

error log file name, relative to datadir

log_error=mysql.err
log_warnings=2

log all queries, useful for debugging but generates an enormous amount of data

#log=mysql.full

log queries slower than n seconds, log file name relative to datadir (for debugging only)

#log_slow_queries=mysql.slow
#long_query_time=1

log queries not using indices, debug only, disable for production use

#log_queries_not_using_indexes=1

maximum blob size

max_allowed_packet=32M
max_connections=256

makes sense when having the same query multiple times

makes no sense with prepared statements and/or transactions

query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M

messure database size and adjust

SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in (“mysql”, “information_schema”);

innodb_buffer_pool_size=80M

size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like “inno%”, show global variables)

innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2

Do not drop the connection to the DB after 8 hours of inactivity

wait_timeout=1296000

Test 9: SUCCESS

akonadictl found and usable
Details: The program ‘/usr/bin/akonadictl’ to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.3.1

Test 10: SUCCESS

Akonadi control process registered at D-Bus.
Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational.

Test 11: SUCCESS

Akonadi server process registered at D-Bus.
Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational.

Test 12: ERROR

Nepomuk search service not registered at D-Bus.
Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 13: ERROR

Server protocol version is too old.
Details: The server protocol version is 23, but at least version 26 is required. Install a newer version of the Akonadi server.

Test 14: SUCCESS

Resource agents found.
Details: At least one resource agent has been found.

Directory listing of ‘/usr/share/akonadi/agents’:
birthdaysresource.desktop
contactsresource.desktop
icalresource.desktop
imapresource.desktop
kabcresource.desktop
kcalresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mtdummyresource.desktop
nepomukcalendarfeeder.desktop
nepomukcontactfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to ‘/usr/share:/etc/opt/kde3/share:/opt/kde3/share’

Test 15: SUCCESS

No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.

Test 16: SUCCESS

No previous Akonadi server error log found.
Details: The Akonadi server did not report any errors during its previous startup.

Test 17: SUCCESS

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

Test 18: SUCCESS

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.

Gruß,

Yentl

Welche KDE Version benutzt du? Du brauchst eine neuere Akonadiversion.
Öffne den Yast Softwaremanager/Konfiguration/Repositories und trage dort folgendes Repo ein:

Index of /repositories/KDE:/Release:/45/openSUSE_11.3

Da bekommst du die stabile KDE Version 4.5.3 und damit sollte es klappen.

Viel Glück
Hans

Soweit ich das sehen kann treten 2 Fehler auf:

> Test 12: ERROR
> --------
>
> Nepomuk search service not registered at D-Bus.
> Details: The Nepomuk search service is not registered at D-Bus which
> typically means it was not started or encountered a fatal error during
> startup.

Probier mal:
Systemeinstellungen -> Desktopsuche

Nepomuk-Semantik-Dienste aktivieren

und falls das nicht hilft bzw schon aktiviert ist:
Strigi-Datei-Indexer aktivieren

>
> Test 13: ERROR
> --------
>
> Server protocol version is too old.
> Details: The server protocol version is 23, but at least version 26 is
> required. Install a newer version of the Akonadi server.

Hast du eine alte Version von akonadi-runtime installiert? Das würde diesen
Fehler erklären.

Zur Info:
Akonadi wird benutzt im deine ganzen Kontakte und Termine zu speichern.

Hallo Ihr Beiden,

danke für Eure Hilfestellung. Das Repository, dass Hans angegeben hat, ist bei mir bereits vorhanden. Dort gibt es keine neuere Version.

Dank des Hinweises von Fruchtratte funktioniert nun auch Nepomuk korrekt.

Allerdings habe ich noch immer den älteren Akonadi Server da, den ich selber nicht installiert habe, der wurde wohl mit eingerichtet, als ich den Computer mit Suse 11.3 aufgesetzt habe.

In meinen Repositories taucht kein neuerer auf, auf der angegebenen Website gibt es nur rmp Dateien, die sich nicht installieren lassen, da nicht für diese Konfiguration gedacht, so die Fehlermeldung.

Wenn ich versuche akonadi-runtime 1.4.0 wie verlangt zu finden, dann bekomme ich auch über die Datenkrake kein Ergebnis, das funktioniert angezeigt. Habe sogar schon unstable und factory Repositories eingebunden, aber da ist er auch nicht zu finden.

Mir fehlt jetzt einfach ‘nur’ noch der Link zum richtigen Repository, denke ich.

Versuche nochmals die Aktualisierungen durchlaufen zu lassen. Mehr fällt mir nicht ein.

Yentl

Akonadi-runtime ist in der Version 1.4.1-2.1 in dem Dir genannten Repo enthalten.
Gerade noch einmal nachgeschaut. Ist das Repo aktualisiert? Mal den Reiter “Versionen” angeklickt?
(Ich habe sogar Version 1.4.1-40.1. Keine Ahnung wo die herkommt :O, ist aber ein anderes Thema. Funktioniert jedenfalls.)

Dietger

On Mon, 22 Nov 2010 01:06:03 +0530, StreisandMagazin
<StreisandMagazin@no-mx.forums.opensuse.org> wrote:

> Wenn ich versuche akonadi-runtime 1.4.0 wie verlangt zu finden, dann
> bekomme ich auch über die Datenkrake kein Ergebnis, das funktioniert
> angezeigt. Habe sogar schon unstable und factory Repositories
> eingebunden, aber da ist er auch nicht zu finden.

ich fürchte, daß sich da bei irgendwelchen libraries unpassende versionen
eingeschlichen haben. es ist gar keine gute idee, etwas von KDE unstable
oder factory in ein system zu installieren, das ansonsten auf stable oder
release/45 beruht.

zuerst wäre es interessant zu sehen, welche repos du zur zeit installiert
hast, also das ergebnis von “zypper lr -u” zum beispiel.

danach würde ich vermutlich vorschlagen, im YAST software manager das KDE
release/45 repo auszuwählen und “alle pakete auf dieses repo umstellen”
anklicken. (weiß nicht, wie das auf deutsch wirklich heißt.)

aber besser erstmal die liste aller aktiven repos anschauen.


phani.

Na ja, wenn man Nepomuk haben will, schon … aber es wird doch nicht von kaddressbook und kmail gebraucht, jedenfalls nicht zum Starten. Deswegen dachte ich mir, dass Test 12: ERROR unbedeutend war. Test 13: ERROR dagegen nicht.

Genau. Zeigt mal bitte zuerst das Ergenis von: zypper lr

  • @phani, sorry, ich habe ueberlesen, dass Du den richtigen Befehl schon gegeben hattest. Uebrigens kannst Du auch im Deutschen ae statt ä, ue statt ü schreiben. Jedenfalls tue ich das gern (habe auch keine deutsche Tastatur).

:wink:

So auch schon phanisvara: NNTP-Test (charset=ISO-8859-1) : ß und ä,ö,ü/Ä,Ö,Ü. (#post2256178 oder #2 des dortigen Threads).

LG
pistazienfresser

@please try again

Ich hab festgestellt, das die Übersichtsseite von Kontact nicht richtig
funktioniert, wenn Strigi nicht läuft. (Genauer: Die nächsten Geburtstage
von meinen Kontakten werden nicht angezeigt.)

Aber ja, hast Recht. Sollte auch zumindest starten ohne sich zu beschweren.

Ich hab festgestellt, das die Übersichtsseite von Kontact nicht richtig
funktioniert, wenn Strigi nicht läuft. (Genauer: Die nächsten Geburtstage
von meinen Kontakten werden nicht angezeigt.)

Danke für den Hinweis :wink:
Jetzt werden endlich auch die Geburtstage meiner Kontakte angezeigt. War schon kurz vorm ausrasten.
Auf Strigi als Ursache wäre ich nicht gekommen.

Dietger