[Touch-packages] [Bug 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

2017-03-28 Thread Stephen M. Webb
** Changed in: mir/0.26
Milestone: 0.26.3 => None

** Changed in: mir
Milestone: 1.0.0 => None

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1667352

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Invalid
Status in Mir 0.26 series:
  Invalid
Status in libsdl2 package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Fix Released

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

2017-03-23 Thread Stephen M. Webb
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1667352

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Invalid
Status in Mir 0.26 series:
  Invalid
Status in libsdl2 package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Fix Released

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

2017-03-23 Thread Launchpad Bug Tracker
This bug was fixed in the package protobuf - 3.0.0-9ubuntu2

---
protobuf (3.0.0-9ubuntu2) zesty; urgency=low

  * debian/patches/Hide-unnecessary-exported-library-symbols.patch:
- Backport upstream fix to hide unnecessary exported symbols
  (LP: #1667352)
  * debian/patches/fix-reload.diff:
- Removed, not needed anymore.

 -- Alexandros Frantzis   Thu, 16 Mar
2017 12:10:45 +0200

** Changed in: protobuf (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1667352

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  Invalid
Status in Mir 0.26 series:
  Invalid
Status in libsdl2 package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Fix Released

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

2017-03-21 Thread Brandon Schaefer
Bug is in protobuf leaking symbols, so not a mir/sdl2 bug.

** Changed in: libsdl2 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: mir/0.26
 Assignee: Brandon Schaefer (brandontschaefer) => (unassigned)

** Changed in: mir
   Status: In Progress => Invalid

** Changed in: mir/0.26
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1667352

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  Invalid
Status in Mir 0.26 series:
  Invalid
Status in libsdl2 package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

2017-03-21 Thread Michael Terry
@Alexandros, I uploaded this to zesty, thanks!  Since we're in freeze
for zesty (and releasing a beta on Thursday), it may not land in short
order, but I'll keep an eye on it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1667352

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

2017-03-17 Thread Mathew Hodson
** No longer affects: neverball (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1667352

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

2017-03-17 Thread Ubuntu Foundations Team Bug Bot
The attachment "protobuf package fix debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1667352

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in neverball package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

2017-03-17 Thread Alexandros Frantzis
I have attached a protobuf debdiff fix for this issue. It's a backport
from upstream (more details in the debian patch metadata).

** Patch added: "protobuf package fix debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1667352/+attachment/4839390/+files/protobuf-zesty-fix-1667352.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1667352

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in neverball package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

2017-03-16 Thread Daniel van Vugt
** Changed in: mir/0.26
Milestone: 0.26.2 => 0.26.3

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1667352

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in neverball package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

2017-03-14 Thread Daniel van Vugt
** Changed in: protobuf (Ubuntu)
 Assignee: (unassigned) => Alexandros Frantzis (afrantzis)

** Changed in: protobuf (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1667352

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in neverball package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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