Bug 312760

Created attachment 76764 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.9.98 using Qt 4.8.3

- What I was doing when the application crashed:

I had just rebooted Kubuntu and shortly after logging in while all the apps and stuff were loading up I noticed Dr.Konq sitting on the taskbar with this crash.

-- Backtrace (Reduced):
#6  0x00007f1b9e74c425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f1b9e74fb8b in __GI_abort () at abort.c:91
[...]
#12 0x00007f1b9cfbb8a2 in QAbstractSocketEngine::createSocketEngine (socketDescripter=18, parent=0x7f1b7c002808) at socket/qabstractsocketengine.cpp:133
#13 0x00007f1b9cfc8223 in QAbstractSocket::setSocketDescriptor (this=0x7f1b7c002808, socketDescriptor=18, socketState=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1604
#14 0x00007f1b9cfd72e0 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=18, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370

Created attachment 77032 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.2

- What I was doing when the application crashed:

Simple reboot. First time this has happened. Had just upgraded the kde suite from normal apt-get update session.

-- Backtrace (Reduced):
#6  0x00007f9ba4c5d425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f9ba4c60b8b in __GI_abort () at abort.c:91
[...]
#12 0x00007f9ba34c7b8a in QAbstractSocketEngine::createSocketEngine (socketDescripter=19, parent=0x7f9b80002808) at socket/qabstractsocketengine.cpp:133
#13 0x00007f9ba34d5763 in QAbstractSocket::setSocketDescriptor (this=0x7f9b80002808, socketDescriptor=19, socketState=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1614
#14 0x00007f9ba34e5861 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=19, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370

I suspect this to be another crash caused by running out of file descriptors, since it looks like it is happening when initialising a new socket descriptor. In which case it should be fixed by 630939e388beb4eaf6387a4f9bb827a87fdd0478

Can someone confirm it is fixed by that? Should be easy when 10.1 is released

*** Bug 315359 has been marked as a duplicate of this bug. ***

*** Bug 313033 has been marked as a duplicate of this bug. ***

