[Bug 1163632] Re: nepomukserver crashed with SIGSEGV in close()

2014-02-12 Thread Rohan Garg
Thanks for taking the time to report this bug. 13.04 reached EOL on January 27, 2014. Please see this document for currently supported Kubuntu releases: https://wiki.kubuntu.org/Releases Unfortunately this means that there will be no more bugfixes for 13.04. It is also recommended that you

[Bug 1163632] Re: nepomukserver crashed with SIGSEGV in close()

2013-04-07 Thread RussianNeuroMancer
I have same issue. In my case output of this command is true. ** Changed in: nepomuk-core (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1163632 Title:

[Bug 1163632] Re: nepomukserver crashed with SIGSEGV in close()

2013-04-07 Thread Starbetrayer
In my case, I have no output, it just goes back to the normal console. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1163632 Title: nepomukserver crashed with SIGSEGV in close() To manage

[Bug 1163632] Re: nepomukserver crashed with SIGSEGV in close()

2013-04-07 Thread Harald Sitter
it's caused by signals landing while the qapplication is already cleaning up, thus making the signal handler work on a partially destructed object tree. solution would be to prevent signal handling after the qapplication mainloop returned. talked to upstream and hope it gets resolved soonishy.

[Bug 1163632] Re: nepomukserver crashed with SIGSEGV in close()

2013-04-04 Thread Harald Sitter
What is the output of kreadconfig --file nepomukserverrc --group Basic Settings --key Start Nepomuk ** Changed in: nepomuk-core (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.