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. meanwhile it's not an issue, supposedly this
happens on logout when it is shutting down already but takes too long
such that it gets a TERM or QUIT signal to tell it to hurry up, so only
a theoretical problem.
** Changed in: nepomuk-core (Ubuntu)
Importance: Undecided => Low
** Changed in: nepomuk-core (Ubuntu)
Status: New => Triaged
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nepomuk-core/+bug/1163632/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