(In reply to comment #3)
> 
> Can someone confirm it is fixed by that? Should be easy when 10.1 is released

Doesn't seem like it has gotten fixed. Plus, I think each process has a max file descriptor limit. We were overflowing the process's max limit. Not the global one. I think.

*** Bug 315713 has been marked as a duplicate of this bug. ***

Created attachment 78112 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.1 using Qt 4.8.2

- What I was doing when the application crashed:

I reboot my computer and Nepomuk crashed after login.

-- Backtrace (Reduced):
#12 0x00007f64d010eb8a in QAbstractSocketEngine::createSocketEngine (socketDescripter=20, parent=0x7f64b0002a08) at socket/qabstractsocketengine.cpp:133
#13 0x00007f64d011c763 in QAbstractSocket::setSocketDescriptor (this=0x7f64b0002a08, socketDescriptor=20, socketState=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1614
#14 0x00007f64d012c861 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=20, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370
[...]
#17 0x00007f64d3d4509b in QThreadPrivate::start (arg=0x1c30c50) at thread/qthread_unix.cpp:307
[...]

Created attachment 78211 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.1 using Qt 4.8.2

- What I was doing when the application crashed:

Restarted the computer. Crashed immediately upon login to desktop.

-- Backtrace (Reduced):
#6  0x00007f16cdebb425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f16cdebeb8b in __GI_abort () at abort.c:91
[...]
#12 0x00007f16cc725b8a in QAbstractSocketEngine::createSocketEngine (socketDescripter=21, parent=0x7f16a4002808) at socket/qabstractsocketengine.cpp:133
#13 0x00007f16cc733763 in QAbstractSocket::setSocketDescriptor (this=0x7f16a4002808, socketDescriptor=21, socketState=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1614
#14 0x00007f16cc743861 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=21, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370

Created attachment 78306 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.1 "release 545" using Qt 4.8.4

- What I was doing when the application crashed: After a cold reboot, the session is in opening state. (kde use autologin)
Kwallet is not open at that time. Nepomuk services are all ask to start 
The crash appear right after the session is opened.
look like all are running ?

-- Backtrace (Reduced):
#12 0x00007f46447c6db2 in QAbstractSocketEngine::createSocketEngine (socketDescripter=20, parent=0x7f4624002808) at socket/qabstractsocketengine.cpp:133
#13 0x00007f46447d3713 in QAbstractSocket::setSocketDescriptor (this=0x7f4624002808, socketDescriptor=20, socketState=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1604
#14 0x00007f46447e2870 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=20, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370
#15 0x00007f4638afd523 in (anonymous namespace)::LocalServerConnection::createIODevice (this=0x1f6e950) at /usr/src/debug/soprano-2.9.0/server/localserver.cpp:41
#16 0x00007f4638af9da7 in Soprano::Server::ServerConnection::run (this=0x1f6e950) at /usr/src/debug/soprano-2.9.0/server/serverconnection.cpp:140

Created attachment 78575 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.1 "release 545" using Qt 4.8.4

- What I was doing when the application crashed:

I simply switched on the computer and the crash popped up after logging in.

-- Backtrace (Reduced):
#12 0x00007fee2bff9dd2 in QAbstractSocketEngine::createSocketEngine (socketDescripter=23, parent=0x7fee04002a08) at socket/qabstractsocketengine.cpp:133
#13 0x00007fee2c006733 in QAbstractSocket::setSocketDescriptor (this=0x7fee04002a08, socketDescriptor=23, socketState=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1604
#14 0x00007fee2c015890 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=23, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370
#15 0x00007fee20589543 in (anonymous namespace)::LocalServerConnection::createIODevice (this=0xe4acd0) at /usr/src/debug/soprano-2.9.0/server/localserver.cpp:41
#16 0x00007fee20585dc7 in Soprano::Server::ServerConnection::run (this=0xe4acd0) at /usr/src/debug/soprano-2.9.0/server/serverconnection.cpp:140

*** Bug 317821 has been marked as a duplicate of this bug. ***

*** Bug 317383 has been marked as a duplicate of this bug. ***

*** Bug 318369 has been marked as a duplicate of this bug. ***

Created attachment 79513 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.2 "release 1" using Qt 4.8.4

- What I was doing when the application crashed: restartin my computer. appeared right after login.

-- Backtrace (Reduced):
#11 0x00007fd70d727dd2 in QAbstractSocketEngine::createSocketEngine (socketDescripter=19, parent=0x7fd6f4002a08) at socket/qabstractsocketengine.cpp:133
#12 0x00007fd70d734733 in QAbstractSocket::setSocketDescriptor (this=0x7fd6f4002a08, socketDescriptor=19, socketState=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1604
#13 0x00007fd70d743890 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=19, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370
#14 0x00007fd701c32543 in (anonymous namespace)::LocalServerConnection::createIODevice (this=0x24b2040) at /usr/src/debug/soprano-2.9.0/server/localserver.cpp:41
#15 0x00007fd701c2edc7 in Soprano::Server::ServerConnection::run (this=0x24b2040) at /usr/src/debug/soprano-2.9.0/server/serverconnection.cpp:140

Created attachment 79661 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.2 using Qt 4.8.4

- What I was doing when the application crashed:

Immediatly after turning on the computer, this crashed. It restarted successfully though.

-- Backtrace (Reduced):
#11 0x00007f6c870fe802 in QAbstractSocketEngine::createSocketEngine (socketDescripter=socketDescripter@entry=19, parent=parent@entry=0x7f6c5c002808) at socket/qabstractsocketengine.cpp:133
#12 0x00007f6c8710aee3 in QAbstractSocket::setSocketDescriptor (this=this@entry=0x7f6c5c002808, socketDescriptor=socketDescriptor@entry=19, socketState=socketState@entry=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1604
#13 0x00007f6c8711a2e0 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=19, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370
[...]
#16 0x00007f6c8acd9bec in QThreadPrivate::start (arg=0x23cc780) at thread/qthread_unix.cpp:338
[...]

*** Bug 319327 has been marked as a duplicate of this bug. ***

(In reply to comment #3)
> I suspect this to be another crash caused by running out of file
> descriptors, since it looks like it is happening when initialising a new
> socket descriptor.

Simeon, should this also be fixed with your "Fix QTBUG-18934 by checking return value of qt_safe_pipe " Qt commit? 
(asking as a packager, as i did not experience the bug)

Unlikely - I thought about this a bit more, and I suspect it is because the storage service is receiving an X error at an inconvenient time, which causes an uncontrolled shutdown of qapplication, starts to kill some singleton classes and then new socket opens crash. 

But not sure why the X error is being received on startup. This only seems to happen on opensuse and ubuntu, so is it perhaps an apparmor thing?

(In reply to comment #19)
> Unlikely - I thought about this a bit more, and I suspect it is because the
> storage service is receiving an X error at an inconvenient time, which
> causes an uncontrolled shutdown of qapplication, starts to kill some
> singleton classes and then new socket opens crash. 
Ok ;-) I asked as that commit was added to our Qt package, but a bit too late for inclusion in 12.3, so i was wondering should we issue an update for it.

> But not sure why the X error is being received on startup. This only seems
> to happen on opensuse and ubuntu, so is it perhaps an apparmor thing?
Well, we have it disabled by default on openSUSE (and tbh i am not sure our apparmor packages are in usable state), so i doubt it's that.

*** Bug 319436 has been marked as a duplicate of this bug. ***

> > Unlikely - I thought about this a bit more, and I suspect it is because the
> > storage service is receiving an X error at an inconvenient time, which
> > causes an uncontrolled shutdown of qapplication, starts to kill some
> > singleton classes and then new socket opens crash. 
> Ok ;-) I asked as that commit was added to our Qt package, but a bit too
> late for inclusion in 12.3, so i was wondering should we issue an update for
> it.

Yup, probably not worth it

> > But not sure why the X error is being received on startup. This only seems
> > to happen on opensuse and ubuntu, so is it perhaps an apparmor thing?
> Well, we have it disabled by default on openSUSE (and tbh i am not sure our
> apparmor packages are in usable state), so i doubt it's that.

Aha, thanks. That rules out one more hypothesis.

Created attachment 79793 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.2 "release 1" using Qt 4.8.4

- What I was doing when the application crashed:

I had logged on, KDE was loaded & kwallet had opened requesting the P/wd for the network manager.

This is an intermittent fault - it has happened before but is not reproducible.  Interestingly the Kernel has recently (within the last 2/3 days) been upgraded to 3.7.10-1.4.  This fault has occurred with both the old and the new Kernel

There is no indication as to when some of the previous reports were made but this does some to have been going on for some time.

System:    
    Host: linux-mn4n.site Kernel: 3.7.10-1.4-desktop x86_64 (64 bit, gcc: 4.7.2) 
    Desktop KDE 4.10.2 (Qt 4.8.4) 
    Distro: openSUSE 12.3 (x86_64)
    VERSION = 12.3 
    CODENAME = Dartmouth

Machine:   
    System: SAMSUNG (portable) product: RV411/RV511/E3511/S3511/RV711
     Mobo: SAMSUNG 
     model: RV411/RV511/E3511/S3511/RV711 
     Bios: Phoenix 
     version: 03PA.M001.20110312.XW 
     date: 03/12/2011

CPU:
     Dual core Intel Core i5 CPU M 480 (-HT-MCP-) 
     cache: 3072 KB 
     flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) 
     bmips: 10639.8

