Incorrect udev-fallback-graphics.conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Dariusz Gadomski | ||
Trusty |
Fix Released
|
Low
|
Unassigned | ||
Utopic |
Fix Released
|
Undecided
|
Dariusz Gadomski | ||
udev (Ubuntu) |
Invalid
|
Undecided
|
Dariusz Gadomski | ||
Precise |
Fix Released
|
Low
|
Bartosz Kosiorek |
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-
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).
Changed in udev (Ubuntu): | |
assignee: | nobody → Dariusz Gadomski (dgadomski) |
Changed in systemd (Ubuntu): | |
assignee: | nobody → Dariusz Gadomski (dgadomski) |
tags: |
added: verification-needed-precise removed: verification-needed |
tags: | added: cts |
Status changed to 'Confirmed' because the bug affects multiple users.