touch-packages team mailing list archive

[Christopher Townsend <christopher.townsend@xxxxxxxxxxxxx>]

Most definitely not the lack of the graphics drivers as I have those
installed on my machine and have a working Unity 8 desktop session.

Another data point is that this doesn't occur when running against
mir_demo_server, but only when running in a Unity 8 desktop session.  I
start an Xmir instance using a desktop file like the following:

$cat ~/.local/share/applications/xmir-debug.desktop
[Desktop Entry]
Version=1.0
Name=XMir Debug
Exec=Xmir :1
Type=Application
StartupNotify=true
X-Ubuntu-Touch=true

Then from an ssh session, I do something like:
$ DISPLAY=:1 xprop -root

I get the following output:
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""

But after the command is finished, the Xmir window goes away and the
error message I put in the description is printed in ~/.cache/upstart
/application-legacy-xmir-debug-blah.log.

The test program that William attached to this bug also produces the
same behavior while in a Unity 8 desktop session.

I hope this helps.  Also, considering it doesn't occur when running with
mir_demo_server, it's probably not a Mir/Xmir issue, but I'm really not
sure whose problem it is, but it needs fixing:)

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

Title:
  Xmir crashes when client closes display

Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xmir crashes when a client loses its connection to Xmir, either
  through XCloseDisplay, or by normal program termination. This affects
  xprop and GTK applications (they temporarily open a connection to the
  X server to obtain the value of the AT_SPI_BUS property on the root
  window).

  This is what is printed in application's upstart log:

  (EE)
  Fatal server error:
  (EE) Failed to connect to Mir: Failed to process connect response: /build/mir-3eDTxk/mir-0.14.0+15.10.20150723.1/src/client/probing_client_platform_factory.cpp(37): Throw in function virtual std::shared_ptr<mir::client::ClientPlatform> mir::client::ProbingClientPlatformFactory::create_client_platform(mir::client::ClientContext*)
  Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
  std::exception::what: No appropriate client platform module found

  (EE)

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