Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 460448 - kde-base/nepomuk-4.10.1 - Nepomuk service crashed on start
Summary: kde-base/nepomuk-4.10.1 - Nepomuk service crashed on start
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-05 21:30 UTC by Alex Barker
Modified: 2013-07-05 20:01 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Barker 2013-03-05 21:30:25 UTC
I dont have a whole lot of information on this other than the backtrace.  Application cashed on start-up after rebooting.  Stack trace was sent up stream via in app bug reporting utility.

Reproducible: Sometimes

Steps to Reproduce:
I am not sure this if this is reproducible.  I will run Nepomuk Cleaner and monitor to see if it pops up again.
Actual Results:  
Application: Nepomuk Service Stub (nepomukservicestub), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe7407b1780 (LWP 3481))]

Thread 3 (Thread 0x7fe739146700 (LWP 3960)):
[KCrash Handler]
#6  0x00000031cba37ba5 in raise () from /lib64/libc.so.6
#7  0x00000031cba3901b in abort () from /lib64/libc.so.6
#8  0x0000003ef3abbc7d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libstdc++.so.6
#9  0x0000003ef3ab9e36 in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libstdc++.so.6
#10 0x0000003ef3ab9e63 in std::terminate() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libstdc++.so.6
#11 0x0000003ef3aba87f in __cxa_pure_virtual () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libstdc++.so.6
#12 0x0000003ef48c24b8 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#13 0x0000003ef48d0003 in QAbstractSocket::setSocketDescriptor(int, QAbstractSocket::SocketState, QFlags<QIODevice::OpenModeFlag>) () from /usr/lib64/qt4/libQtNetwork.so.4
#14 0x0000003ef48dfe21 in QLocalSocket::setSocketDescriptor(unsigned long long, QLocalSocket::LocalSocketState, QFlags<QIODevice::OpenModeFlag>) () from /usr/lib64/qt4/libQtNetwork.so.4
#15 0x00007fe73b809cd3 in ?? () from /usr/lib64/libsopranoserver.so.1
#16 0x00007fe73b8061e7 in ?? () from /usr/lib64/libsopranoserver.so.1
#17 0x0000003ef3e8205c in ?? () from /usr/lib64/qt4/libQtCore.so.4
#18 0x00000031cc608ec6 in start_thread () from /lib64/libpthread.so.0
#19 0x00000031cbaea7fd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fe738945700 (LWP 3961)):
#0  0x00000031cbae74f9 in syscall () from /lib64/libc.so.6
#1  0x0000003ef3e80afb in ?? () from /usr/lib64/qt4/libQtCore.so.4
#2  0x0000003ef3e7c8fd in QMutex::lockInternal() () from /usr/lib64/qt4/libQtCore.so.4
#3  0x0000003ef48c28a7 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#4  0x0000003ef48cd703 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#5  0x0000003ef48b858a in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#6  0x0000003ef48b91d4 in QNetworkProxy::QNetworkProxy() () from /usr/lib64/qt4/libQtNetwork.so.4
#7  0x0000003ef48d1a6f in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#8  0x0000003ef48d640e in QTcpSocket::QTcpSocket(QObject*) () from /usr/lib64/qt4/libQtNetwork.so.4
#9  0x0000003ef48deeb5 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#10 0x0000003ef48d8b5e in QLocalSocket::QLocalSocket(QObject*) () from /usr/lib64/qt4/libQtNetwork.so.4
#11 0x00007fe73b809cb8 in ?? () from /usr/lib64/libsopranoserver.so.1
#12 0x00007fe73b8061e7 in ?? () from /usr/lib64/libsopranoserver.so.1
#13 0x0000003ef3e8205c in ?? () from /usr/lib64/qt4/libQtCore.so.4
#14 0x00000031cc608ec6 in start_thread () from /lib64/libpthread.so.0
#15 0x00000031cbaea7fd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fe7407b1780 (LWP 3481)):
#0  0x00000031cbae74f9 in syscall () from /lib64/libc.so.6
#1  0x0000003ef3e80afb in ?? () from /usr/lib64/qt4/libQtCore.so.4
#2  0x0000003ef3e7c8fd in QMutex::lockInternal() () from /usr/lib64/qt4/libQtCore.so.4
#3  0x0000003ef48c28a7 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#4  0x0000003ef48cd703 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#5  0x0000003ef48ba4d8 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#6  0x00000031cba3a6c9 in ?? () from /lib64/libc.so.6
#7  0x00000031cba3a755 in exit () from /lib64/libc.so.6
#8  0x000000371ce466c8 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#9  0x00007fe740d3a518 in KApplication::xioErrhandler(_XDisplay*) () from /usr/lib64/libkdeui.so.5
#10 0x00000031cd64760e in _XIOError () from /usr/lib64/libX11.so.6
#11 0x00000031cd64509d in _XEventsQueued () from /usr/lib64/libX11.so.6
#12 0x00000031cd6366af in XEventsQueued () from /usr/lib64/libX11.so.6
#13 0x000000371ce7d9cc in ?? () from /usr/lib64/qt4/libQtGui.so.4
#14 0x00000031cee49103 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#15 0x00000031cee49596 in ?? () from /usr/lib64/libglib-2.0.so.0
#16 0x00000031cee49724 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#17 0x0000003ef3fb113f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#18 0x000000371ce7db8e in ?? () from /usr/lib64/qt4/libQtGui.so.4
#19 0x0000003ef3f80d92 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#20 0x0000003ef3f80fe7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#21 0x0000003ef3f85db5 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#22 0x0000000000404499 in ?? ()
#23 0x00000031cba2460d in __libc_start_main () from /lib64/libc.so.6
#24 0x00000000004047c1 in _start ()
Comment 1 Johannes Huber (RETIRED) gentoo-dev 2013-07-05 19:33:38 UTC
Is this fixed for you with current stable 4.10.4 or testing 4.10.5?
Comment 2 Alex Barker 2013-07-05 19:54:06 UTC
I have been running 4.10.4 and have not had the problem reappear.  We can close this bug for now and reopen if it comes back.
Comment 3 Johannes Huber (RETIRED) gentoo-dev 2013-07-05 20:01:51 UTC
(In reply to Alex Barker from comment #2)
> I have been running 4.10.4 and have not had the problem reappear.  We can
> close this bug for now and reopen if it comes back.

Thanks for the feedback.