touch-packages team mailing list archive

[TWC Service <1367241@xxxxxxxxxxxxxxxxxx>]

This resolves our issue, so +1 on the migration from proposed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1367241

Title:
  Incorrect udev-fallback-graphics.conf

Status in “systemd” package in Ubuntu:
  Fix Released
Status in “udev” package in Ubuntu:
  Invalid
Status in “udev” source package in Precise:
  Fix Committed
Status in “systemd” source package in Trusty:
  Fix Committed
Status in “systemd” source package in Utopic:
  Fix Released

Bug description:
  [Impact]

   * When setting up primary display driver fails an attempt to load vesafb
     module is undertaken. This fails since from 3.13.0-16.36 version
     vesafb is compiled in the kernel (so no actual modprobing is needed).
     This causes false alert in the log:
     "Starting load fallback graphic devices: [fail]"

  [Test Case]

   * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device).
   * Wait for loading graphics devices.
   * If the primary device module has failed to load, falling back to vesafb will be attempted.

  [Regression Potential]

   * Implemented by the bug reported.

   * Affects only the debian/ directory.

  [Other Info]
   
   * Original bug description:

  The udev-fallback-graphics.conf script tries to load vesafb module if
  PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier.

  The problem is that from kernel version 3.13.0-16.36 vesafb is
  compiled in permanently into the kernel (CONFIG_FB_VESA=y), so
  whenever the fallback mode is triggered this script will FAIL
  confusing the users.

  Most probably this file is no longer needed (or it just be used to
  print informative message).

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