This appears to be a crash inside Qt itself, and only occurs with 5.6+,
apparently due to QDBus changing to use threading instead of the event
loop, for asynchronous operations. There seems to be some fixes in Qt
Code Review that should theoretically fix this. It would be nice if we
could test these and get them into our release of Qt. I'm afraid there
won't be any way to work around this crash in the scope or ubuntu-
download-manager (we're keeping a u-d-m singleton object around, which
is destroyed on exit) code itself.

** Package changed: unity-scope-click (Ubuntu) => qtbase-opensource-src
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618590

Title:
  scoperunner crashed with SIGSEGV in QObject::disconnect()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1618590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to