Bug 328968 - K0ntact stopped due to Akonadi
Summary: K0ntact stopped due to Akonadi
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-12-18 15:33 UTC by Ian Powell
Modified: 2014-01-27 02:01 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Error dialogue from Kontact (152.48 KB, image/png)
2013-12-18 15:40 UTC, Ian
Details
Akonadi self test error file (30.73 KB, text/plain)
2013-12-18 15:42 UTC, Ian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Powell 2013-12-18 15:33:32 UTC
Application: kontact (4.11.4)
KDE Platform Version: 4.11.4
Qt Version: 4.8.5
Operating System: Linux 3.7.10-1.16-desktop x86_64
Distribution: "openSUSE 12.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Just loading the Kontact to view my emails
Akonadi not starting autoamtically or manually due not be able to register with DBUS

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f341c2597c0 (LWP 6081))]

Thread 4 (Thread 0x7f3416f9a700 (LWP 6082)):
#0  0x00007f342af0f964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f342e63a770 in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f342e63a7a9 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x00007f342af0be0f in start_thread () from /lib64/libpthread.so.0
#4  0x00007f3430d6d44d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f33d6677700 (LWP 6083)):
#0  0x00007f342af0f964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f342e3b6f47 in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f342e661c9e in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x00007f342af0be0f in start_thread () from /lib64/libpthread.so.0
#4  0x00007f3430d6d44d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f33c41b2700 (LWP 6104)):
#0  0x00007f342a994831 in ?? () from /usr/lib64/libglib-2.0.so.0
#1  0x00007f342a994a69 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f342a957343 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f342a9579cb in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x00007f342a957bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#5  0x00007f34314e45d6 in QEventDispatcherGlib::processEvents (this=0x7f33bc0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#6  0x00007f34314b4bef in QEventLoop::processEvents (this=this@entry=0x7f33c41b1dc0, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f34314b4e78 in QEventLoop::exec (this=0x7f33c41b1dc0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f34313b7110 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:536
#9  0x00007f34313ba0ec in QThreadPrivate::start (arg=0xda0540) at thread/qthread_unix.cpp:338
#10 0x00007f342af0be0f in start_thread () from /lib64/libpthread.so.0
#11 0x00007f3430d6d44d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f341c2597c0 (LWP 6081)):
[KCrash Handler]
#6  activateInitialPluginModule (this=0xa814e0) at /usr/src/debug/kdepim-4.11.4/kontact/src/mainwindow.cpp:329
#7  Kontact::MainWindow::activateInitialPluginModule (this=0xa814e0) at /usr/src/debug/kdepim-4.11.4/kontact/src/mainwindow.cpp:324
#8  0x00000000004040ca in KontactApp::newInstance (this=0x7fff1d0cd770) at /usr/src/debug/kdepim-4.11.4/kontact/src/main.cpp:148
#9  0x00007f3432bd82f2 in KUniqueApplicationAdaptor::newInstance (this=0xa7c010, asn_id=..., args=...) at /usr/src/debug/kdelibs-4.11.4/kdeui/kernel/kuniqueapplication.cpp:442
#10 0x00007f3432bd8374 in qt_static_metacall (_a=0x7fff1d0cc9b0, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at /usr/src/debug/kdelibs-4.11.4/build/kdeui/kuniqueapplication_p.moc:57
#11 KUniqueApplicationAdaptor::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=0x7fff1d0cc9b0) at /usr/src/debug/kdelibs-4.11.4/build/kdeui/kuniqueapplication_p.moc:51
#12 0x00007f3432bd84ab in KUniqueApplicationAdaptor::qt_metacall (this=0xa7c010, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff1d0cc9b0) at /usr/src/debug/kdelibs-4.11.4/build/kdeui/kuniqueapplication_p.moc:101
#13 0x00007f34300e8e2a in QDBusConnectionPrivate::deliverCall (this=this@entry=0xa5a250, object=object@entry=0xa7c010, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:951
#14 0x00007f34300e9fa5 in QDBusConnectionPrivate::activateCall (this=this@entry=0xa5a250, object=0xa7c010, flags=flags@entry=337, msg=...) at qdbusintegrator.cpp:863
#15 0x00007f34300ea916 in QDBusConnectionPrivate::activateObject (this=0xa5a250, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1427
#16 0x00007f34300eaa0b in QDBusActivateObjectEvent::placeMetaCall (this=0xd38ac0) at qdbusintegrator.cpp:1541
#17 0x00007f34314ca92e in QObject::event (this=0x7fff1d0cd770, e=<optimized out>) at kernel/qobject.cpp:1203
#18 0x00007f3431ec1a34 in QApplication::event (this=0x7fff1d0cd770, e=0xd38ac0) at kernel/qapplication.cpp:2544
#19 0x00007f3431ebf92c in QApplicationPrivate::notify_helper (this=this@entry=0xa76db0, receiver=receiver@entry=0x7fff1d0cd770, e=e@entry=0xd38ac0) at kernel/qapplication.cpp:4562
#20 0x00007f3431ec3dab in QApplication::notify (this=0x7fff1d0cd770, receiver=0x7fff1d0cd770, e=0xd38ac0) at kernel/qapplication.cpp:4423
#21 0x00007f3432bd2016 in KApplication::notify (this=0x7fff1d0cd770, receiver=0x7fff1d0cd770, event=0xd38ac0) at /usr/src/debug/kdelibs-4.11.4/kdeui/kernel/kapplication.cpp:311
#22 0x00007f34314b5f3e in QCoreApplication::notifyInternal (this=0x7fff1d0cd770, receiver=receiver@entry=0x7fff1d0cd770, event=event@entry=0xd38ac0) at kernel/qcoreapplication.cpp:949
#23 0x00007f34314b98a1 in sendEvent (event=0xd38ac0, receiver=0x7fff1d0cd770) at kernel/qcoreapplication.h:231
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9e42b0) at kernel/qcoreapplication.cpp:1573
#25 0x00007f34314e4423 in sendPostedEvents () at kernel/qcoreapplication.h:236
#26 postEventSourceDispatch (s=0xa6bf70) at kernel/qeventdispatcher_glib.cpp:280
#27 0x00007f342a9577d5 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#28 0x00007f342a957b08 in ?? () from /usr/lib64/libglib-2.0.so.0
#29 0x00007f342a957bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#30 0x00007f34314e45b6 in QEventDispatcherGlib::processEvents (this=0x9e9710, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#31 0x00007f3431f5fe0e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#32 0x00007f34314b4bef in QEventLoop::processEvents (this=this@entry=0x7fff1d0cd5e0, flags=...) at kernel/qeventloop.cpp:149
#33 0x00007f34314b4e78 in QEventLoop::exec (this=0x7fff1d0cd5e0, flags=...) at kernel/qeventloop.cpp:204
#34 0x00007f34314b9bb8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#35 0x0000000000403679 in main (argc=1, argv=0x7fff1d0cd8b8) at /usr/src/debug/kdepim-4.11.4/kontact/src/main.cpp:219

