[kde-de] Kalender - Wochentagsansicht (Arbeitswoche) verschwunden (KDE 4.9)?
huq
hans-ulrich.queitsch at gmx.de
Mi Sep 19 19:44:14 UTC 2012
Hi,
Guten Abend
bin bisher (seit sechs, acht oder vielleicht auch schon 10 Jahren) mit KDE gut
gefahren
ausdrücklichen Dank dafür an die Entwickler und Tester
viele Dinge sind in kde 4.6, 4.8, 4.9 immer besser geworden
aber im Moment hab ich viel Frust mit KDE
bei SUSE 11.x lief kontact noch sauber (bis Mitte Juli)
dann update auf SUSE 12.1
Adressbook und Kmail liefen auch
in Korganizer war keine Termine zu sehen und
das Eintragen von Terminen im Korganizer nicht möglich
aber meine alten, importierten Termine waren in der Übersicht zu sehen
bisschen gegoogelt
update auf SUSE 12.2 und teilweise zusätzlich auf (SUSE-)KDE4.9
(sollte helfen)
(gelesen, getan)
inzwischen kann ich auch neue Termine erfassen (!),
aber die sind immer noch nicht im Korganizer,
aber wie bisher nur in der Übersicht sichtbar
bei aller Freude (und auch Frust) am PC,
der Kalender ist mir nun schon wichtig geworden
vielleicht weiß jemand, wie sich das bereinigen lässt
... und kde3 ist wohl keine echte Alternative
vielen Dank im Voraus
uli
auch so, ja
meinen Konfiguration
Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz
intel Q35
Linux 3.4.6-2.10-default i686
KDE: 4.8.5 (4.8.5) "release 2", z.T. 4.9
und der test:
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/xxxx/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/xxx/.local/share/akonadi/socket-
enterprise/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.5.25a for Linux on i686
(Source distribution)
Test 5: SUCCESS
--------
MySQL server log contains no errors.
Details: The MySQL server log file '<a
href='/home/xxx/.local/share/akonadi/db_data/mysql.err'>/home/xxx/.local/share/akonadi/db_data/mysql.err</a>'
does not contain any errors or warnings.
File content of '/home/xxx/.local/share/akonadi/db_data/mysql.err':
120919 18:17:11 InnoDB: The InnoDB memory heap is disabled
120919 18:17:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120919 18:17:11 InnoDB: Compressed tables use zlib 1.2.7
120919 18:17:11 InnoDB: Initializing buffer pool, size = 80.0M
120919 18:17:11 InnoDB: Completed initialization of buffer pool
120919 18:17:12 InnoDB: highest supported file format is Barracuda.
120919 18:17:15 InnoDB: Waiting for the background threads to start
120919 18:17:16 InnoDB: 1.1.8 started; log sequence number 110226877
120919 18:17:17 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.25a' socket: '/home/xxx/.local/share/akonadi/socket-
enterprise/mysql.socket' port: 0 Source distribution
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 at mysql.com>
#
[mysqld]
# 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
# DEBUGGING:
# 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
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM
information_schema.tables WHERE table_schema not in ("mysql",
"information_schema");
# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show
global status like "inno%", show global variables)
#expire_logs_days=3
#sync_bin_log=0
# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# memory pool InnoDB uses to store data dictionary information and other
internal data structures (default:1M)
innodb_additional_mem_pool_size=1M
# memory buffer InnoDB uses to cache data and indexes of its tables
(default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M
# Create a .ibd file for each table (default:0)
innodb_file_per_table=1
# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2
# Buffer size used to write to the log files on disk (default:1M for builtin,
8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M
# Size of each log file in a log group (default:5M) larger means less I/O but
more time for recovery.
innodb_log_file_size=64M
# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err
# print warnings and connection errors (default:1)
log_warnings=2
# Convert table named to lowercase
lower_case_table_names=1
# Maximum size of one packet or any generated/intermediate string.
(default:1M)
max_allowed_packet=32M
# Maximum simultaneous connections allowed (default:100)
max_connections=256
# The two options below make no sense with prepared statements and/or
transactions
# (make sense when having the same query multiple times)
# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0
# Do not cache results (default:1)
query_cache_type=0
# Do not use the privileges mechanisms
skip_grant_tables
# Do not listen for TCP/IP connections at all
skip_networking
# The number of open tables for all threads. (default:64)
table_cache=200
# How many threads the server should cache for reuse (default:0)
thread_cache_size=3
# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000
[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/xxx/.local/share/akonadi/mysql.conf'>/home/uli/.local/share/akonadi/mysql.conf</a>
and is readable.
File content of '/home/xxx/.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 at mysql.com>
#
[mysqld]
# 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
# DEBUGGING:
# 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
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM
information_schema.tables WHERE table_schema not in ("mysql",
"information_schema");
# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show
global status like "inno%", show global variables)
#expire_logs_days=3
#sync_bin_log=0
# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# memory pool InnoDB uses to store data dictionary information and other
internal data structures (default:1M)
innodb_additional_mem_pool_size=1M
# memory buffer InnoDB uses to cache data and indexes of its tables
(default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M
# Create a .ibd file for each table (default:0)
innodb_file_per_table=1
# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2
# Buffer size used to write to the log files on disk (default:1M for builtin,
8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M
# Size of each log file in a log group (default:5M) larger means less I/O but
more time for recovery.
innodb_log_file_size=64M
# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err
# print warnings and connection errors (default:1)
log_warnings=2
# Convert table named to lowercase
lower_case_table_names=1
# Maximum size of one packet or any generated/intermediate string.
(default:1M)
max_allowed_packet=32M
# Maximum simultaneous connections allowed (default:100)
max_connections=256
# The two options below make no sense with prepared statements and/or
transactions
# (make sense when having the same query multiple times)
# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0
# Do not cache results (default:1)
query_cache_type=0
# Do not use the privileges mechanisms
skip_grant_tables
# Do not listen for TCP/IP connections at all
skip_networking
# The number of open tables for all threads. (default:64)
table_cache=200
# How many threads the server should cache for reuse (default:0)
thread_cache_size=3
# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000
[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.7.2
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: SUCCESS
--------
Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically
indicates it is operational.
Test 13: SUCCESS
--------
Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.
Test 14: 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 15: SUCCESS
--------
Resource agents found.
Details: At least one resource agent has been found.
Directory listing of '/usr/share/akonadi/agents':
akonadinepomukfeederagent.desktop
akonotesresource.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
microblog.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.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 16: SUCCESS
--------
No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current
startup.
Test 17: 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/xxx/.local/share/akonadi/akonadiserver.error.old'>/home/uli/.local/share/akonadi/akonadiserver.error.old</a>.
File content of '/home/xxx/.local/share/akonadi/akonadiserver.error.old':
Control process died, committing suicide!
Test 18: SUCCESS
--------
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its
current startup.
Test 19: SUCCESS
--------
No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its
previous startup.
Am Samstag, 15. September 2012, 14:29:33 schrieb Sebastian Voitzsch:
> Hallo,
>
> ich habe seit längerer Abstinenz mal wieder KDE ausprobiert und muss sagen,
> 4.9 gefällt mir bisher sehr gut!
>
> Allerdings vermisse ich in Kontact die Möglichkeit, im Kalender nur die
> "Arbeitswoche" anstatt der vollen Woche (d.h., nur die Tage Mo-Fr) anzeigen
> zu lassen. Ist diese Option so gut versteckt, dass ich sie nicht gefunden
> habe, oder ist sie entfallen?
>
> Danke,
> Sebastian
>
> --
> _______________________________________________
> kde-de mailing list
> kde-de at kde.org
> kde-de Admin: sebastian at voitzsch.net
> Abmelden? Mailadresse ändern? ->
> https://mail.kde.org/mailman/listinfo/kde-de
Mehr Informationen über die Mailingliste kde-de