Bug 286457 - kubuntu, kde 4.7.3 on dell xps15 L502X. nepomuk crash at startup
Summary: kubuntu, kde 4.7.3 on dell xps15 L502X. nepomuk crash at startup
Status: RESOLVED DUPLICATE of bug 285789
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-11-13 01:14 UTC by Carlos Novaes
Modified: 2011-11-16 10:04 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (2.71 KB, text/plain)
2011-11-13 12:57 UTC, Thomas Richard
Details
New crash information added by DrKonqi (2.81 KB, text/plain)
2011-11-13 15:36 UTC, Paul Schloemer
Details
New crash information added by DrKonqi (2.69 KB, text/plain)
2011-11-13 15:57 UTC, GGG
Details
New crash information added by DrKonqi (3.08 KB, text/plain)
2011-11-14 04:11 UTC, Samuel Desnoës
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Novaes 2011-11-13 01:14:10 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
Just login and a message will pop up with failure notification

The crash can be reproduced every time.

-- Backtrace:
Application: Stub do servidor do Nepomuk (nepomukservicestub), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fc193ccce4a in Nepomuk::Repository::close (this=0x18da1a0) at ../../../../nepomuk/services/storage/repository.cpp:96
#7  0x00007fc193cccf6c in Nepomuk::Repository::~Repository (this=0x18da1a0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:78
#8  0x00007fc193ccd049 in Nepomuk::Repository::~Repository (this=0x18da1a0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:79
#9  0x00007fc193a71ed7 in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1
#10 0x00007fc193ccbc6c in Nepomuk::Core::~Core (this=0x18d2ff0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
#11 0x00007fc193ccbd19 in Nepomuk::Core::~Core (this=0x18d2ff0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:48
#12 0x00007fc1a2c20d75 in QObjectPrivate::deleteChildren (this=0x18d9630) at kernel/qobject.cpp:1955
#13 0x00007fc1a2c26349 in QObject::~QObject (this=0x18dc720, __in_chrg=<optimized out>) at kernel/qobject.cpp:946
#14 0x00007fc193ccaef3 in ~Storage (this=0x18dc720, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/storage.cpp:54
#15 Nepomuk::Storage::~Storage (this=0x18dc720, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/storage.cpp:56
#16 0x00007fc1a2c20d75 in QObjectPrivate::deleteChildren (this=0x18d3570) at kernel/qobject.cpp:1955
#17 0x00007fc1a2c26349 in QObject::~QObject (this=0x18c33d0, __in_chrg=<optimized out>) at kernel/qobject.cpp:946
#18 0x0000000000404439 in Nepomuk::ServiceControl::~ServiceControl (this=0x18c33d0, __in_chrg=<optimized out>) at ../../../nepomuk/servicestub/servicecontrol.cpp:39
#19 0x00007fc1a2c20d75 in QObjectPrivate::deleteChildren (this=0x1706300) at kernel/qobject.cpp:1955
#20 0x00007fc1a2c26349 in QObject::~QObject (this=0x7fff03562100, __in_chrg=<optimized out>) at kernel/qobject.cpp:946
#21 0x00007fc1a0f51f87 in QApplication::~QApplication (this=0x7fff03562100, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1093
#22 0x0000000000403a54 in main (argc=2, argv=0x7fff035625a8) at ../../../nepomuk/servicestub/main.cpp:105

This bug may be a duplicate of or related to bug 286338.

Possible duplicates by query: bug 286338, bug 286231, bug 286222, bug 286210, bug 286199.

Reported using DrKonqi
Comment 1 Thomas Richard 2011-11-13 12:57:59 UTC
Created attachment 65587 [details]
New crash information added by DrKonqi

nepomukservicestub (0.2) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4

- What I was doing when the application crashed:

Just booting my system. It happens every time i try to start Nepomuk.

-- Backtrace (Reduced):
#6  0x00007f25f562ee4a in Nepomuk::Repository::close (this=0x2675180) at ../../../../nepomuk/services/storage/repository.cpp:96
#7  0x00007f25f562ef6c in Nepomuk::Repository::~Repository (this=0x2675180, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:78
#8  0x00007f25f562f049 in Nepomuk::Repository::~Repository (this=0x2675180, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:79
#9  0x00007f25f53f5ed7 in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1
#10 0x00007f25f562dc6c in Nepomuk::Core::~Core (this=0x261aec0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
Comment 2 Paul Schloemer 2011-11-13 15:36:35 UTC
Created attachment 65590 [details]
New crash information added by DrKonqi

nepomukservicestub (0.2) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4

- What I was doing when the application crashed:

Just starting up Kubuntu. Happens every time I boot, and when I close the error log, every once in a while the error message about Nepomuk reappears to remind me it is not working.

-- Backtrace (Reduced):
#6  0x00007f295d804b8e in Nepomuk::Repository::close (this=0x1288d30) at ../../../../nepomuk/services/storage/repository.cpp:86
#7  0x00007f295d804ccc in Nepomuk::Repository::~Repository (this=0x1288d30, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:75
#8  0x00007f295d804da9 in Nepomuk::Repository::~Repository (this=0x1288d30, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:76
#9  0x00007f295d5cbed7 in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1
#10 0x00007f295d8039fc in Nepomuk::Core::~Core (this=0x12e8d80, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
Comment 3 GGG 2011-11-13 15:57:23 UTC
Created attachment 65616 [details]
New crash information added by DrKonqi

nepomukservicestub (0.2) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4

- What I was doing when the application crashed:

Again crashed during startup. _________

-- Backtrace (Reduced):
#6  0x00007f6556e50b8e in Nepomuk::Repository::close (this=0x1552d70) at ../../../../nepomuk/services/storage/repository.cpp:86
#7  0x00007f6556e50ccc in Nepomuk::Repository::~Repository (this=0x1552d70, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:75
#8  0x00007f6556e50da9 in Nepomuk::Repository::~Repository (this=0x1552d70, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:76
#9  0x00007f6556befed7 in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1
#10 0x00007f6556e4f9fc in Nepomuk::Core::~Core (this=0x159ab80, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
Comment 4 Samuel Desnoës 2011-11-14 04:11:20 UTC
Created attachment 65640 [details]
New crash information added by DrKonqi

nepomukservicestub (0.2) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.2

- What I was doing when the application crashed:
Just starting KDE... Happens every time i start my system.

-- Backtrace (Reduced):
#7  0x08594dee in Nepomuk::Repository::close (this=0xa169b38) at ../../../../nepomuk/services/storage/repository.cpp:86
#8  0x08594f2b in Nepomuk::Repository::~Repository (this=0xa169b38, __in_chrg=<value optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:75
#9  0x08595022 in Nepomuk::Repository::~Repository (this=0xa169b38, __in_chrg=<value optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:76
[...]
#11 0x06f50df0 in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1
#12 0x0859392b in Nepomuk::Core::~Core (this=0xa16b260, __in_chrg=<value optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
Comment 5 Sebastian Trueg 2011-11-16 10:04:59 UTC

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