Adding SRU proposal for Precise.

** Description changed:

+ [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).

** Patch added: "udev_175-0ubuntu9.7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4201483/+files/udev_175-0ubuntu9.7.debdiff

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

Title:
  Incorrect udev-fallback-graphics.conf

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to