So to determine if the client crashes due to the --desktop_file_hint causing the application to be rejected, you should see a "REJECTED" line in the unity8 log file. The application rejection causes the Mir connection to be denied, and app crashes with this error.
However digging into this instance of the fail: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4469/ the unity8 log file: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4469/artifact/results/log/unity8.log does not contain this string. However there are many unity8/mir crashes, eventually breaking things to be unrecoverable. The bad crash appears to be: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::logic_error> >' what(): compositor_acquire would block; probably too many clients. Will need Mir team input to investigate this further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262982 Title: dialer-app crashed: QUbuntu: Could not create application instance To manage notifications about this bug go to: https://bugs.launchpad.net/unity-mir/+bug/1262982/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
