Ubuntu
mir package

mir_demo_server_basic Error opening DRM device VirtualBox

Bug #1331980 reported by Huck-bernhard on 2014-06-19

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 1 person

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

Bug Description

:~$ sudo mir_demo_server_basic
ERROR: /build/buildd/mir-0.3.0+14.10.20140618.1/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"

:~$ lsmod | grep drm
drm 245600 2 vboxvideo
:~$

:~$ sudo pmap `pidof X` | grep dri.so
ae62d000 3372K r-x-- swrast_dri.so
ae978000 32K r---- swrast_dri.so
ae980000 24K rw--- swrast_dri.so

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: mir-demos 0.3.0+14.10.20140618.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic i686
ApportVersion: 2.14.3-0ubuntu2
Architecture: i386
Date: Thu Jun 19 10:44:48 2014
InstallationDate: Installed on 2014-06-13 (5 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140613)
SourcePackage: mir
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Huck-bernhard (huck-bernhard) wrote on 2014-06-19:

Dependencies.txt Edit (5.5 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (291 bytes, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2014-07-01:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1118903, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.