[Touch-packages] [Bug 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
*** 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 sometimes hangs on boot -- 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) Status in the base for Ubuntu mobile products: New Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
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 is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1417773 Title: Unity8 completely frozen (unable to unlock, receive calls, etc) Status in the base for Ubuntu mobile products: New Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
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 subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1417773 Title: Unity8 completely frozen (unable to unlock, receive calls, etc) Status in the base for Ubuntu mobile products: New Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
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/1417773 Title: Unity8 completely frozen (unable to unlock, receive calls, etc) Status in the base for Ubuntu mobile products: New Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
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 ** Attachment added: "t a a bt of the same crash (same result with bt full)" https://bugs.launchpad.net/ubuntu-rtm/+source/unity8/+bug/1417773/+attachment/4320194/+files/trace.txt -- 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) Status in the base for Ubuntu mobile products: New Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
** 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) Status in the base for Ubuntu mobile products: New Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
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, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1417773 Title: Unity8 completely frozen (unable to unlock, receive calls, etc) Status in the base for Ubuntu mobile products: New Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
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.net/bugs/1417773 Title: Unity8 completely frozen (unable to unlock, receive calls, etc) Status in the base for Ubuntu mobile products: New Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
> 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 (unable to unlock, receive calls, etc) Status in the base for Ubuntu mobile products: New Status in Mir: Triaged Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
> 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 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) Status in the base for Ubuntu mobile products: New Status in Mir: Triaged Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
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) Status in the base for Ubuntu mobile products: New Status in Mir: Triaged Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
> 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 Mir deadlock. In Saviq's backtrace, threads 1 and 11(both Qt related) and 15 (Mir waiting for a reply) seem suspicious. -- 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) Status in the base for Ubuntu mobile products: New Status in Mir: Triaged Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
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: Unity8 completely frozen (unable to unlock, receive calls, etc) Status in the base for Ubuntu mobile products: New Status in Mir: Triaged Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
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 Ubuntu. https://bugs.launchpad.net/bugs/1417773 Title: Unity8 completely frozen (unable to unlock, receive calls, etc) Status in the base for Ubuntu mobile products: New Status in Mir: Triaged Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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 1417773] Re: Unity8 completely frozen (unable to unlock, receive calls, etc)
** 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 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) Status in the base for Ubuntu mobile products: New Status in Mir: Triaged Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 Was driving around with my car, and noticed once I got back home that my clock was stuck in a previous time (~20min before getting home), and after trying to use the phone I noticed unity8 was completely stuck, but the underling OS was still running fine. The worst here is that we're unable to notify the user about calls, as the interface is completely stuck. Another bad thing is that this could as well happen when the user is sleeping or something, without an easy way to know until he tries to use the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417773/+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
