← Back to team overview

touch-packages team mailing list archive

[Bug 1366805] Re: Can't log in to Unity8 in VirtualBox; Mir crashes with "std::exception::what: Error opening DRM device"

 

*** This bug is a duplicate of bug 1118903 ***
    https://bugs.launchpad.net/bugs/1118903

Actually, I don't think this should be a duplicate of #1118903. Why
should we be forced to use (dreadfully slow) software rendering for
unity8 in a VM when we don't need to do so for unity7? Wouldn't it be
better to fix mir so it can use vboxdrv's DRM capabilties?

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

Title:
  Can't log in to Unity8 in VirtualBox; Mir crashes with
  "std::exception::what: Error opening DRM device"

Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  When I try to login to Unity Next the system-compositor seems to crash
  immediately. I'm using Ubuntu Next on VirtualBox.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-desktop-mir (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Mon Sep  8 15:10:15 2014
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2014-07-09 (61 days ago)
  InstallationMedia: Ubuntu-Desktop-Next 14.10 "Utopic Unicorn" - Alpha amd64 (20140708)
  SourcePackage: unity-system-compositor
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UnitySystemCompositorLog:
   Warning: ignoring unrecognised arguments:
   ERROR: /build/buildd/mir-0.7.0+14.10.20140829/src/platform/graphics/mesa/display_helpers.cpp(242): Throw in function int mir::graphics::mesa::helpers::DRMHelper::open_drm_device(const std::shared_ptr<mir::udev::Context>&)
   Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
   std::exception::what: Error opening DRM device
   123, "No medium found"
  UnitySystemCompositorLogOld:
   Warning: ignoring unrecognised arguments:
   ERROR: /build/buildd/mir-0.7.0+14.10.20140829/src/platform/graphics/mesa/display_helpers.cpp(242): Throw in function int mir::graphics::mesa::helpers::DRMHelper::open_drm_device(const std::shared_ptr<mir::udev::Context>&)
   Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
   std::exception::what: Error opening DRM device
   123, "No medium found"
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.libdrm: libdrm2 2.4.56-1
  version.lightdm: lightdm 1.11.8-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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


References