Bug 170520 - knepomuk crashes during shutdown
Summary: knepomuk crashes during shutdown
Status: RESOLVED FIXED
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: 4.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
: 171110 201140 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-09-06 11:28 UTC by Wolfgang
Modified: 2009-07-22 23:21 UTC (History)
8 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 Wolfgang 2008-09-06 11:28:36 UTC
Version:            (using KDE 4.1.1)
OS:                Linux

Anwendung: Nepomuk-Serverdienst (nepomukserver), Signal SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f076fac2700 (LWP 3249)]
[New Thread 0x40f95950 (LWP 3250)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00007f076eda0e70 in QObject::thread () from /usr/lib64/libQtCore.so.4
#6  0x00007f076ed93950 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#7  0x00007f076f6d87f9 in ?? () from /usr/lib64/libkdeinit4_nepomukserver.so
#8  0x00007f076f6d9b6f in ?? () from /usr/lib64/libkdeinit4_nepomukserver.so
#9  0x00007f076f6d5c24 in ?? () from /usr/lib64/libkdeinit4_nepomukserver.so
#10 0x00007f076f6d5d8b in ?? () from /usr/lib64/libkdeinit4_nepomukserver.so
#11 0x00007f076f6d4abc in ?? () from /usr/lib64/libkdeinit4_nepomukserver.so
#12 0x00007f076eda1231 in QObjectPrivate::deleteChildren ()
   from /usr/lib64/libQtCore.so.4
#13 0x00007f076eda93fb in QObject::~QObject () from /usr/lib64/libQtCore.so.4
#14 0x00007f076d01c354 in QApplication::~QApplication ()
   from /usr/lib64/libQtGui.so.4
#15 0x00007f076f6db1e5 in kdemain ()
   from /usr/lib64/libkdeinit4_nepomukserver.so
#16 0x00007f076a0f5436 in __libc_start_main () from /lib64/libc.so.6
#17 0x0000000000400829 in _start ()
#0  0x00007f076a179261 in nanosleep () from /lib64/libc.so.6
Comment 1 George Kiagiadakis 2008-09-06 11:37:11 UTC
*** This bug has been confirmed by popular vote. ***
Comment 2 George Kiagiadakis 2008-09-06 11:41:34 UTC
wtf?? I didn't mean to confirm this bug, just reassign it to nepomuk. how did it get confirmed? And I can't even unconfirm it.... sorry.
Comment 3 Carsten Niehaus 2008-09-06 18:36:19 UTC
Nepomuk crashes here from time to time, always on shutdown. Next time I will try to a get a backtrace with symbols.
Comment 4 Carsten Niehaus 2008-09-07 10:01:31 UTC
Anwendung: Nepomuk-Serverdienst (nepomukserver), Signal SIGSEGV
 [?1034hUsing host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6564930 (LWP 3806)]
[New Thread 0xb4d2eb90 (LWP 3807)]
[KCrash handler]
#6  0xb7c07ea7 in QObject::thread () from /usr/lib/libQtCore.so.4
#7  0xb7f3ea2a in Nepomuk::ServiceController::waitForInitialized ()
   from /usr/lib/libkdeinit4_nepomukserver.so
#8  0xb7f3fd95 in Nepomuk::ServiceController::stop ()
   from /usr/lib/libkdeinit4_nepomukserver.so
#9  0xb7f3c0b6 in Nepomuk::ServiceManager::Private::stopService ()
   from /usr/lib/libkdeinit4_nepomukserver.so
#10 0xb7f3c207 in Nepomuk::ServiceManager::stopAllServices ()
   from /usr/lib/libkdeinit4_nepomukserver.so
#11 0xb7f3b43d in Nepomuk::Server::~Server ()
   from /usr/lib/libkdeinit4_nepomukserver.so
#12 0xb7c0876c in QObjectPrivate::deleteChildren ()
   from /usr/lib/libQtCore.so.4
#13 0xb7c0fe22 in QObject::~QObject () from /usr/lib/libQtCore.so.4
#14 0xb7bfb824 in QCoreApplication::~QCoreApplication ()
   from /usr/lib/libQtCore.so.4
#15 0xb6f91249 in QApplication::~QApplication () from /usr/lib/libQtGui.so.4
#16 0xb6c1714a in KApplication::~KApplication () from /usr/lib/libkdeui.so.5
#17 0xb6c1e618 in KUniqueApplication::~KUniqueApplication ()
   from /usr/lib/libkdeui.so.5
#18 0xb7f416df in kdemain () from /usr/lib/libkdeinit4_nepomukserver.so
#19 0x08048762 in main ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 5 Sebastian Trueg 2008-09-08 15:44:09 UTC
I think this is already fixed in trunk. Could someone please verify (here nothing crashes ever anyway ;)
If it is, I will backport it.
Comment 6 Sebastian Trueg 2008-09-15 20:54:26 UTC
*** Bug 171110 has been marked as a duplicate of this bug. ***
Comment 7 Todd 2008-10-25 23:15:26 UTC
I still have this problem on two computers.  Running 4.1.2 on opensuse.
Comment 8 uprooter 2008-11-28 10:02:41 UTC
Here's a little story.
This bug almost burned my CPU.
I was very hurry and clicked the shutdown. then closed the laptop lid and the crash aborted the shutdown.
then I put my laptop in it's case. and when I opened it 2 hours later  the crash dialog was open...and it was burning hot with a light smell of burnt plastic. 

kde 4.1.3 from sources.

Comment 9 Sebastian Trueg 2009-04-28 12:13:32 UTC
still happening in kde 4.2?
Comment 10 Paul Jewell 2009-04-28 19:56:42 UTC
I had this problem on 4.1, under Gentoo. I removed 3.5 and recompiled all of 4.1 and dependencies and had no more problems. Under 4.2, this problem has not appeared again. Unfortunately I cannot confirm where the problem was rooted.

Sorry!
Comment 11 Dario Andres 2009-07-22 23:21:15 UTC
*** Bug 201140 has been marked as a duplicate of this bug. ***