Possible duplicates by query: bug 324131, bug 323845, bug 322264, bug 315612, bug 315104.

Reported using DrKonqi
Comment 1 Ian 2013-12-18 15:40:40 UTC
Created attachment 84160 [details]
Error dialogue from Kontact

THis is displayed when you press <Details> on the fail screen presented in Kontact
Comment 2 Ian 2013-12-18 15:42:47 UTC
Created attachment 84161 [details]
Akonadi self test error file

error file from Akonadi during attempt to start due Kontact loading up
Comment 3 Ian 2013-12-18 15:46:26 UTC
THis error is random. You can sometimes log out of your KDE session and back in again and it will sometimes work.
You can also sometimes unload a working Kontact session and it might restart okay or it might not. 
It has also made the log off process a lot slower, it doesn;t matter if Kontact worked or not.
Comment 4 Russ Fineman 2013-12-18 16:55:15 UTC
same issues as Ian. Mine occur on openSUSE 13.1 (3.11.6-4-desktop) and on openSUSE 12.3 (3.11.1-3.gfeffbf9-desktop). Very random on 13.1, almost allways on 12.3. This started happening about 10-21-2013 after some updates to system and kde.
Comment 5 Russ Fineman 2013-12-20 17:53:37 UTC
(In reply to comment #4)
> same issues as Ian. Mine occur on openSUSE 13.1 (3.11.6-4-desktop) and on
> openSUSE 12.3 (3.11.1-3.gfeffbf9-desktop). Very random on 13.1, almost
> allways on 12.3. This started happening about 10-21-2013 after some updates
> to system and kde.

System ran all day yesterday. Shut Down Last night and this morning Kmail would not start. Tried procedure described by Roger Oberholtzer on mailing list (opensuse-kde. (12-15-2013 11:19 PM))
I think the message ID is: <52AEA965.10106@opq.se>.

Start up messages and errors are at:
CODE
----------
 http://paste.opensuse.org/34513492
---------
Comment 6 Ian 2013-12-20 18:13:20 UTC
Upgraded to KDE 4.12 - not fixed
Upgraded to opensuse 13.1 adn kde 4.12 - still no change
Comment 7 Ian 2013-12-21 10:30:41 UTC
Just wish i could update the Severity from Normal to Critical.  Seems if you post a bug via Dr Konqy, you can't set an "Importance" value on it, you stuck with what ever DrKonqy puts on it
Comment 8 George Baltz 2013-12-22 15:52:24 UTC
What video card are you using?  I had an error dialog just like the above (MySQL log contains errors, Akonadi * process not registered at DBus) when using the new nVidia driver 331.20 (on 12.3). Look here(http://forums.opensuse.org/english/get-technical-help-here/applications/493649-opensuse-12-3-nvidia-akonadi-nepomuk-error.html) and at the nvidia linux support site(https://devtalk.nvidia.com/default/topic/659230/331-20-on-x86_64-breaks-signal-processing-/) for more info.
Comment 9 Ian 2013-12-23 11:23:32 UTC
I'm using Nvidia as well.  I've checked this bug 326480 which appears to be related and there are comments in the list where people have downgraded their Nvidia release and they are suffering the same problem so is it related to all releases of Nvidia or just coincidence?
Comment 10 George Baltz 2013-12-23 16:07:12 UTC
On Monday, December 23, 2013 11:23:32 AM you wrote:
> https://bugs.kde.org/show_bug.cgi?id=328968
> 
> --- Comment #9 from Ian <ianseeks@yahoo.co.uk> ---
> I'm using Nvidia as well.  I've checked this bug 326480 which appears to be
> related and there are comments in the list where people have downgraded
> their Nvidia release and they are suffering the same problem so is it
> related to all releases of Nvidia or just coincidence?

I looked at that related bug, and at the changelog descriptions of the various 
Nvidia driver releases. One of the responders said he went back to 319.60, and 
still had the problem; if I were a betting man, I would bet that one of the 
changes mentioned in the 319.60 release is the source of the problem: "Fixed a 
bug that could cause OpenGL applications to crash during the initialization of 
new threads".  The pthread interface is the crux of the problem.

I downgraded my system to 319.32, and no problems since then. If I get some 
time, I'll load the 319.49 driver and narrow down the range of the problem.
Comment 11 Ian 2014-01-26 17:53:37 UTC
Please close.

Failure has gone away due to removing Nvidia driver and using "nv".  Apparently new version of nvidia drivers seem to have cured the problem
Comment 12 Russ Fineman 2014-01-26 18:11:16 UTC
I agree this should be closed by who ever is authorized to do it. openSUSE 13.1 and the new Nvidia 331-38 driver appear to have solved it (at least for my GeForce 8400 GS card..