-- Backtrace (Reduced):
#11 0x00007f9af29badd2 in QAbstractSocketEngine::createSocketEngine (socketDescripter=17, parent=0x7f9ad4002808) at socket/qabstractsocketengine.cpp:133
#12 0x00007f9af29c7733 in QAbstractSocket::setSocketDescriptor (this=0x7f9ad4002808, socketDescriptor=17, socketState=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1604
#13 0x00007f9af29d6890 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=17, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370
#14 0x00007f9ae6e32543 in (anonymous namespace)::LocalServerConnection::createIODevice (this=0x2368000) at /usr/src/debug/soprano-2.9.0/server/localserver.cpp:41
#15 0x00007f9ae6e2edc7 in Soprano::Server::ServerConnection::run (this=0x2368000) at /usr/src/debug/soprano-2.9.0/server/serverconnection.cpp:140

Created attachment 79802 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.2 using Qt 4.8.4

- What I was doing when the application crashed:
I booted openSUSE 12.3 in runlevel 5 ( AKA X11 with network) .

-- Backtrace (Reduced):
#5  0x00007fee4feaf3d5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#6  0x00007fee4feb0858 in __GI_abort () at abort.c:90
#7  0x00007fee5028d8cd in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#8  0x00007fee5028b9c6 in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:40
#9  0x00007fee5028b9f3 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:50

