Bug 267921 - Nepomuk service stub crashes after update 4.6.0 -> 4.6.1
Summary: Nepomuk service stub crashes after update 4.6.0 -> 4.6.1
Status: RESOLVED DUPLICATE of bug 267666
Alias: None
Product: nepomuk
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-07 21:49 UTC by Andreas K. Huettel
Modified: 2011-03-07 22:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas K. Huettel 2011-03-07 21:49:05 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.6.1 (4.6.1) (Compiled from sources)
Qt Version: 4.7.1
Operating System: Linux 2.6.36-gentoo-r5 x86_64
Distribution (Platform): Gentoo Packages

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

* Update 4.6.0 -> 4.6.1
* Log out
* Log in -> crash
* Log out
* Log in -> same crash (this report)

The crash can be reproduced every time.

-- Backtrace:
Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f25facac83c in Nepomuk::Repository::close (this=0x1640e80) at /opt/virtual/tmp-portage/portage/kde-base/nepomuk-4.6.1/work/nepomuk-4.6.1/nepomuk/services/storage/repository.cpp:73
#7  0x00007f25facac92d in Nepomuk::Repository::~Repository (this=0x1640e80, __in_chrg=<value optimized out>) at /opt/virtual/tmp-portage/portage/kde-base/nepomuk-4.6.1/work/nepomuk-4.6.1/nepomuk/services/storage/repository.cpp:65
#8  0x00007f25faa76b5f in qDeleteAll<QHash<QString, Soprano::Model*>::const_iterator> (this=0x1612e50, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qalgorithms.h:322
#9  qDeleteAll<QHash<QString, Soprano::Model*> > (this=0x1612e50, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qalgorithms.h:330
#10 Soprano::Server::ServerCore::~ServerCore (this=0x1612e50, __in_chrg=<value optimized out>) at /opt/virtual/tmp-portage/portage/dev-libs/soprano-2.6.0/work/soprano-2.6.0/server/servercore.cpp:77
#11 0x00007f25facab715 in Nepomuk::Core::~Core (this=0x1612e50, __in_chrg=<value optimized out>) at /opt/virtual/tmp-portage/portage/kde-base/nepomuk-4.6.1/work/nepomuk-4.6.1/nepomuk/services/storage/nepomukcore.cpp:48
#12 0x00007f26097c740f in QObjectPrivate::deleteChildren (this=0x1635de0) at kernel/qobject.cpp:1949
#13 0x00007f26097ceacb in QObject::~QObject (this=<value optimized out>, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#14 0x00007f25facaa473 in Nepomuk::Storage::~Storage (this=0x163c000, __in_chrg=<value optimized out>) at /opt/virtual/tmp-portage/portage/kde-base/nepomuk-4.6.1/work/nepomuk-4.6.1/nepomuk/services/storage/storage.cpp:52
#15 0x00007f26097c740f in QObjectPrivate::deleteChildren (this=0x1611490) at kernel/qobject.cpp:1949
#16 0x00007f26097ceacb in QObject::~QObject (this=<value optimized out>, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#17 0x0000000000404ade in Nepomuk::ServiceControl::~ServiceControl (this=0x15fb570, __in_chrg=<value optimized out>) at /opt/virtual/tmp-portage/portage/kde-base/nepomuk-4.6.1/work/nepomuk-4.6.1/nepomuk/servicestub/servicecontrol.cpp:39
#18 0x00007f26097c740f in QObjectPrivate::deleteChildren (this=0x14854f0) at kernel/qobject.cpp:1949
#19 0x00007f26097ceacb in QObject::~QObject (this=<value optimized out>, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#20 0x00007f2607860687 in QApplication::~QApplication (this=0x7fff0cebc140, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1195
#21 0x0000000000404216 in main (argc=<value optimized out>, argv=<value optimized out>) at /opt/virtual/tmp-portage/portage/kde-base/nepomuk-4.6.1/work/nepomuk-4.6.1/nepomuk/servicestub/main.cpp:165

Reported using DrKonqi
Comment 1 Dario Andres 2011-03-07 22:00:53 UTC
[Comment from a bug triager]
This issue is being tracked at bug 267666.
Merging. Thanks

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