Am Mittwoch, 5. September 2012 schrieb Herbert Albert:
Am Mittwoch, 5. September 2012 schrieb Sven Burmeister:
Am Mittwoch, 5. September 2012, 09:15:35 schrieb h.albert@odn.de:
nach dem gestrigen zypper up kann ich mich nicht mehr in KDE4 anleden,
weder als mein User, als demo-User noch als root. Es erscheint:
Call to lnusertemp failed (temporary directories full?). Check your
istallation.
Ggf. einfach mal /tmp leeren. Ansonsten einen neuen Benutzer anlegen und
mit dem testen. Und ein zypper verify hilft nicht aufgelöste
Abhängigkeiten zu finden.
Sven
Anscheinend gibt es einen Unterschied (ich kenne ihn nur nicht) zwischen
zypper up und Yast - Paket - Alle aktualisieren, falls neuere vorhanden.
Wenn ich letzteres durchführe wurden mir mehrere Pakte gelöschte bzw.
downgradet. Nun kann ich mich zumindest wieder anmelden. Werde mal
beobachteten was mir nun fehlt.
Herbert
Jetzt muss ich den thread doch noch einmal aufwärmen.
Durch die Aktion ist meine, zugegeben etwas setlsame, Konstellation KDE 4.7.4
mit kmail 1.13.6 aus: kmail | Paket | 4.4.10-3.2 | x86_64 | openSUSE-11.4-Oss
dahin. Bis dahin hatte ich akonadi-runtime 1.5.0-3.3 oder späder akonadi-
runtime 1.6.0-8.2 installiert.
Durch das update wurde etwas so verändert, dass ich ständig eine Fehlermeldung
vom Akonadi-Server erhalte, wenn kmail erstmalig gestartet wird (normalerweise
beim anmelden des Users)
Der Akonadi-Server hat während des letzten Starts Fehler gemeldet. Das
Protokoll kann hier gefunden werden:
/home/herbert/.local/share/akonadi/akonadiserver.error.old
Das Akonadi-Steuerprogramm hat während des letzten Starts Fehler gemeldet. Das
Protokoll kann hier gefunden werden:
/home/herbert/.local/share/akonadi/akonadi_control.error.old
Anfänglich war auch noch nein Nepomuk-Fehler dabei, doch nachdem ich nun
mehrere Versionen ausprobiert habe und nun
akonadi-runtime-1.6.0-7.4.x86_64.rpm
libakonadiprotocolinternals1-1.6.0-7.4.x86_64.rpm
libakonadi4-4.6.5-9.3.x86_64.rpm
libkdepimlibs4-4.6.5-9.3.x86_64.rpm
instaliert habe erhalte ich nur noch die beiden obigen (Akonadi Server Self-
Test Report siehe unten). quittiere die Meldung mit "Schließen" ist auch kmail
weg, starte ich danach kamil erneut läuft es einwandfrei.
Die seltsame Konstellation habe ich mir nach dem KDE-Upgrade auf 4.7
zusammengezimmert, doch ist dies schon so lange her, dass ich nicht mehr genau
weiß wie. Grund war, dass ich mit kmail2 aus 4.7 einfach nicht zurechtkam, die
Migration meiner Verzeichnisse hat einfach nicht geklappt (siehe
http://lists.opensuse.org/opensuse-de/2011-08/msg00788.html).
Ich würde ja gerne einen sauberen Schnitt machen, vielleicht mit KDE 4.8.x,
doch fürchte ich mich, nach allem was hier so geschrieben wurde, vor der
Migration nach kmail2. Ich habe ca. 60 Verzeichnisse unter "Local Folders",
davon 7 vom Typ Mailbox (darunter inbox, outbox, send und trash) und die
restlichen vom Typ Maildir. Alle Mails liegen in $HOME/Mail.
Also was ist hier ratsam, das alte Frickelsystem zu reparieren oder auf KDE
4.8.x umzusteigen mit einer guten und sicheren Anleitung der Migration zu
kmail2?
Gruß
Herbert
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/herbert/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/herbert/.local/share/akonadi/socket-
wodan/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.63 for suse-linux-gnu
on x86_64 (SUSE MySQL RPM)
Test 5: SUCCESS
--------
MySQL server log contains no errors.
Details: The MySQL server log file '<a
href='/home/herbert/.local/share/akonadi/db_data/mysql.err'>/home/herbert/.local/share/akonadi/db_data/mysql.err</a>'
does not contain any errors or warnings.
File content of '/home/herbert/.local/share/akonadi/db_data/mysql.err':
120908 13:00:29 InnoDB: Initializing buffer pool, size = 80.0M
120908 13:00:29 InnoDB: Completed initialization of buffer pool
120908 13:00:29 InnoDB: Started; log sequence number 0 153563
120908 13:00:29 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.63' socket: '/home/herbert/.local/share/akonadi/socket-
wodan/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
#
[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=utf8
collation_server=utf8_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
[client]
default-character-set=utf8
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/herbert/.local/share/akonadi/mysql.conf'>/home/herbert/.local/share/akonadi/mysql.conf</a>
and is readable.
File content of '/home/herbert/.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
#
[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=utf8
collation_server=utf8_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
[client]
default-character-set=utf8
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.5.0
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/gnome/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: ERROR
--------
Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The
log can be found in <a
href='/home/herbert/.local/share/akonadi/akonadiserver.error.old'>/home/herbert/.local/share/akonadi/akonadiserver.error.old</a>.
File content of '/home/herbert/.local/share/akonadi/akonadiserver.error.old':
D-Bus session bus went down - quitting
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: ERROR
--------
Previous Akonadi control error log found.
Details: The Akonadi control process reported errors during its previous
startup. The log can be found in <a
href='/home/herbert/.local/share/akonadi/akonadi_control.error.old'>/home/herbert/.local/share/akonadi/akonadi_control.error.old</a>.
File content of
'/home/herbert/.local/share/akonadi/akonadi_control.error.old':
D-Bus session bus went down - quitting
--
Um die Liste abzubestellen, schicken Sie eine Mail an:
opensuse-de+unsubscribe@opensuse.org
Um den Listen Administrator zu erreichen, schicken
Sie eine Mail an: opensuse-de+owner@opensuse.org