Mir

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

Bug #1366805 reported by Ruben Grimm on 2014-09-08

This bug report is a duplicate of: Bug #1118903: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines). Edit Remove

This bug affects 16 people

Affects		Status	Importance	Assigned to	Milestone
	Mir	New	Undecided	Unassigned	Mir 0.8.0
	mir (Ubuntu)	Confirmed	Undecided	Unassigned

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

Tags:

Revision history for this message

Ruben Grimm (pmk1c) wrote on 2014-09-08:

BootLog.txt Edit (5.4 KiB, text/plain; charset="utf-8")
LightDMLog.txt Edit (4.2 KiB, text/plain; charset="utf-8")
LightDMLogOld.txt Edit (6.3 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (301 bytes, text/plain; charset="utf-8")

Daniel van Vugt (vanvugt) on 2014-09-09

summary:	- Can't login to Unity Next + Can't login to Unity8 in VirtualBox; Mir crashes with + "std::exception::what: Error opening DRM device"
affects:	unity-system-compositor (Ubuntu) → mir (Ubuntu)
summary:	- Can't login to Unity8 in VirtualBox; Mir crashes with + Can't log in to Unity8 in VirtualBox; Mir crashes with "std::exception::what: Error opening DRM device"
Changed in mir:
milestone:	none → 0.8.0

Daniel van Vugt (vanvugt) on 2014-09-09

Changed in mir:
milestone:	0.8.0 → 0.9.0

Revision history for this message

Andreas Pokorny (andreas-pokorny) wrote on 2014-09-09:

Apart from the strange errno in the logs above.. to allow mir to run on vbox we need to add page flipping and the default implementation of prime to the vbox drm driver:

http://www.virtualbox.org/svn/vbox/trunk/src/VBox/Additions/linux/drm/

page flipping has been adde here:

https://github.com/xknight/vboxvideo

That plus mesa 10.3 and mir should work. Maybe there is also a way to use the virtualbox GL implementation?

Daniel van Vugt (vanvugt) on 2014-09-10

Changed in mir:
milestone:	0.9.0 → 0.8.0

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2014-09-10:

Duplicate of bug 1331980, which is arguably a duplicate of bug 1118903.

Revision history for this message

Rocko (rockorequin) wrote on 2015-01-02:

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?

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-01-02:

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