Bug 271109 - Nepomuk crashes on logout
Summary: Nepomuk crashes on logout
Status: RESOLVED DUPLICATE of bug 281448
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-16 17:21 UTC by Robert Simmons
Modified: 2011-09-19 11:36 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (11.79 KB, text/plain)
2011-06-04 20:31 UTC, EP
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Simmons 2011-04-16 17:21:24 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-28-generic i686
Distribution: Ubuntu 10.10

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

I had just closed my browser window (Chrome) and tried to logout.  During logout Nepomuk crashed.

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

Thread 2 (Thread 0xb0e21b70 (LWP 2121)):
[KCrash Handler]
#7  0x00000000 in ?? ()
#8  0x0030fb3b in QCoreApplication::notifyInternal (this=0xbfc0c858, receiver=0x82e6660, event=0xb0e21024) at kernel/qcoreapplication.cpp:732
#9  0x0033e93a in sendEvent (source=0x849c058) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#10 socketNotifierSourceDispatch (source=0x849c058) at kernel/qeventdispatcher_glib.cpp:110
#11 0x00b11855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#12 0x00b15668 in ?? () from /lib/libglib-2.0.so.0
#13 0x00b15848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#14 0x0033e565 in QEventDispatcherGlib::processEvents (this=0x8357418, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#15 0x0030e609 in QEventLoop::processEvents (this=0xb0e21280, flags=) at kernel/qeventloop.cpp:149
#16 0x0030ea8a in QEventLoop::exec (this=0xb0e21280, flags=...) at kernel/qeventloop.cpp:201
#17 0x0020ab7e in QThread::exec (this=0x8330c48) at thread/qthread.cpp:490
#18 0x020fd9bd in ?? () from /usr/lib/libsopranoserver.so.1
#19 0x0020ddf9 in QThreadPrivate::start (arg=0x8330c48) at thread/qthread_unix.cpp:266
#20 0x00115cc9 in start_thread (arg=0xb0e21b70) at pthread_create.c:304
#21 0x00a4769e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb77bb710 (LWP 1856)):
#0  0x00f02416 in __kernel_vsyscall ()
#1  0x0011a4dc in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x00a54d9d in __pthread_cond_wait (cond=0x834c0a0, mutex=0x834c088) at forward.c:139
#3  0x0020e9c7 in wait (this=0x82f26e8, mutex=0x82f26d0, time=4294967295) at thread/qwaitcondition_unix.cpp:88
#4  QWaitCondition::wait (this=0x82f26e8, mutex=0x82f26d0, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#5  0x0020da1f in QThread::wait (this=0x8330c48, time=4294967295) at thread/qthread_unix.cpp:652
#6  0x020fe862 in ?? () from /usr/lib/libsopranoserver.so.1
#7  0x0210351a in ?? () from /usr/lib/libsopranoserver.so.1
#8  0x020f701e in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1
#9  0x024b1f9b in Nepomuk::Core::~Core (this=0x826e038, __in_chrg=<value optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:48
#10 0x00322816 in QObjectPrivate::deleteChildren (this=0x826e428) at kernel/qobject.cpp:1957
#11 0x00329f30 in QObject::~QObject (this=0x823ac30, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#12 0x007a09a8 in Nepomuk::Service::~Service (this=0x823ac30, __in_chrg=<value optimized out>) at ../../nepomuk/core/nepomukservice.cpp:44
#13 0x024b080a in Nepomuk::Storage::~Storage (this=0x823ac30, __in_chrg=<value optimized out>) at ../../../../nepomuk/services/storage/storage.cpp:52
#14 0x00322816 in QObjectPrivate::deleteChildren (this=0x8250bc8) at kernel/qobject.cpp:1957
#15 0x00329f30 in QObject::~QObject (this=0x824dee0, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#16 0x0804ba22 in Nepomuk::ServiceControl::~ServiceControl (this=0x824dee0, __in_chrg=<value optimized out>) at ../../../nepomuk/servicestub/servicecontrol.cpp:39
#17 0x00322816 in QObjectPrivate::deleteChildren (this=0x818fb38) at kernel/qobject.cpp:1957
#18 0x00329f30 in QObject::~QObject (this=0xbfc0c858, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#19 0x003114fa in QCoreApplication::~QCoreApplication (this=0xbfc0c858, __in_chrg=<value optimized out>) at kernel/qcoreapplication.cpp:648
#20 0x03bf3690 in QApplication::~QApplication (this=0xbfc0c858, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1153
#21 0x0110e5ba in KApplication::~KApplication (this=0xbfc0c858, __in_chrg=<value optimized out>) at ../../kdeui/kernel/kapplication.cpp:911
#22 0x0804b10e in main (argc=2, argv=0xbfc0ca04) at ../../../nepomuk/servicestub/main.cpp:165

Possible duplicates by query: bug 271040, bug 270116, bug 270025, bug 269839, bug 269610.

Reported using DrKonqi
Comment 1 EP 2011-06-04 20:31:22 UTC
Created attachment 60627 [details]
New crash information added by DrKonqi

nepomukservicestub (0.2) on KDE Platform 4.6.80 (4.7 Beta1) "release 6" using Qt 4.7.3

- What I was doing when the application crashed:

I closed all open applications and tried to logout

-- Backtrace (Reduced):
#8  0xb759f78e in QCoreApplication::notifyInternal (this=0xbfb331c8, receiver=0x826fc10, event=0xb0a54084) at kernel/qcoreapplication.cpp:731
#9  0xb75cd918 in sendEvent (source=0x8291128) at kernel/qcoreapplication.h:215
#10 socketNotifierSourceDispatch (source=0x8291128) at kernel/qeventdispatcher_glib.cpp:110
[...]
#14 0xb75cdf7b in QEventDispatcherGlib::processEvents (this=0x8462418, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#15 0xb759ea6d in QEventLoop::processEvents (this=0xb0a54290, flags=...) at kernel/qeventloop.cpp:149
Comment 2 Sebastian Trueg 2011-09-19 11:36:41 UTC

*** This bug has been marked as a duplicate of bug 281448 ***