[Bug 1208024] Re: Default rules fail to set PRIMARY_DEVICE_FOR_DISPLAY for vmwgfx driver

[Martin Pitt]

Thanks! Committed to packaging tree.

** Package changed: udev (Ubuntu) => systemd (Ubuntu)

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu)
       Status: New => Fix Committed

** Summary changed:

- Default rules fail to set PRIMARY_DEVICE_FOR_DISPLAY for vmwgfx driver
+ [udev] Default rules fail to set PRIMARY_DEVICE_FOR_DISPLAY for vmwgfx driver

** Changed in: systemd (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1208024

Title:
  [udev] Default rules fail to set PRIMARY_DEVICE_FOR_DISPLAY for vmwgfx
  driver

Status in “systemd” package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 13.04
  175-0ubuntu26

  The default 78-graphics-card.rules does not set
  PRIMARY_DEVICE_FOR_DISPLAY=1 for devices using the vmwgfx driver (from
  the open-vm-tools package). Several other drm subsystem drivers are
  special-cased here (i915, radeon, nouveau). This causes a misleading
  failure message in the boot log, such as:

  * Starting load fallback graphics devices
  [ FAIL ]

  caused by /etc/init/udev-fallback-graphics.conf erroneously trying to
  modprobe vesafb because it thinks that no graphics driver has been
  successfully loaded. The VM does still function properly, this bug
  just causes a spurious error message.

  Adding a rule for vmwgfx similar to what already exists for other
  drivers fixes the issue.

  Example of others experiencing this issue:
  http://askubuntu.com/questions/142213/ubuntu-12-04-server-failed-to-load-fallback-graphics-devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1208024/+subscriptions