touch-packages team mailing list archive

[Alexandros Frantzis <alexandros.frantzis@xxxxxxxxxxxxx>]

As I mentioned before, the failures shown in both the errors.u.c reports
(and which are really confusing, I don't really trust the backtraces to
be correct there, they don't make much sense) and the original
backtrace, just indicate that that the server has died and the clients
fail to communicate with it.

So I take this bug as a request to make the failures more graceful on
the client side (as much as we can).

-- 
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/1347053

Title:
  Clients are crashing with a fatal exception in
  MirSocketRpcChannel::send_message()

Status in Mir:
  Triaged
Status in Mir 0.5 series:
  Won't Fix
Status in Mir 0.6 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity-system-compositor” package in Ubuntu:
  Invalid

Bug description:
  Starting unity8 when u-s-c is running results in them fighting over
  the hardware (not for the socket due to the default XDG_RUNTIME_DIR)
  and u-s-c crashing.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor 0.0.4+14.10.20140718-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  Date: Tue Jul 22 16:26:40 2014
  ExecutablePath: /usr/bin/unity-system-compositor-spinner
  GraphicsCard:
   
  InstallationDate: Installed on 2014-07-22 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140722-095505)
  LocalLibraries: /android/system/lib/liblog.so /android/system/lib/libhardware.so /android/system/lib/libstdc++.so /android/system/lib/libcutils.so /android/system/lib/libcorkscrew.so /android/system/lib/libsync.so /android/system/lib/libc.so /android/system/lib/hw/gralloc.msm8960.so /android/system/lib/libm.so /android/system/lib/libGLESv1_CM.so /android/system/lib/libmemalloc.so /android/system/lib/egl/libGLESv1_CM_adreno.so /android/system/lib/libz.so /android/system/lib/libgccdemangle.so /android/system/lib/libui.so /android/system/lib/libadreno_utils.so /android/system/lib/egl/libEGL_adreno.so /android/system/lib/libstlport.so /android/system/lib/egl/eglsubAndroid.so /android/system/lib/libutils.so /android/system/lib/libgsl.so /android/system/lib/libdsyscalls.so /android/system/lib/egl/libGLESv2_adreno.so /android/system/lib/libsc-a3xx.so /android/system/lib/libGLESv2.so /android/system/lib/libGLES_trace.so /android/system/lib/libEGL.so /android/system/lib/libqdutils.so
  ProcCmdline: /usr/bin/unity-system-compositor-spinner
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
   ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  Title: unity-system-compositor-spinner crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.54-1
  version.lightdm: lightdm 1.11.4-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1347053/+subscriptions