Bug 282086 - Nepomuk Service Stub crashing even when not doing anything
Summary: Nepomuk Service Stub crashing even when not doing anything
Status: RESOLVED DUPLICATE of bug 281448
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-15 14:28 UTC by Jakub Schmidtke
Modified: 2011-09-19 19:09 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jakub Schmidtke 2011-09-15 14:28:26 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.4
Operating System: Linux 3.0-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:

It doesn't feel like I am triggering this crash. I can leave the computer and come back just to see the crash dialog.
It started happening after I updated from 4.7.0 to 4.7.1, and I didn't even have any email accounts configured yet.
This crash happens several times a day.

The crash can be reproduced every time.

-- Backtrace:
Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault
[Current thread is 1 (Thread 0x7ff40d22a760 (LWP 10981))]

Thread 2 (Thread 0x7ff3fdb4a700 (LWP 10982)):
[KCrash Handler]
#6  0x00007ff40cd2788d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#7  0x00007ff40cd5391b in QEventDispatcherUNIX::activateSocketNotifiers() () from /usr/lib/libQtCore.so.4
#8  0x00007ff40cd54b93 in QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timeval*) () from /usr/lib/libQtCore.so.4
#9  0x00007ff40cd54f63 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#10 0x00007ff40cd26a92 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#11 0x00007ff40cd26c97 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0x00007ff40cc3e13f in QThread::exec() () from /usr/lib/libQtCore.so.4
#13 0x00007ff40cc40bc5 in ?? () from /usr/lib/libQtCore.so.4
#14 0x00007ff40c9b6da0 in start_thread () from /lib/libpthread.so.0
#15 0x00007ff40a6e07dd in clone () from /lib/libc.so.6
#16 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ff40d22a760 (LWP 10981)):
#0  0x00007ff4073a5300 in ?? () from /usr/lib/libsoprano.so.4
#1  0x00007ff40a644281 in ?? () from /lib/libc.so.6
#2  0x00007ff40a644305 in exit () from /lib/libc.so.6
#3  0x00007ff40ae9f938 in ?? () from /usr/lib/libQtGui.so.4
#4  0x00007ff40be1df78 in KApplication::xioErrhandler(_XDisplay*) () from /usr/lib/libkdeui.so.5
#5  0x00007ff4085a112e in _XIOError () from /usr/lib/libX11.so.6
#6  0x00007ff40859e9ad in _XEventsQueued () from /usr/lib/libX11.so.6
#7  0x00007ff40858f32f in XEventsQueued () from /usr/lib/libX11.so.6
#8  0x00007ff40aed7d16 in ?? () from /usr/lib/libQtGui.so.4
#9  0x00007ff40cd26a92 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#10 0x00007ff40cd26c97 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#11 0x00007ff40cd2aeab in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#12 0x0000000000403a89 in ?? ()
#13 0x00007ff40a62e13d in __libc_start_main () from /lib/libc.so.6
#14 0x0000000000403da9 in _start ()

Possible duplicates by query: bug 271808, bug 271682, bug 251356, bug 246930, bug 241723.

Reported using DrKonqi
Comment 1 Sebastian Trueg 2011-09-19 10:12:09 UTC
Would you mind installing kde-runtime and kdelibs debug symbols?
Comment 2 Sebastian Trueg 2011-09-19 12:46:52 UTC

*** This bug has been marked as a duplicate of bug 281448 ***
Comment 3 Jakub Schmidtke 2011-09-19 17:42:16 UTC
I wouldn't, but unfortunately there are no debug packages for Arch.
I could probably manually build those parts - would kde-runtime and kdelibs be sufficient? The problem is, I haven't seen this problem in a while.
I haven't changed anything, so I'm not sure why it stopped happening...
Comment 4 Sebastian Trueg 2011-09-19 19:09:47 UTC
(In reply to comment #3)
> I wouldn't, but unfortunately there are no debug packages for Arch.
> I could probably manually build those parts - would kde-runtime and kdelibs be
> sufficient? The problem is, I haven't seen this problem in a while.
> I haven't changed anything, so I'm not sure why it stopped happening...

Well, there is a patch for kde-runtime at bug https://bugs.kde.org/show_bug.cgi?id=257176. But if you cannot reproduce the problem anymore it does not help a lot. :P