Nepomuk service stub crashes on logon.

[jfl]

Every time I log on to KDE on my computer, a windows comes up saying: "We are sorry, Nepomuk Service Stub closed unexpectedly." It also says: "Details:
Executable: nepomukservicestub PID: 1819 Signal: Segmentation fault(11)."
This started just after I upgaded to KDE 4.6.1 from KDE 4.5. It hasn't affected anything I've done on the computer so far, but it gets annoying.

[woodsmoke]

Re: Nepomuk service stub crashes on logon.

Hi
I have no clue so don't listen to me, but i just spent a long time on nepomuk and there is basically one database thing that has to be there, you might check my thread elsehwere and see if my thread says that a database is missing and then install that one. it is, I think, mysqld or something like that.

But, then a segmentation fault may mean something totally different.

woodsmoke

[jfl]

Re: Nepomuk service stub crashes on logon.

I think a segmentation fault is when a program tries to access something it is not allowed to in RAM.

[woodsmoke]

Re: Nepomuk service stub crashes on logon.

hmmmm the db would be running in ram... hmm don't know though

woodsmoke

[jfl]

Re: Nepomuk service stub crashes on logon.

I think it might be trying to access the kernel software, or the kernel hasn't set up permissions properly.

[lmilano]

Re: Nepomuk service stub crashes on logon.

Try reinstalling all nepomuk and akonadi packages. That solved a similar crash I had in one of my computers after upgrading to 4.6.1

[woodsmoke]

Re: Nepomuk service stub crashes on logon.

That also is what I did, if you do not actually have settings in Kontact, uninstall it also. Do akonadi and nepomuk both at once and then Kontact
woodsmoke

[Guest]

Re: Nepomuk service stub crashes on logon.

It appears as though Nepomuk is a file indexing/search function which is a dependency for kdelibs. I've tried updating the package/reinstalling it as well as akonadi and removed the kontact package all to no avail. I agree that it must be a permission thing (I started having the crashes after my kernel update earlier today). I guess we'll have to just ride it out until an update arrives since kde depends on nepomuk and we can't just remove it. I am going to try and suspend indexing service for a bit and see if the crashes cease.

[caryb]

I have had this problem for years! I did a fresh install from the 13.10 dailies & it still is broken.