XMir starts with black screen ("[xmir] Failed to set new display config: ... std::exception::what: Invalid format for used output")

It's a mir issue.

upgrade again, mir abi had changed

hmm no you have the latest versions..

[ 41.737] (EE) [xmir] Failed to set new display config: /build/buildd/mir-0.1.4+14.04.20140204/src/platform/graphics/mesa/real_kms_display_configuration.cpp(130): Throw in function virtual void mir::graphics::mesa::RealKMSDisplayConfiguration::configure_output(mir::graphics::DisplayConfigurationOutputId, bool, mir::geometry::Point, size_t, MirPixelFormat, MirPowerMode, MirOrientation)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
std::exception::what: Invalid format for used output

OK - sounds as if there is a problem - hope it gets fixed soon.

I tried downgrading to the previous versions of xserver-xorg-xmir and xserver-xorg-core (2:1.15.0-1ubuntu2), but no help.

Then I removed ubuntu-desktop-xmir (and xserver-xorg-xmir) and all is well again.

Status changed to 'Confirmed' because the bug affects multiple users.

Renders the system temporarily or permanently unusable.

Although I didn't write it, this exception is in a region of code I am actively refactoring. And the placement of this validity check is something I was going to have to modify as part of that.

Unfortunately bug 1237332 prevents us from finding the root cause of the crash.

It would seem the offending code comes from https://code.launchpad.net/~andreas-pokorny/mir/add-pixel-format-to-display-configuration/+merge/200294 ?

Yeah, I'm not convinced the validation check is useful or even correct. But I will have to review it in detail soon.

The offending validation check has been removed, moved and changed in this proposal:
  lp:~vanvugt/mir/eliminate-configure-output

Unfortunately, without details of what the invalid format being used was, I can't tell if the issue is fixed or could simply reoccur in a new location.

After updating to xserver-xorg-xmir 2:1.15.0-1ubuntu6 on Feb 13th the system reboots without problems. A whole set of mir packages went through at the same time; don't know if Daniel's fix was included, but something fixed my problem at least.

Thanks for the quick solution.

No the proposal in comment #14 has not landed in any release yet.

Big thanks, applying the preview.diff from lp:~vanvugt/mir/eliminate-configure-output fixes the crash for me :)

Only problem the elimination presents now is that unity-system-compositor will fail to build when it doesn't see 'configure_output'.

