[Touch-packages] [Bug 1421308] Re: Yet another Mir deadlock
Forgot to get libdbus symbols :/, will do so the next time I encounter this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1421308 Title: Yet another Mir deadlock Status in Mir: Invalid Status in unity8 package in Ubuntu: New Bug description: Got a lockup on boot, here's a another gdb t a a bt. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1421308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421308] Re: Yet another Mir deadlock
I agree with Alberto's assessment. Qt's mainloop appears blocked. Would need more frames of thread1 to get a good idea why. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1421308 Title: Yet another Mir deadlock Status in Mir: Invalid Status in unity8 package in Ubuntu: New Bug description: Got a lockup on boot, here's a another gdb t a a bt. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1421308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
