Bug 181743 - App Akondai Resource crash when I login account OS
Summary: App Akondai Resource crash when I login account OS
Status: RESOLVED DUPLICATE of bug 180655
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: VCard file resource (show other bugs)
Version: 4.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-24 13:32 UTC by Nemanja
Modified: 2009-01-24 13:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nemanja 2009-01-24 13:32:46 UTC
Version:            (using KDE 4.1.96)
Compiler:          gcc, 4.3.2 Kubuntu 8.10 amd64
OS:                Linux
Installed from:    Ubuntu Packages

Tomorrow I try import some Vcards files to my Address Manager using app KAdressBook and then I saw this message (about 8 times).

Today when I try login in my account (KDE login) I see this message:

Application: Akonadi Resource (akonadi_vcard_resource), signal SIGABRT
0x00007fbd5d4e15f0 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7fbd611c36f0 (LWP 6448)):
[KCrash Handler]
#5  0x00007fbd5d46bfd5 in raise () from /lib/libc.so.6
#6  0x00007fbd5d46db43 in abort () from /lib/libc.so.6
#7  0x00007fbd6091c6b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007fbd6091c7fd in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007fbd60d5b577 in Akonadi::CollectionFetchJob::CollectionFetchJob () from /usr/lib/libakonadi-kde.so.4
#10 0x00007fbd60d8c8e6 in Akonadi::ItemCollectionFetchJob::doStart () from /usr/lib/libakonadi-kde.so.4
#11 0x00007fbd60d89e80 in ?? () from /usr/lib/libakonadi-kde.so.4
#12 0x00007fbd60d9e625 in ?? () from /usr/lib/libakonadi-kde.so.4
#13 0x00007fbd60da11c8 in ?? () from /usr/lib/libakonadi-kde.so.4
#14 0x00007fbd60da1319 in Akonadi::Session::qt_metacall () from /usr/lib/libakonadi-kde.so.4
#15 0x00007fbd60a21134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0x00007fbd60a2739f in ?? () from /usr/lib/libQtCore.so.4
#17 0x00007fbd60a1ba43 in QObject::event () from /usr/lib/libQtCore.so.4
#18 0x00007fbd5e11fc3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#19 0x00007fbd5e1279ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#20 0x00007fbd5f4563cb in KApplication::notify () from /usr/lib/libkdeui.so.5
#21 0x00007fbd60a0cd61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#22 0x00007fbd60a38ab6 in ?? () from /usr/lib/libQtCore.so.4
#23 0x00007fbd60a351fd in ?? () from /usr/lib/libQtCore.so.4
#24 0x00007fbd5c4a8d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0x00007fbd5c4ac50d in ?? () from /usr/lib/libglib-2.0.so.0
#26 0x00007fbd5c4ac6cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0x00007fbd60a3515f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#28 0x00007fbd5e1b1a6f in ?? () from /usr/lib/libQtGui.so.4
#29 0x00007fbd60a0b682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#30 0x00007fbd60a0b80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#31 0x00007fbd60a0dcbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#32 0x00007fbd60d93962 in Akonadi::ResourceBase::init () from /usr/lib/libakonadi-kde.so.4
#33 0x000000000040f288 in _start ()


I restart computer some times and I view this message any time.

When I closed KDE Crash Akonadi Resources app I see [b] new KDE Crash reported [/b]:

App: Ark

Report message is:

Application: Ark (ark), signal SIGSEGV
0x00007f28a27385f0 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7f28a63786f0 (LWP 6357)):
[KCrash Handler]
#5  0x000000000040d2a0 in _start ()

What can I do?
Comment 1 Dario Andres 2009-01-24 13:52:56 UTC
The Ark crash is another unrelated bug (already reported)
The Akonadi crash is reported at bug 180655 and already fixed for KDE4.2 final. So you only have to wait for 4.2 to be release from Kubuntu
Thanks

*** This bug has been marked as a duplicate of bug 180655 ***