[Bug 257460] New: Akonadi will not sync / import previously working ical resource

[John Murphy]

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

           Summary: Akonadi will not sync / import previously working ical
                    resource
           Product: Akonadi
           Version: unspecified
          Platform: openSUSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: murphyjj at bigpond.net.au


Application: akonadi_kcal_resource (0.1)
KDE Platform Version: 4.5.76 (4.6 >= 20101111) "release 4"
Qt Version: 4.7.1
Operating System: Linux 2.6.34.7-0.5-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
Upgrade seemed to lose previously working ical resource.
Adding it through Akonadi configuration wizard seems to work.
Akonadi Console seems to show a number of entries exist for the the resource.
but it does not work.
Using Akonadi Console Browser for the ical resource seems OK and if copied show
- 
akonadi:?item=69872&type=application%2Fx-vnd.akonadi.calendar.event
akonadi:?item=69873&type=application%2Fx-vnd.akonadi.calendar.event
The calendar seems to look ok - but shows no events and if an event is added
Korganizer crashes immediately.
In fact any type of use of the Korganizer or from within Kontact causes a
crash.
Great shame - have everying else working.
Kontact version 4.6 pre on KDE 4.5.76 (4.6 >= 20101111) "release 4"
openSuse 11.3 X64 from SC Distro

-- Backtrace:
Application: Akonadi Resource (akonadi_kcal_resource), signal: Aborted
[Current thread is 1 (Thread 0x7fe3af9d1760 (LWP 2878))]

Thread 2 (Thread 0x7fe3974d4710 (LWP 8329)):
#0  0x00007fe3ab434660 in __pthread_mutex_unlock_usercnt () from
/lib64/libpthread.so.0
#1  0x00007fe3aa95e3d5 in g_main_context_query () from
/usr/lib64/libglib-2.0.so.0
#2  0x00007fe3aa95eedb in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fe3aa95f510 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x00007fe3aeebba06 in QEventDispatcherGlib::processEvents (this=0x9f35b0,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#5  0x00007fe3aee90192 in QEventLoop::processEvents (this=<value optimized
out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007fe3aee903a5 in QEventLoop::exec (this=0x7fe3974d3de0, flags=...) at
kernel/qeventloop.cpp:201
#7  0x00007fe3aeda30d4 in QThread::exec (this=<value optimized out>) at
thread/qthread.cpp:490
#8  0x00007fe3aee71848 in QInotifyFileSystemWatcherEngine::run (this=0xb2eb30)
at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007fe3aeda594e in QThreadPrivate::start (arg=0xb2eb30) at
thread/qthread_unix.cpp:285
#10 0x00007fe3ab430a4f in start_thread () from /lib64/libpthread.so.0
#11 0x00007fe3ac88682d in clone () from /lib64/libc.so.6
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fe3af9d1760 (LWP 2878)):
[KCrash Handler]
#6  0x00007fe3ac7e89e5 in raise () from /lib64/libc.so.6
#7  0x00007fe3ac7e9ee6 in abort () from /lib64/libc.so.6
#8  0x00007fe3acdebcdd in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib64/libstdc++.so.6
#9  0x00007fe3acde9ef6 in ?? () from /usr/lib64/libstdc++.so.6
#10 0x00007fe3acde9f23 in std::terminate() () from /usr/lib64/libstdc++.so.6
#11 0x00007fe3acdea076 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6
#12 0x00007fe3aee90473 in QEventLoop::exec (this=0x7ffffbdad620, flags=...) at
kernel/qeventloop.cpp:214
#13 0x00007fe3aee9480b in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1009
#14 0x00007fe3af505a62 in Akonadi::ResourceBase::init (r=0x7a1760) at
/usr/src/debug/kdepimlibs-4.5.76svn1195572/akonadi/resourcebase.cpp:283
#15 0x000000000040e488 in _start ()

This bug may be a duplicate of or related to bug 232879, bug 222283, bug
226608, bug 238029, bug 244016.

Possible duplicates by query: bug 256946, bug 256838, bug 256837, bug 256820,
bug 255169.

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.