desktop-packages team mailing list archive

[Christopher Townsend <christopher.townsend@xxxxxxxxxxxxx>]

I also ran xprop in gdb to see what may be causing the Xmir window to
clsoe and just the simple exit(0) at the end of xprop.c causes it to
close.

Based on the call to XCloseDisplay() and xprop exiting causing Xmir to
close, I'm wondering if Xmir is being too aggressive on cleaning up when
the application is done with DISPLAY????   Need some expert advice
here:)

** Summary changed:

- Reading/setting xprop on Xmir causes it to crash
+ Reading/setting xprop on Xmir window causes it to close

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1481330

Title:
  Reading/setting xprop on Xmir window causes it to close

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

Bug description:
  When having an Xmir window up and running and then trying to read or
  set an xprop, the Xmir window immediately exits.  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/ubuntu/+source/mir/+bug/1481330/+subscriptions