** Description changed:

  There are failing asserts:
  ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects 
owned by a different thread. Current thread 33abf0. Receiver '' (of type 
'QNetworkAccessManager') was created in thread 4220b460", file 
kernel/qcoreapplication.cpp, line 502
  
  See for example https://launchpadlibrarian.net/162128583
  /buildlog_ubuntu-trusty-armhf.unity-scopes-
  api_1%3A0.1.7-0~125%2B201401101436~ubuntu14.04.1_FAILEDTOBUILD.txt.gz
+ 
+ To upgrade to the Qt 5.2 easily (now possible on desktop where all 
dependencies are built):
+ apt-add-repository ppa:canonical-qt5-edgers/qt5-beta2
+ apt-get update
+ apt-get dist-upgrade
+ 
+ See/describe dependencies of packages at
+ http://pad.ubuntu.com/qt52-dependencies

** Description changed:

  There are failing asserts:
  ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects 
owned by a different thread. Current thread 33abf0. Receiver '' (of type 
'QNetworkAccessManager') was created in thread 4220b460", file 
kernel/qcoreapplication.cpp, line 502
  
  See for example https://launchpadlibrarian.net/162128583
  /buildlog_ubuntu-trusty-armhf.unity-scopes-
  api_1%3A0.1.7-0~125%2B201401101436~ubuntu14.04.1_FAILEDTOBUILD.txt.gz
  
  To upgrade to the Qt 5.2 easily (now possible on desktop where all 
dependencies are built):
  apt-add-repository ppa:canonical-qt5-edgers/qt5-beta2
  apt-get update
  apt-get dist-upgrade
  
+ Downgrade with ppa-purge ppa:canonical-qt5-edgers/qt5-beta2
+ 
  See/describe dependencies of packages at
  http://pad.ubuntu.com/qt52-dependencies

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

Title:
  HTTP tests failing when built with Qt5.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scopes-api/+bug/1267917/+subscriptions

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

Reply via email to