[Touch-packages] [Bug 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
** Changed in: canonical-pocket-desktop Status: Fix Committed => Fix Released ** Changed in: mir Status: Fix Committed => Fix Released -- 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/1511095 Title: unity-system-compositor crash, no interaction on windowed mode Status in canonical-pocket-desktop: Fix Released Status in Mir: Fix Released Status in Mir 0.17 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to say) but I regularly see N7 reboot with me having interacted with it I will have usually connected the BT mouse and have maybe u-s-s open as well as dash (i think i've even seen it do so after just being rebooted with me not touching it before the next reboot). the screen will be on or off from being idel, no interaction per se and the device will suddenly display the "spinner" screen which is actually ubuntu dot-dot-dots I have seen it enough to confirm there are no crash files generated/associated with it lastly, i have seen this mostly while i have added silo21 (unity8 improvements) on top of the latest pd image. attached is a syslog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+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 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
** Changed in: mir/0.17 Status: Fix Committed => Fix Released -- 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/1511095 Title: unity-system-compositor crash, no interaction on windowed mode Status in canonical-pocket-desktop: Fix Committed Status in Mir: Fix Committed Status in Mir 0.17 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to say) but I regularly see N7 reboot with me having interacted with it I will have usually connected the BT mouse and have maybe u-s-s open as well as dash (i think i've even seen it do so after just being rebooted with me not touching it before the next reboot). the screen will be on or off from being idel, no interaction per se and the device will suddenly display the "spinner" screen which is actually ubuntu dot-dot-dots I have seen it enough to confirm there are no crash files generated/associated with it lastly, i have seen this mostly while i have added silo21 (unity8 improvements) on top of the latest pd image. attached is a syslog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+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 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
** Changed in: mir/0.17 Status: New => Fix Committed ** Changed in: canonical-pocket-desktop Status: New => Fix Committed ** Changed in: mir (Ubuntu) Status: New => Fix Committed ** No longer affects: qtmir (Ubuntu) ** No longer affects: unity-system-compositor (Ubuntu) ** No longer affects: unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1511095 Title: unity-system-compositor crash, no interaction on windowed mode Status in canonical-pocket-desktop: Fix Committed Status in Mir: Fix Committed Status in Mir 0.17 series: Fix Committed Status in mir package in Ubuntu: Fix Committed Bug description: I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to say) but I regularly see N7 reboot with me having interacted with it I will have usually connected the BT mouse and have maybe u-s-s open as well as dash (i think i've even seen it do so after just being rebooted with me not touching it before the next reboot). the screen will be on or off from being idel, no interaction per se and the device will suddenly display the "spinner" screen which is actually ubuntu dot-dot-dots I have seen it enough to confirm there are no crash files generated/associated with it lastly, i have seen this mostly while i have added silo21 (unity8 improvements) on top of the latest pd image. attached is a syslog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+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 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
** Branch linked: lp:mir/0.17 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1511095 Title: unity-system-compositor crash, no interaction on windowed mode Status in canonical-pocket-desktop: New Status in Mir: Fix Committed Status in Mir 0.17 series: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to say) but I regularly see N7 reboot with me having interacted with it I will have usually connected the BT mouse and have maybe u-s-s open as well as dash (i think i've even seen it do so after just being rebooted with me not touching it before the next reboot). the screen will be on or off from being idel, no interaction per se and the device will suddenly display the "spinner" screen which is actually ubuntu dot-dot-dots I have seen it enough to confirm there are no crash files generated/associated with it lastly, i have seen this mostly while i have added silo21 (unity8 improvements) on top of the latest pd image. attached is a syslog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+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 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
** Also affects: mir/0.17 Importance: Undecided Status: New ** Changed in: mir/0.17 Milestone: None => 0.17.1 ** Changed in: mir/0.17 Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1511095 Title: unity-system-compositor crash, no interaction on windowed mode Status in canonical-pocket-desktop: New Status in Mir: Fix Committed Status in Mir 0.17 series: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to say) but I regularly see N7 reboot with me having interacted with it I will have usually connected the BT mouse and have maybe u-s-s open as well as dash (i think i've even seen it do so after just being rebooted with me not touching it before the next reboot). the screen will be on or off from being idel, no interaction per se and the device will suddenly display the "spinner" screen which is actually ubuntu dot-dot-dots I have seen it enough to confirm there are no crash files generated/associated with it lastly, i have seen this mostly while i have added silo21 (unity8 improvements) on top of the latest pd image. attached is a syslog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+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 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.18.0 ** Changed in: mir Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1511095 Title: unity-system-compositor crash, no interaction on windowed mode Status in canonical-pocket-desktop: New Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to say) but I regularly see N7 reboot with me having interacted with it I will have usually connected the BT mouse and have maybe u-s-s open as well as dash (i think i've even seen it do so after just being rebooted with me not touching it before the next reboot). the screen will be on or off from being idel, no interaction per se and the device will suddenly display the "spinner" screen which is actually ubuntu dot-dot-dots I have seen it enough to confirm there are no crash files generated/associated with it lastly, i have seen this mostly while i have added silo21 (unity8 improvements) on top of the latest pd image. attached is a syslog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+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 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
** Changed in: mir Assignee: (unassigned) => Alexandros Frantzis (afrantzis) ** Changed in: mir Status: New => In Progress ** Changed in: mir Importance: Undecided => High ** Changed in: mir Milestone: None => 0.18.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1511095 Title: unity-system-compositor crash, no interaction on windowed mode Status in canonical-pocket-desktop: New Status in Mir: In Progress Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to say) but I regularly see N7 reboot with me having interacted with it I will have usually connected the BT mouse and have maybe u-s-s open as well as dash (i think i've even seen it do so after just being rebooted with me not touching it before the next reboot). the screen will be on or off from being idel, no interaction per se and the device will suddenly display the "spinner" screen which is actually ubuntu dot-dot-dots I have seen it enough to confirm there are no crash files generated/associated with it lastly, i have seen this mostly while i have added silo21 (unity8 improvements) on top of the latest pd image. attached is a syslog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+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 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
** Branch linked: lp:~afrantzis/mir/maybe-fix-1511095 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1511095 Title: unity-system-compositor crash, no interaction on windowed mode Status in canonical-pocket-desktop: New Status in Mir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to say) but I regularly see N7 reboot with me having interacted with it I will have usually connected the BT mouse and have maybe u-s-s open as well as dash (i think i've even seen it do so after just being rebooted with me not touching it before the next reboot). the screen will be on or off from being idel, no interaction per se and the device will suddenly display the "spinner" screen which is actually ubuntu dot-dot-dots I have seen it enough to confirm there are no crash files generated/associated with it lastly, i have seen this mostly while i have added silo21 (unity8 improvements) on top of the latest pd image. attached is a syslog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+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 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
The stack trace shows a crash in mi::DisplayInputRegion::bounding_rectangle() because we don't have any displays in the region. A fix for the immediate crash is at: https://code.launchpad.net/~afrantzis/mir/maybe-fix-1511095-for-0.17/ >From the supplied info I can't tell if not having any detected active displays is a valid situation or it's indeed a problem and the root cause of what we are seeing. Whatever the case we shouldn't crash like this, so this fix is a definite improvement, even if it turns out not to be a final fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1511095 Title: unity-system-compositor crash, no interaction on windowed mode Status in canonical-pocket-desktop: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to say) but I regularly see N7 reboot with me having interacted with it I will have usually connected the BT mouse and have maybe u-s-s open as well as dash (i think i've even seen it do so after just being rebooted with me not touching it before the next reboot). the screen will be on or off from being idel, no interaction per se and the device will suddenly display the "spinner" screen which is actually ubuntu dot-dot-dots I have seen it enough to confirm there are no crash files generated/associated with it lastly, i have seen this mostly while i have added silo21 (unity8 improvements) on top of the latest pd image. attached is a syslog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+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 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
** Also affects: mir Importance: Undecided Status: New ** Branch linked: lp:~afrantzis/mir/maybe-fix-1511095-for-0.17 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1511095 Title: unity-system-compositor crash, no interaction on windowed mode Status in canonical-pocket-desktop: New Status in Mir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to say) but I regularly see N7 reboot with me having interacted with it I will have usually connected the BT mouse and have maybe u-s-s open as well as dash (i think i've even seen it do so after just being rebooted with me not touching it before the next reboot). the screen will be on or off from being idel, no interaction per se and the device will suddenly display the "spinner" screen which is actually ubuntu dot-dot-dots I have seen it enough to confirm there are no crash files generated/associated with it lastly, i have seen this mostly while i have added silo21 (unity8 improvements) on top of the latest pd image. attached is a syslog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+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