unity-system-compositor-0.0.2+14.04.20140212.1/src/dbus_screen.cpp:66:28: error: 'class mir::graphics::DisplayConfiguration' has no member named 'configure_output'
             displayConfig->configure_output(
                            ^
src/CMakeFiles/unity-system-compositor.dir/build.make:97: recipe for target 'src/CMakeFiles/unity-system-compositor.dir/dbus_screen.cpp.o' failed
make[2]: *** [src/CMakeFiles/unity-system-compositor.dir/dbus_screen.cpp.o] Error 1

Thanks. When/if that branch lands in Mir, I'll be sure to fix unity-system-compositor et al.

OK, I just realized "eliminate-configure-output" doesn't fix the bug. The branch itself has a bug which prevents this bug from manifesting (which it still should).

Tried u-s-c (with ubuntu-desktop-mir). At first I got a blank screen, but after running `sudo restart lightdm` I was able to log into Unity. The fonts looks a a bit weird and some apps (Firefox, VLC, file selector) are not themed. Otherwise, usable... Nonetheless, when I removed these packages with `remove --auto-remove` and rebooting, lightdm wouldn't start (and I was presented with the "Low graphics" dialog). So for now I'll have to use XMir.

After starting `gnome-settings-daemon` manually, Firefox (and the other apps) have recovered their theme. The fonts still look funny, though.

Just did a dist-upgrad (maybe the last one got interrupted, or this is a new update), and the fonts look good again and gnome-settings-daemon started fine (no theming issue). The blank screen persists, and I still need to restart lightdm as a workaround.

Edwin - That's an X bug. Mir and unity-system-compositor only deal the the screen as a whole. Not the pixels/fonts etc. Please log the bug elsewhere.

Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown

A fix is ready for Mir 0.1.6. Maybe we can try to get it into Ubuntu before 0.1.6 even...

Not Fix Committed to Ubuntu just yet...
https://code.launchpad.net/~mir-team/mir/trusty

Thanks again Daniel.
http://bazaar.launchpad.net/~mir-team/mir/development-branch/revision/1405 fixes nicely, look forward to 0.1.6.

Is there an ETA for when this will land in Trusty ... ?

We're trying to land Mir 0.1.6 in trusty right now. There's no predicting how long that can take. Sometimes a couple of hours, sometimes a week. Keep an eye out: https://launchpad.net/ubuntu/+source/mir

This bug was fixed in the package mir - 0.1.6+14.04.20140310-0ubuntu1

---------------
mir (0.1.6+14.04.20140310-0ubuntu1) trusty; urgency=medium

  [ Kevin Gunn ]
  * Cherry-picked from future release 0.1.7:
    - Enhancement: options: Make it easier to customize DefaultConfiguration
    - Bug fix: Don't pass a parameter to bash's popd command. It doesn't expect
      one and will return an error from cross-compile-chroot.sh. (LP: #1287600)
  * New upstream release 0.1.6 (https://launchpad.net/mir/+milestone/0.1.6)
    - mirserver ABI bumped to 16.
    - Server API changes:
      . Report classes have moved to new namespaces/components. Please
        consult the server headers.
      . General clean-ups and virtual function changes affecting the ABI
        (a rebuild is required for all shells).
    - mirclient ABI unchanged, still at 7. Clients do not need rebuilding.
    - Add new feature: Screen recording ("screencasting") as demonstrated by
      the new mir-util "mirscreencast".
    - debian: Provide platform packages managed with dpkg alternatives.
    - Add new valgrind suppressions (mostly for armhf right now)
    - tools: Add new libmirclientplatform.so to install_on_android.sh.
    - Add "mir_demo_standalone_render_overlays", which is a free-standing
      example of overlay support.
    - Proper DisplayConfiguration for the AndroidDisplay to be better
      prepared for multi-monitor Android.
    - Commenced/continued simplifying the surface class hierarchy: BasicSurface
      has now absorbed SurfaceData.
    - Dynamically load the client platform library.
    - Bugs fixed:
      . Exceptions thrown from within compositing threads were untraceable,
        resulting in a bunch of undebuggable crash reports (LP: #1237332)
      . Ensure we close drm device file descriptors on exec. (LP: #1284081)
      . nested render_surfaces fails on N4 [std::exception::what: Failed to
        compile vertex shader:] (LP: #1284597)
      . examples: correct "fullscreen-surfaces" option. (LP: #1284554)
      . Fix mutex data race reported by helgrind in integration test:
        SwapperSwappingStress (LP: #1282886)
      . scene: Return null snapshots for sessions without surfaces
        (LP: #1281728)
      . tests: Address some raciness in
        MesaDisplayTest.drm_device_change_event_triggers_handler.
        (LP: #1283085)
      . tests: Suppress spurious memory errors occuring when running the
        unit tests on armhf with valgrind. (LP: #1279438)
      . Mir shows an old frame on client startup (for Mesa GL clients)
        (LP: #1281938)
      . tests: Add expectation to validate second SessionAuthorizer method
        is called wit correct parameter. (LP: #1218436)
      . Set field "current_format" when sending a display config to the
        server. (LP: #1277343)
      . Fix crash in android devices by working around a subtle threading
        bug, use a dummy thead_local array to push the gl/egl context TLS
        into a region where the future wait code does not overwrite it.
        (LP: #1280086)
      . compositor: calling SwitchingBundle::force_requests_to_complete()
        can be a no-op when there are no requests. (LP...