[Bug 1367241] Re: Incorrect udev-fallback-graphics.conf

[Dariusz Gadomski]

Actually I think the second approach would be better, since the error
comes not from the message (which is redirected to upstart logs anyway),
but from the return code of the script.

Unfortunately, according to my knowledge, the upstart scripts are
executed with the "-e" switch making it stop with a failure on a first
failed call. This ties our hands a bit as we cannot have any failing
commands there (even those we expect to fail in a particular
configuration) and makes our potential script less flexible.

So in any case we would be interested in not returning anything other than 0. A commonly used work-around for this limitation could be used like this:
modprobe -q -b vesafb || true

This would load the module if available, but would remain quiet (-q
switch to modprobe with additional || true) if the module is not there.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1367241

Title:
  Incorrect udev-fallback-graphics.conf

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

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