Ok - so my present guess is that the X error being received is "X server not yet ready". 
If so, we can fix this by just starting nepomuk a bit later (with the added bonus that kde will start a little faster because it won't wait for nepomuk). 

If my guess is right, the bug can be fixed by executing at a terminal the following command (for OpenSuSe):

sudo sed -i -e "s/X-KDE-autostart-phase=1/X-KDE-autostart-phase=2/" /usr/share/autostart/nepomukserver.desktop

Can someone who can reproduce this try that and reboot a couple times?

Thanks

> I suspect it is because the storage service is receiving an X error at an inconvenient time

No, the XIO Error is because of the crash in thread 4 (original report).

Simeon, actually I didn't saw anymore crashes with 4.10.3 
Your fix (starting nepomuk later) cause klauncher error in folder view I've on my desktop, one pointing to Desktop and another one for nepomuksearch:/

Am 12.05.2013 22:26, schrieb Simeon Bird:
> https://bugs.kde.org/show_bug.cgi?id=312760
> 
> --- Comment #25 from Simeon Bird <bladud@gmail.com> ---
> Ok - so my present guess is that the X error being received is "X server not
> yet ready". 
> If so, we can fix this by just starting nepomuk a bit later (with the added
> bonus that kde will start a little faster because it won't wait for nepomuk). 
> 
> If my guess is right, the bug can be fixed by executing at a terminal the
> following command (for OpenSuSe):
> 
> sudo sed -i -e "s/X-KDE-autostart-phase=1/X-KDE-autostart-phase=2/"
> /usr/share/autostart/nepomukserver.desktop
> 
> Can someone who can reproduce this try that and reboot a couple times?
> 
> Thanks
> 
Hi Simeon,
I've tried Your hint.
And - ok- it works for me.
No more crashes.

Thanks
Felix

*** Bug 319832 has been marked as a duplicate of this bug. ***

(In reply to comment #26)
> > I suspect it is because the storage service is receiving an X error at an inconvenient time
> 
> No, the XIO Error is because of the crash in thread 4 (original report).

Christoph: Why do you say that? You are probably right because you have been doing this longer than I, but could you elaborate? How does a crash reliably cause an X error (it's in every backtrace there, I think)?

See for example discussion at bug 194750, or http://lists.kde.org/?l=kde-core-devel&m=124388224108162&w=2

I guess when a thread crashes, the connection (pipe) to the X server is closed, causing any subsequent X calls (from other still running threads) to generate an XIO error. For details, you would have to ask someone more familiar with X internals, such as Luboš Luňák.

> I guess when a thread crashes, the connection (pipe) to the X server is
> closed, causing any subsequent X calls (from other still running threads) to
> generate an XIO error. For details, you would have to ask someone more
> familiar with X internals, such as Luboš Luňák.

Ah - I see. Thank you. Then I guess the problem is some sort of race on startup, probably causing a double deletion (since it is a pure virtual crash). My hint helps just because it changes the startup order enough to avoid the race.

Created attachment 80025 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.3 "release 563" using Qt 4.8.4

- What I was doing when the application crashed: After having my session opened by autologin nepomuk crashed .
It was a long time I didn't get that kind of crash. It occur with no real good reasons. Has nothing have changed during the last few days.

-- Backtrace (Reduced):
#11 0x00007fce5be51dd2 in QAbstractSocketEngine::createSocketEngine (socketDescripter=19, parent=0x7fce34002808) at socket/qabstractsocketengine.cpp:133
#12 0x00007fce5be5e733 in QAbstractSocket::setSocketDescriptor (this=0x7fce34002808, socketDescriptor=19, socketState=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1604
#13 0x00007fce5be6d890 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=19, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370
#14 0x00007fce50082543 in (anonymous namespace)::LocalServerConnection::createIODevice (this=0x13207f0) at /usr/src/debug/soprano-2.9.0/server/localserver.cpp:41
#15 0x00007fce5007edc7 in Soprano::Server::ServerConnection::run (this=0x13207f0) at /usr/src/debug/soprano-2.9.0/server/serverconnection.cpp:140

Created attachment 80044 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.2 using Qt 4.8.4

- What I was doing when the application crashed:

the crash happened directly after log in  after the splash screen.

-- Backtrace (Reduced):
#6  0x00007f715e388037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007f715e38b698 in __GI_abort () at abort.c:90
[...]
#12 0x00007f715cbe8802 in QAbstractSocketEngine::createSocketEngine (socketDescripter=socketDescripter@entry=18, parent=parent@entry=0x7f713c002808) at socket/qabstractsocketengine.cpp:133
#13 0x00007f715cbf4ee3 in QAbstractSocket::setSocketDescriptor (this=this@entry=0x7f713c002808, socketDescriptor=socketDescriptor@entry=18, socketState=socketState@entry=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1604
#14 0x00007f715cc042e0 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=18, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370

I just pushed a patch to remove the LocalSocket code entirely, so this bug should be fixed. Though it would have been nice to figure out why this was happening.

*** Bug 320189 has been marked as a duplicate of this bug. ***

*** Bug 320079 has been marked as a duplicate of this bug. ***

*** Bug 320411 has been marked as a duplicate of this bug. ***

I have problems on login too, but I use Fedora.

Shit, this bug didn't happend on OpenSuse.

Created attachment 80235 [details]
Bug file from Fedora

*** Bug 320649 has been marked as a duplicate of this bug. ***

My problem has been solved removing the Nepomuk configuration.

I had Strigi as one of my Nepomuk config files.

¬¬

*** Bug 320676 has been marked as a duplicate of this bug. ***

*** Bug 320946 has been marked as a duplicate of this bug. ***

*** Bug 322338 has been marked as a duplicate of this bug. ***

*** Bug 322439 has been marked as a duplicate of this bug. ***

*** Bug 323620 has been marked as a duplicate of this bug. ***

*** Bug 323708 has been marked as a duplicate of this bug. ***

*** Bug 323743 has been marked as a duplicate of this bug. ***

*** Bug 324977 has been marked as a duplicate of this bug. ***

*** Bug 325158 has been marked as a duplicate of this bug. ***

*** Bug 325948 has been marked as a duplicate of this bug. ***

*** Bug 325965 has been marked as a duplicate of this bug. ***

Created attachment 82896 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.5 using Qt 4.8.4

I started my system and saw this crash immediately after login.

-- Backtrace (Reduced):
#6  0x00007f76d8496037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007f76d8499698 in __GI_abort () at abort.c:90
[...]
#12 0x00007f76d6cf6802 in QAbstractSocketEngine::createSocketEngine (socketDescripter=socketDescripter@entry=19, parent=parent@entry=0x7f76b8002a08) at socket/qabstractsocketengine.cpp:133
#13 0x00007f76d6d02ee3 in QAbstractSocket::setSocketDescriptor (this=this@entry=0x7f76b8002a08, socketDescriptor=socketDescriptor@entry=19, socketState=socketState@entry=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1604
#14 0x00007f76d6d122e0 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=19, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370

Created attachment 83068 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.5 "release 1" using Qt 4.8.4

- What I was doing when the application crashed: it crashed upon initial start up of the computer.

-- Backtrace (Reduced):
#11 0x00007f136d65add2 in QAbstractSocketEngine::createSocketEngine (socketDescripter=18, parent=0x7f1350002808) at socket/qabstractsocketengine.cpp:133
#12 0x00007f136d667733 in QAbstractSocket::setSocketDescriptor (this=0x7f1350002808, socketDescriptor=18, socketState=QAbstractSocket::ConnectedState, openMode=...) at socket/qabstractsocket.cpp:1604
#13 0x00007f136d676890 in QLocalSocket::setSocketDescriptor (this=<optimized out>, socketDescriptor=18, socketState=QLocalSocket::ConnectedState, openMode=...) at socket/qlocalsocket_unix.cpp:370
#14 0x00007f1361bff543 in (anonymous namespace)::LocalServerConnection::createIODevice (this=0x1df0940) at /usr/src/debug/soprano-2.9.0/server/localserver.cpp:41
#15 0x00007f1361bfbdc7 in Soprano::Server::ServerConnection::run (this=0x1df0940) at /usr/src/debug/soprano-2.9.0/server/serverconnection.cpp:140

*** Bug 327542 has been marked as a duplicate of this bug. ***

*** Bug 329547 has been marked as a duplicate of this bug. ***