Bug 261465

Summary: segfault in nepomuk during closing KDE
Product: [Unmaintained] nepomuk Reporter: Zsombor <renszarv07>
Component: generalAssignee: Sebastian Trueg <sebastian>
Status: RESOLVED DUPLICATE    
Severity: crash CC: trueg
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Zsombor 2010-12-28 18:08:00 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-24-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:
 I've initated shutdown the computer from KDE, everything went fine, only this error dialog popped up

-- Backtrace:
Application: Nepomuk szolgáltatásalap (nepomukservicestub), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fc4a64b666c in malloc_consolidate (av=0x7fc4a67bde40) at malloc.c:5161
#7  0x00007fc4a64b9350 in _int_free (av=0x7fc4a67bde40, p=0xb2e9f0) at malloc.c:5034
#8  0x00007fc4a64bcc83 in __libc_free (mem=<value optimized out>) at malloc.c:3738
#9  0x00007fc4a4f6b5b9 in ~QByteArray (this=<value optimized out>, data=0x0) at ../../include/QtCore/../../src/corelib/tools/qbytearray.h:383
#10 node_destruct (this=<value optimized out>, data=0x0) at ../../include/QtCore/../../src/corelib/tools/qlist.h:420
#11 QList<QByteArray>::free (this=<value optimized out>, data=0x0) at ../../include/QtCore/../../src/corelib/tools/qlist.h:741
#12 0x00007fc4a4fe1d23 in ~QList (this=0xaf1d50, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qlist.h:716
#13 ~QRingBuffer (this=0xaf1d50, __in_chrg=<value optimized out>) at ../../include/QtCore/private/../../../src/corelib/tools/qringbuffer_p.h:62
#14 QAbstractSocketPrivate::~QAbstractSocketPrivate (this=0xaf1d50, __in_chrg=<value optimized out>) at socket/qabstractsocket.cpp:494
#15 0x00007fc4a4fe9151 in QTcpSocketPrivate::~QTcpSocketPrivate (this=0x7fc4a67bde40, __in_chrg=<value optimized out>) at socket/qtcpsocket_p.h:62
#16 0x00007fc4a8b6a46c in cleanup (this=<value optimized out>, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62
#17 ~QScopedPointer (this=<value optimized out>, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100
#18 QObject::~QObject (this=<value optimized out>, __in_chrg=<value optimized out>) at kernel/qobject.cpp:963
#19 0x00007fc4a4ff11a0 in ~QLocalUnixSocket (this=0xaf1c00, __in_chrg=<value optimized out>) at socket/qlocalsocket_p.h:80
#20 QLocalSocketPrivate::~QLocalSocketPrivate (this=0xaf1c00, __in_chrg=<value optimized out>) at socket/qlocalsocket_p.h:115
#21 0x00007fc4a8b6a46c in cleanup (this=<value optimized out>, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62
#22 ~QScopedPointer (this=<value optimized out>, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100
#23 QObject::~QObject (this=<value optimized out>, __in_chrg=<value optimized out>) at kernel/qobject.cpp:963
#24 0x00007fc4a4febac5 in QLocalSocket::~QLocalSocket (this=0xb07490, __in_chrg=<value optimized out>) at socket/qlocalsocket.cpp:353
#25 0x00007fc4a298cda0 in ?? () from /usr/lib/libsopranoclient.so.1
#26 0x00007fc4a8a5bc22 in QThreadStorageData::set (this=<value optimized out>, p=0x0) at thread/qthreadstorage.cpp:148
#27 0x00007fc4a6cfce4a in qt_cleanup () at kernel/qapplication_x11.cpp:2596
#28 0x00007fc4a6c8b647 in QApplication::~QApplication (this=0x7fff9e2bd4b0, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1121
#29 0x0000000000403c96 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../nepomuk/servicestub/main.cpp:165

Possible duplicates by query: bug 234223.

Reported using DrKonqi
Comment 1 Sebastian Trueg 2011-01-04 18:35:14 UTC
Not related to #234223.
Could you please install Soprano debug symbols and produce another backtrace.
Comment 2 Sebastian Trueg 2011-09-30 15:42:36 UTC

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