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

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 204-0ubuntu10

---------------
systemd (204-0ubuntu10) saucy; urgency=low

  * debian/systemd-services.install: Install systemd-multi-seat-x
    (LP: #1214146)
  * debian/local/78-graphics-card.rules: Also recognize vmwgfx driver. Thanks
    Reagan Sanders! (LP: #1208024)
  * Add 0000-upstream-hwdb-updates.patch: Update to latest upstream fixes of
    hwdb, to get proper keyboard support.
  * Move to hwdb keymap database to be able to continue to sync to upstream,
    and benefit from the improved speed and eased maintenance:
    - Drop 0000-upstream-keymaps.patch.
    - Add 0000-upstream-hwdb-keyboard.patch to backport the "keymap" builtin.
    - Add debian/extra/60-keyboard.hwdb (straight copy from upstream master),
      install in debian/udev.install.
    - debian/rules: Configure with --disable-keymap to not build/install the
      old keymap stuff any more.
    - Adds keymap for Samsung NP53U3C (LP: #1203853)
 -- Martin Pitt <martin.pitt at ubuntu.com>   Tue, 27 Aug 2013 13:09:08 +0200

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

-- 
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 Released

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