Utopic fix committed to git, thanks! I keep this open for trusty, but as it's neither a data loss nor critical bug and just a cosmetical corner case I keep it as low importance.
You say "since 3.13.0-16.36" which is trusty -- i. e. precise's kernel still has it as a module? So it seems to me that this doesn't affect precise at all. But even if it would, if such a cosmetical bug hasn't caused trouble in 2.5 years, it's certainly going to be fine for the other 1.5 years. ** Also affects: udev (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: udev (Ubuntu Utopic) Importance: Undecided Assignee: Dariusz Gadomski (dgadomski) Status: Confirmed ** Also affects: systemd (Ubuntu Utopic) Importance: Undecided Assignee: Dariusz Gadomski (dgadomski) Status: New ** Changed in: systemd (Ubuntu Utopic) Status: New => Fix Committed ** Changed in: systemd (Ubuntu Trusty) Status: New => Triaged ** Changed in: systemd (Ubuntu Trusty) Importance: Undecided => Low ** No longer affects: udev (Ubuntu Utopic) ** No longer affects: udev (Ubuntu Trusty) ** Also affects: udev (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: udev (Ubuntu) Status: Confirmed => Invalid ** Changed in: udev (Ubuntu Precise) Status: New => Incomplete ** No longer affects: systemd (Ubuntu Precise) -- 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 Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Incomplete 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp