Bug 185479 - /usr/bin/nepomukservicestub nepomukstrigiservice segmentation faults
Summary: /usr/bin/nepomukservicestub nepomukstrigiservice segmentation faults
Status: RESOLVED FIXED
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-24 22:52 UTC by Orion Poplawski
Modified: 2009-11-18 15:01 UTC (History)
7 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 Orion Poplawski 2009-02-24 22:52:10 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Fedora RPMs

Seeing several of these a day:

Feb 24 12:37:22 berretto kernel: nepomukservices[3577] general protection
ip:3970856c2e sp:7fff57aa7420 error:0 in libQtCore.so.4.4.3[3970800000+21e000]

on almost all of our Fedora 10 machines.  May be x86_64 only.  cores are ending
up in ~/Documents.

Core was generated by `/usr/bin/nepomukservicestub nepomukstrigiservice'.
Program terminated with signal 11, Segmentation fault.
[New process 3560]
#0  QThread::d_func () at thread/qthread.h:125
125         Q_DECLARE_PRIVATE(QThread)
(gdb) bt
#0  QThread::d_func () at thread/qthread.h:125
#1  QThread::isRunning (this=0xff70000000000f7) at thread/qthread.cpp:403
#2  0x000000000085ba26 in Nepomuk::IndexScheduler::stop
(this=0xff70000000000f7)
    at
/usr/src/debug/kdebase-runtime-4.2.0/nepomuk/services/strigi/indexscheduler.cpp:150
#3  0x0000000000859d7e in ~StrigiService (this=0xbc1400)
    at
/usr/src/debug/kdebase-runtime-4.2.0/nepomuk/services/strigi/strigiservice.cpp:90
#4  0x000000397094fc31 in QObjectPrivate::deleteChildren (this=0xbae850)
    at kernel/qobject.cpp:1884
#5  0x00000039709589f7 in ~QObject (this=0xbb0410) at kernel/qobject.cpp:884
#6  0x0000000000403cc1 in ~ServiceControl (this=0xbb0410)
    at
/usr/src/debug/kdebase-runtime-4.2.0/nepomuk/servicestub/servicecontrol.cpp:39
#7  0x000000397094fc31 in QObjectPrivate::deleteChildren (this=0xae90d0)
    at kernel/qobject.cpp:1884
#8  0x00000039709589f7 in ~QObject (this=0x7fff465c9390) at
kernel/qobject.cpp:884
#9  0x0000003f1e78be61 in ~QApplication (this=0x7fff465c9390)
    at kernel/qapplication.cpp:1044
#10 0x00000000004035dc in main (argc=2, argv=0x7fff465c9738)
    at /usr/src/debug/kdebase-runtime-4.2.0/nepomuk/servicestub/main.cpp:149
(gdb) up
#1  QThread::isRunning (this=0xff70000000000f7) at thread/qthread.cpp:403
403         Q_D(const QThread);
(gdb) print QThread
Cannot access memory at address 0xff70000000000f7


(gdb) up
#4  0x000000397094fc31 in QObjectPrivate::deleteChildren (this=0xbae850)
    at kernel/qobject.cpp:1884
1884            delete currentChildBeingDeleted;
(gdb) print currentChildBeingDeleted
$2 = (QObject *) 0xbc1400
(gdb) print *currentChildBeingDeleted
$3 = {_vptr.QObject = 0xa6b150, static staticMetaObject = {d = {superdata =
0x0,
      stringdata = 0x39709cc740 "QObject", data = 0x39709cc7c0, extradata =
0x0}},
  d_ptr = 0xbf3ee0, static staticQtMetaObject = {d = {superdata = 0x0,
      stringdata = 0x39709d5980 "Qt", data = 0x39709d7620, extradata = 0x0}}}
(gdb) print *this
$4 = {<QObjectData> = {_vptr.QObjectData = 0x3970c23730, q_ptr = 0xbb0410,
    parent = 0x7fff465c9390, children = {{p = {static shared_null = {ref = {
              _q_value = 375}, alloc = 0, begin = 0, end = 0, sharable = 1,
            array = {0x0}}, d = 0xbf4030}, d = 0xbf4030}}, isWidget = 0,
    pendTimer = 0, blockSig = 0, wasDeleted = 1, ownObjectName = 0,
    sendChildEvents = 1, receiveChildEvents = 1, inEventHandler = 0,
    unused = 17664, postedEvents = 0}, pendingChildInsertedEvents = {{p = {
        static shared_null = {ref = {_q_value = 375}, alloc = 0, begin = 0,
          end = 0, sharable = 1, array = {0x0}}, d = 0x605820}, d = 0x605820}},
  threadData = 0xad7b50, currentSender = 0x0, currentChildBeingDeleted =
0xbc1400,
  eventFilters = {{p = {static shared_null = {ref = {_q_value = 375}, alloc =
0,
          begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0x605820},
      d = 0x605820}}, extraData = 0x0, connectedSignals = 17, objectName = {
    static null = {<No data fields>}, static shared_null = {ref = {_q_value =
138},
      alloc = 0, size = 0, data = 0x3970c26d9a, clean = 0, simpletext = 0,
      righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array =
{0}},
    static shared_empty = {ref = {_q_value = 41}, alloc = 0, size = 0,
      data = 0x3970c26dba, clean = 0, simpletext = 0, righttoleft = 0,
      asciiCache = 0, capacity = 0, reserved = 0, array = {0}}, d =
0x3970c26d80,
    static codecForCStrings = 0x0}, connectionLists = 0x0, senders = {{p = {
        static shared_null = {ref = {_q_value = 375}, alloc = 0, begin = 0,
          end = 0, sharable = 1, array = {0x0}}, d = 0x605820}, d = 0x605820}},
  deleteWatch = 0x0}

Version-Release number of selected component (if applicable):
kdebase-runtime-4.2.0-7.fc10.x86_64
qt-4.4.3-10.fc10.x86_64
Comment 1 Sebastian Trueg 2009-02-27 16:12:32 UTC
this looks like a crash on exit. I need more details on the problem. What does it occur?
Comment 2 Orion Poplawski 2009-02-27 16:18:42 UTC
It appears to occur either just before log out or just after log in.  Not 100% of the time though.
Comment 3 Jonathan Thomas 2009-03-12 13:47:17 UTC
It's a login crash, according to our bug at https://launchpad.net/bugs/341654
But then again it could have crashed at logout but only been reported by apport at the next login.
Comment 4 Kevin Kofler 2009-03-14 21:13:54 UTC
I think this is a bug in the way the Strigi service is disabled when the Redland backend is used.
Comment 5 marcela maslanova 2009-03-16 20:05:52 UTC
My session crashed from time to time. 
Mar 16 19:18:55 localhost kdm[2028]: X server for display :0 terminated unexpectedly
Mar 16 19:19:06 localhost acpid: client connected from 19539[0:0]
Mar 16 19:19:41 localhost kernel: nepomukservices[19954]: segfault at 4 ip 045788a2 sp bfe609e0 error 4 in libQtCore.so.4.4.3[4530000+21e000]

and /var/log/secure
Mar 16 19:19:01 localhost su: pam_unix(su-l:session): session closed for user root
Mar 16 19:19:03 localhost kdm: :0[6624]: pam_unix(kdm:session): session closed for user marca
Mar 16 19:19:20 localhost kdm: :0[19545]: PAM unable to dlopen(/lib/security/pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory
Mar 16 19:19:20 localhost kdm: :0[19545]: PAM adding faulty module: /lib/security/pam_gnome_keyring.so
Mar 16 19:19:21 localhost kdm: :0[19545]: pam_unix(kdm:session): session opened for user marca by (uid=0)

This is normal for pam here or it isn't related problem?
Comment 6 Kevin Kofler 2009-03-17 05:47:06 UTC
There are 3 different issues in your log:
* this bug
* the session crashing, which is not related to this bug (probably an X11 or driver bug)
* pam_gnome_keyring.so not being found - this is simply the gnome-keyring-pam package not being installed. It can be ignored if you don't need gnome-keyring (i.e. if you don't use things like nm-applet or Firefox). It just means that if something tries using gnome-keyring, it will prompt for your password, it won't try to unlock the keyring using the login password.
Comment 7 Alexandr Matveev 2009-05-05 18:07:09 UTC
Same problem on FreeBSD 8-CURRENT i386 with KDE 4.2 and Qt 4.4.3 from ports: nepomukservicestub crashes at KDE startup.

Core was generated by `nepomukservicestub'.
Program terminated with signal 11, Segmentation fault.
#0  0x281427a6 in QThread::d_func (this=0xa5a5a5a5) at thread/qthread.h:125
125         Q_DECLARE_PRIVATE(QThread)
(gdb) bt
#0  0x281427a6 in QThread::d_func (this=0xa5a5a5a5) at thread/qthread.h:125
#1  0x281417ae in QThread::isRunning (this=0xa5a5a5a5) at thread/qthread.cpp:403
#2  0x2afb3155 in Nepomuk::IndexScheduler::stop (this=0xa5a5a5a5)
    at /usr/ports/x11/kdebase4-runtime/work/kdebase-runtime-4.2.2/nepomuk/services/strigi/indexscheduler.cpp:150
