[Bug 1367241] [NEW] Incorrect udev-fallback-graphics.conf
Launchpad Bug Tracker
1367241 at bugs.launchpad.net
Thu Sep 11 14:31:18 UTC 2014
You have been subscribed to a public bug by Dariusz Gadomski (dgadomski):
[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).
** Affects: udev (Ubuntu)
Importance: Undecided
Assignee: Dariusz Gadomski (dgadomski)
Status: Confirmed
--
Incorrect udev-fallback-graphics.conf
https://bugs.launchpad.net/bugs/1367241
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list