[Bug 1515712] Re: maliit-server becomes deadlocked

2016-03-15 Thread Bill Filler
** Changed in: canonical-devices-system-image Milestone: ww08-2016 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515712 Title: maliit-server becomes deadlocked To manage notifications

[Bug 1515712] Re: maliit-server becomes deadlocked

2016-02-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: maliit-framework (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515712

[Bug 1515712] Re: maliit-server becomes deadlocked

2016-01-13 Thread Jean-Baptiste Lallement
Could someone test and confirm if it is still an issue or not as requested by Tony. I didn't experience this problem with latest builds. ** Changed in: canonical-devices-system-image Status: Confirmed => Incomplete ** Changed in: canonical-devices-system-image Milestone: ww02-2016 =>

[Bug 1515712] Re: maliit-server becomes deadlocked

2015-12-08 Thread Tony Espy
@Bill Can you have someone re-test with the latest rc-proposed? As mentioned in my previous comment, we removed a large amount of NM related DBus code from the Qt Bearer Management plugin as a fix for bug #1480877. This work all landed in the PPA and is being tested by QA for release as OTA8.5.

[Bug 1515712] Re: maliit-server becomes deadlocked

2015-11-25 Thread Tony Espy
Any Qt code that uses QNetworkAccessManager, QNetworkSession, or related classes can cause the QNetwork Bearer Management to get instantiated, which in turn loads a network-manager specific plugin. Please see bug #1480877 for details. As it's really long, you might want to check out just the

[Bug 1515712] Re: maliit-server becomes deadlocked

2015-11-13 Thread Albert Astals Cid
As per > We should figure out why we are even doing any network stuff at all, as we probably shouldn't be. It comes from the fact that QtMultimedia uses network transparent methods to load urls used for audio playing, so even if in the keyboard we're using a local sound for audio feedback,

[Bug 1515712] Re: maliit-server becomes deadlocked

2015-11-13 Thread Albert Astals Cid
Agreeing with Pat here dbus_connection_send_with_reply on one thread and qDBusRealToggleWatch in the other are basically the signs of the known qdbus lock we've seen before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1515712] Re: maliit-server becomes deadlocked

2015-11-12 Thread Pat McGowan
Adding qt as qdbus seems suepect see bug #1421009 and perhaps https://bugreports.qt.io/browse/QTBUG-48410 and https://bugreports.qt.io/browse/QTBUG-44836 ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because

[Bug 1515712] Re: maliit-server becomes deadlocked

2015-11-12 Thread Pat McGowan
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image