[Touch-packages] [Bug 1487649] Re: unity8 crashed with SIGSEGV: assign → set_error → MirConnection → MirConnection → make_unique → connect

2016-05-12 Thread Launchpad Bug Tracker
[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.lau

[Touch-packages] [Bug 1487649] Re: unity8 crashed with SIGSEGV: assign → set_error → MirConnection → MirConnection → make_unique → connect

2016-05-12 Thread Launchpad Bug Tracker
[Expired for Mir because there has been no activity for 60 days.] ** Changed in: mir Status: Incomplete => Expired -- 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/1487649

[Touch-packages] [Bug 1487649] Re: unity8 crashed with SIGSEGV: assign → set_error → MirConnection → MirConnection → make_unique → connect

2016-05-12 Thread Launchpad Bug Tracker
[Expired for mir (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mir (Ubuntu) Status: Incomplete => Expired -- 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

[Touch-packages] [Bug 1487649] Re: unity8 crashed with SIGSEGV: assign → set_error → MirConnection → MirConnection → make_unique → connect

2016-03-13 Thread Daniel van Vugt
For a bug to expire, all tasks must be set to Incomplete and Unassigned. ** Changed in: mir Status: New => Incomplete ** Changed in: mir (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subs

[Touch-packages] [Bug 1487649] Re: unity8 crashed with SIGSEGV: assign → set_error → MirConnection → MirConnection → make_unique → connect

2016-03-09 Thread Albert Astals Cid
Agree with Cemil we could probably close it if it since it hasn't happened again ** Changed in: unity8 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.laun

[Touch-packages] [Bug 1487649] Re: unity8 crashed with SIGSEGV: assign → set_error → MirConnection → MirConnection → make_unique → connect

2015-11-10 Thread Cemil Azizoglu
Looks like an isolated protobuf lib error to me. Hasn't happened in almost 3 months. ** Changed in: mir Importance: High => Low ** Changed in: mir (Ubuntu) Importance: High => Low ** Changed in: mir Milestone: 0.18.0 => None -- You received this bug notification because you are a mem

[Touch-packages] [Bug 1487649] Re: unity8 crashed with SIGSEGV: assign → set_error → MirConnection → MirConnection → make_unique → connect

2015-10-08 Thread Alexandros Frantzis
** Changed in: mir Milestone: 0.17.0 => 0.18.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/1487649 Title: unity8 crashed with SIGSEGV: assign → set_error → MirConnectio

[Touch-packages] [Bug 1487649] Re: unity8 crashed with SIGSEGV: assign → set_error → MirConnection → MirConnection → make_unique → connect

2015-09-15 Thread Cemil Azizoglu
** Changed in: mir Milestone: 0.16.0 => 0.17.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/1487649 Title: unity8 crashed with SIGSEGV: assign → set_error → MirConnectio