#3  0x2afae917 in ~StrigiService (this=0x2b054e80)
    at /usr/ports/x11/kdebase4-runtime/work/kdebase-runtime-4.2.2/nepomuk/services/strigi/strigiservice.cpp:90
#4  0x2824f414 in QObjectPrivate::deleteChildren (this=0x2aebfb50) at kernel/qobject.cpp:1875
#5  0x28256387 in ~QObject (this=0x2b018600) at kernel/qobject.cpp:884
#6  0x0804c58c in ~ServiceControl (this=0x2b018600)
    at /usr/ports/x11/kdebase4-runtime/work/kdebase-runtime-4.2.2/nepomuk/servicestub/servicecontrol.cpp:39
#7  0x2824f414 in QObjectPrivate::deleteChildren (this=0x2ae58180) at kernel/qobject.cpp:1875
#8  0x28256387 in ~QObject (this=0xbfbfe7fc) at kernel/qobject.cpp:884
#9  0x2824194c in ~QCoreApplication (this=0xbfbfe7fc) at kernel/qcoreapplication.cpp:516
#10 0x285c5a16 in ~QApplication (this=0xbfbfe7fc) at kernel/qapplication.cpp:1044
#11 0x0804b3ac in main (argc=Cannot access memory at address 0xa5a5a5a5
) at /usr/ports/x11/kdebase4-runtime/work/kdebase-runtime-4.2.2/nepomuk/servicestub/main.cpp:149
Comment 8 Nicolas L. 2009-11-18 14:49:35 UTC
work on kde 4.3.x and trunk.

can you confirm ?
Comment 9 Alexandr Matveev 2009-11-18 14:59:39 UTC
Yes, it's works now perfectly
Comment 10 Nicolas L. 2009-11-18 15:01:29 UTC
Thanks for your feedback 

i can close this bug.


---
Nicolas Lécureuil
Mandriva KDE Team