[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-03-06 Thread Michał Sawicz
*** This bug is a duplicate of bug 1421009 *** https://bugs.launchpad.net/bugs/1421009 OK the underlying cause for all of those seems to be a Qt dbus bug, marking dupe of one that has the most complete trace of all threads. ** This bug has been marked a duplicate of bug 1421009 unity8 some

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-19 Thread Alberto Aguirre
Right Thread#1 and Thread#15 seem deadlock. There must be at least a couple of different mutexes used by the Qt DBus abstraction that are causing this but have not inspected the code fully yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which i

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-15 Thread Daniel van Vugt
OK then, based on comment #14 we have three different deadlocks now :) This one is roughly: (hung in some dbus calls) from: QNetworkManagerInterfaceDeviceWireless::accessPointAdded -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscr

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-15 Thread Daniel van Vugt
Did we just split this bug into two; bug 1421255, bug 1421308 and leave this one representing nothing? :) Is this now a duplicate? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-15 Thread Ricardo Salveti
Got the same crash, output of 't a a bt' attached. current build number: 234 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-02-14 00:43:00 version version: 234 version ubuntu: 20150211.1 version device: 20150211-74c2df2 version custom: 20150207-538-29-183

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-15 Thread Daniel van Vugt
** Changed in: mir Milestone: 0.12.0 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1417773 Title: Unity8 completely frozen (unable to unlock, receive calls, etc)

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-12 Thread Cemil Azizoglu
rsalveti's original bug doesn't seem to be related to Mir. Marking it as Invalid for Mir. ** Changed in: mir Status: Triaged => Invalid ** Changed in: mir (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-12 Thread Cemil Azizoglu
Spawned another Mir bug for Saviq's second backtrace as it looks unrelated to the first one. https://bugs.launchpad.net/mir/+bug/1421308 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.ne

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-12 Thread Alexandros Frantzis
> Looking again, this could indeed be happening (in Saviq's traces). Thanks Alberto ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1417773 Title: Unity8 completely frozen

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-12 Thread Alexandros Frantzis
> Fun. Looks like some kind of deadlock in Mir's GlibMainLoop with > Mir's framedropping logic > > I see no indication of this in the backtraces. Looking again, this could indeed be happening (in Saviq's traces). -- You received this bug notification because you are a member of Ubuntu Touch se

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-12 Thread kevin gunn
spawing Mir bug 1421255 for the vivid findings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1417773 Title: Unity8 completely frozen (unable to unlock, receive calls, etc) S

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-12 Thread Alexandros Frantzis
> Fun. Looks like some kind of deadlock in Mir's GlibMainLoop with Mir's framedropping logic I see no indication of this in the backtraces. > I think we might have two unrelated deadlocks here. > > rsalveti's is a dbus deadlock. > saviq's is a Mir deadlock. Not sure if Saviq's issue is a pure M

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-12 Thread Daniel van Vugt
I think we might have two unrelated deadlocks here. rsalveti's is a dbus deadlock. saviq's is a Mir deadlock. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1417773 Title: Un

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-12 Thread Michał Sawicz
Fun. Looks like some kind of deadlock in Mir's GlibMainLoop with Mir's framedropping logic ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubun

[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)

2015-02-12 Thread Daniel van Vugt
** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Status: New => Triaged ** Changed in: mir Importance: Undecided => Critical ** Changed in: mir Milestone: None => 0.12.0 -- You received this bug notification because you are a member of Ubuntu To