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

Harald Sitter sitter.harald at gmail.com
Sun Apr 7 15:00:38 UTC 2013


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 Kubuntu
Bugs, which is subscribed to nepomuk-core in 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



More information about the kubuntu-bugs mailing list