[Akonadi] [Bug 320757] New: CalDAV Calender not shown anymore. Tasks only partly.

[Arthur Schiwon]

https://bugs.kde.org/show_bug.cgi?id=320757

            Bug ID: 320757
           Summary: CalDAV Calender not shown anymore. Tasks only partly.
    Classification: Unclassified
           Product: Akonadi
           Version: 4.10
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: DAV Resource
          Assignee: kdepim-bugs at kde.org
          Reporter: blizzz at arthur-schiwon.de

Fresh and clean setup of KDEPIM 4.10.2.
I added a CalDAV calender resource (serverd by my ownCloud 4.5). In the wizard,
I chose genered CalDAV and configured everything myself.
Meanwhile I upgraded to 4.10.3. It's already some weeks ago.

What happens now is that my calenders (5 calenders in my CalDAV resource) are
not shown. To be more precise: they are shown in the resource list, but no
appointment is displayed (and there should be lots).

In the Tasks/Todo View, also all ToDos vanished. Yesterday I added additional
ones (via ownCloud), they do appear in Kontact. Old ones do not,  however.

There are odd Error messages in the log files (see additional information).

Reproducible: Always

Steps to Reproduce:
1. configure CalDAV resource
2. use it
3. after some days or so see described issues
Actual Results:  
- CalDAV Calendars not shown
- CalDAV Todos only shown partly

Expected Results:  
- CalDAV Calendars  shown
- CalDAV Todos  shown fully

Log mysql.err (Akonadi internal DB. Never touched it.)

130605 11:02:56 [Note] Plugin 'FEDERATED' is disabled.
130605 11:02:56 InnoDB: The InnoDB memory heap is disabled
130605 11:02:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130605 11:02:56 InnoDB: Compressed tables use zlib 1.2.7
130605 11:02:56 InnoDB: Using Linux native AIO
130605 11:02:56 InnoDB: Initializing buffer pool, size = 80.0M
130605 11:02:56 InnoDB: Completed initialization of buffer pool
130605 11:02:56 InnoDB: highest supported file format is Barracuda.
130605 11:03:00  InnoDB: Waiting for the background threads to start
130605 11:03:01 InnoDB: 5.5.31 started; log sequence number 388069446
130605 11:03:01 [Warning] Can't open and lock time zone table: Table
'mysql.time_zone_leap_second' doesn't exist trying to live without them
130605 11:03:01 [ERROR] Can't open and lock privilege tables: Table
'mysql.servers' doesn't exist
130605 11:03:01 [ERROR] Native table
'performance_schema'.'events_waits_current' has the wrong structure
130605 11:03:01 [ERROR] Native table
'performance_schema'.'events_waits_history' has the wrong structure
130605 11:03:01 [ERROR] Native table
'performance_schema'.'events_waits_history_long' has the wrong structure
130605 11:03:01 [ERROR] Native table 'performance_schema'.'setup_consumers' has
the wrong structure
130605 11:03:01 [ERROR] Native table 'performance_schema'.'setup_instruments'
has the wrong structure
130605 11:03:01 [ERROR] Native table 'performance_schema'.'setup_timers' has
the wrong structure
130605 11:03:01 [ERROR] Native table 'performance_schema'.'performance_timers'
has the wrong structure
130605 11:03:01 [ERROR] Native table 'performance_schema'.'threads' has the
wrong structure
130605 11:03:01 [ERROR] Native table
'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the
wrong structure
130605 11:03:01 [ERROR] Native table
'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
130605 11:03:01 [ERROR] Native table
'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong
structure
130605 11:03:01 [ERROR] Native table
'performance_schema'.'file_summary_by_event_name' has the wrong structure
130605 11:03:01 [ERROR] Native table
'performance_schema'.'file_summary_by_instance' has the wrong structure
130605 11:03:01 [ERROR] Native table 'performance_schema'.'mutex_instances' has
the wrong structure
130605 11:03:01 [ERROR] Native table 'performance_schema'.'rwlock_instances'
has the wrong structure
130605 11:03:01 [ERROR] Native table 'performance_schema'.'cond_instances' has
the wrong structure
130605 11:03:01 [ERROR] Native table 'performance_schema'.'file_instances' has
the wrong structure
130605 11:03:01 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.31-0ubuntu0.13.04.1'  socket:
'/home/blizzz/.local/share/akonadi/socket-zara/mysql.socket'  port: 0  (Ubuntu)

Log akonadiserver.error (looks like Nepomuk or what forgets parts of resource
configurations??):

Nepomuk Query Server not available 
"Cannot connect to agent instance with identifier
'akonadi_davgroupware_resource_2', error message: 'Could not get owner of name
'org.freedesktop.Akonadi.Resource.akonadi_davgroupware_resource_2': no such
name'" 
ItemRetrieverException :  Unable to contact resource 
Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( (
PimItemTable.id = :1 ) )" :  "Deadlock found when trying to get lock; try
restarting transaction QMYSQL3: Unable to execute statement" 
Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( (
PimItemTable.id = :1 ) )" :  "Deadlock found when trying to get lock; try
restarting transaction QMYSQL3: Unable to execute statement"

-- 
You are receiving this mail because:
You are the assignee for the bug.