Mir

[regression] Mir servers choose graphics-dummy (or no driver at all) over mesa-kms on a desktop

Bug #1528082 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Medium
Daniel van Vugt
0.18
Won't Fix
Medium
Daniel van Vugt
mir (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Mir demo servers fail to start without additional help.

Running the latest code on a xenial system, I find the Mir demo servers fail to start when run from ssh and I am logged into X (or on the login screen):

[1450665937.536318] mirserver: Selected driver: dummy (version 0.19.0)
...
ERROR: /home/dan/bzr/mir/trunk/src/renderers/gl/renderer.cpp(51): Throw in function mir::renderer::gl::CurrentRenderTarget::CurrentRenderTarget(mir::graphics::DisplayBuffer*)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::logic_error> >
std::exception::what: DisplayBuffer does not support GL rendering

This is obviously wrong, because for Mir to choose the dummy driver means mesa-kms has returned a platform priority of zero (unsupported). Mesa-kms is not "unsupported", it's the right platform!

Tags: regression

Related branches

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Workaround: --vt 1

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That said, Mir 0.17.1 also fails but at least it fails for the right reason -- trying to use mesa-kms...

[1450666238.373712] mirserver: Selected driver: mesa-kms (version 0.17.1)
ERROR: /build/mir-sTjxjQ/mir-0.17.1+16.04.20151105.1/src/platforms/mesa/server/common/display_helpers.cpp(256): Throw in function int mir::graphics::mesa::helpers::DRMHelper::open_drm_device(const std::shared_ptr<mir::udev::Context>&)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
std::exception::what: Error opening DRM device
22, "Invalid argument"

So the behaviour seem in Mir 0.19 is a step backwards.

summary: - Mir demo servers fail to start without additional help
+ [regression] Mir demo servers fail to start without additional help
Changed in mir:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: [regression] Mir demo servers fail to start without additional help

It appears in fixing the special case of nested for bug 1515558, we forgot to also keep non-nested working.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Essentially we just need mesa-kms to always return at least "supported", and that may be trumped by other drivers like android or proprietary drivers. But mesa-kms should never report itself as "unsupported".

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Correction: It was probably the fix for bug 1506707 that caused this.

summary: - [regression] Mir demo servers fail to start without additional help
+ [regression] Mir demo servers graphics-dummy over mesa-kms on a desktop
summary: - [regression] Mir demo servers graphics-dummy over mesa-kms on a desktop
+ [regression] Mir demo servers choose graphics-dummy over mesa-kms on a
+ desktop
Changed in mir:
assignee: nobody → Daniel van Vugt (vanvugt)
milestone: none → 0.19.0
status: Triaged → In Progress
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: [regression] Mir demo servers choose graphics-dummy over mesa-kms on a desktop

Blocked by bug 1528135, which makes fixing this bug silently exit and less useful than not fixing it right now :/

summary: - [regression] Mir demo servers choose graphics-dummy over mesa-kms on a
- desktop
+ [regression] Mir servers choose graphics-dummy (or no driver at all)
+ over mesa-kms on a desktop
tags: added: regression
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.19.0

Changed in mir:
status: In Progress → Fix Committed
Changed in mir (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mir - 0.19.0+16.04.20160128-0ubuntu1

---------------
mir (0.19.0+16.04.20160128-0ubuntu1) xenial; urgency=medium

  [ Brandon Schaefer ]
  * New upstream release 0.19.0
    - API summary:
      . mirclient abi unchanged at 9
      . mirserver abi bumped to 37
      . mircommon abi unchanged at 5
      . mirplatform abi unchanged at 11
      . mirprotobuf abi unchanged at 3
      . mirplatformgraphics abi bumped to 7
      . mirclientplatform abi bumped to 4
      . mirinputplatform abi bumped to 5
      . mircookie abi bumped to 2
    - Bug fix:
      . Mir servers crash on mouse input (LP: #1528438)
      . Pinch to zoom not working reliably (LP: #1531517)
      . Passing DisplayConfiguration scale property from
        nested server to host appears to not work (LP: #1535780)
      . Various TSan reports when running test suite
        on a mir tsan enabled build (LP: #1523647)
      . Buffer leak during repeated mirscreencasts
        causes server to be killed (LP: #1523900)
      . Cursor now displays correctly (LP: #1526779)
      .ProgramOption::parse_file() reports problems to cerr (LP: #1190165)
      . Nested servers can select wrong platform (LP: #1515558)
      . There seems to be missing RTTI information
         when linking with UBSan enabled (LP: #1521930)
      . Mir threadsanitizer build fails with GCC (LP: #1522581)
      . After "make install" mir_demo_server cannot
        find shared object file in /usr/local/lib (LP: #1522836)
      . Fixed a test in TestClientInput (LP: #1523965)
      . Mir servers choose graphics-dummy (or no driver at all)
        over mesa-kms on a desktop (LP: #1528082)
      . Function mir_event_get_close_surface_event is never used (LP: #1447690)
      . mir::input::Surface::consume(MirEvent const& event)
        should not take a reference to an opaque type (LP: #1450797)
      . lintian: E: mir-doc: privacy-breach-logo (LP: #1483471)

  [ CI Train Bot ]
  * No-change rebuild.

 -- Brandon Schaefer <email address hidden> Thu, 28 Jan 2016 12:19:47 +0000

Changed in mir (Ubuntu):
status: Triaged → Fix Released
Changed in mir:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.