[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
This bug was fixed in the package udev - 175-0ubuntu9.7 --- udev (175-0ubuntu9.7) precise; urgency=low * udev-fallback-graphics.conf: Avoid failure if vesafb module is compiled in. (LP: #1367241). -- Dariusz Gadomski dariusz.gadom...@canonical.com Fri, 12 Sep 2014 13:29:08 +0200 ** Changed in: udev (Ubuntu Precise) Status: Fix Committed = Fix Released -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Released Status in “systemd” source package in Trusty: Fix Released Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Verification done for Precise ** Changed in: udev (Ubuntu Precise) Assignee: (unassigned) = Bartosz Kosiorek (gang65) ** Tags removed: verification-needed-precise ** Tags added: verification-done-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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Released Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
** Branch linked: lp:ubuntu/trusty-proposed/systemd ** Branch linked: lp:ubuntu/utopic-proposed/systemd -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Released Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
** Tags added: cts -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Released Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
This bug was fixed in the package systemd - 204-5ubuntu20.7 --- systemd (204-5ubuntu20.7) trusty; urgency=medium * udev-fallback-graphics.conf: Avoid failure if vesafb module is compiled in. (LP: #1367241). -- Dariusz Gadomski dariusz.gadom...@canonical.com Fri, 12 Sep 2014 13:31:52 +0200 ** Changed in: systemd (Ubuntu Trusty) Status: Fix Committed = Fix Released -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Released Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
TWC Service verified trusty. Adding correct tag. ** Tags added: verification-done-trusty -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
** Tags removed: verification-needed ** Tags added: verification-needed-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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
This script cannot be simply removed, other parts of the boot recovery rely on the events it triggers by existing. Removing this wholesale breaks plymouth-splash.conf in the face of no primary displays being detected, and prevents us from loading the display manager of choice. The fix as applied in the SRUs works correctly. There is a new bug filed for the fallout from this in utopic. Bug #1375805. We will use that one to reinstate it and fix it to match the SRU fix here. -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
@TWC Service Thank you for checking this. ** Tags removed: verification-needed ** Tags added: verification-done -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Its not clear for which release the verification of this SRU took place, so I'm changing the tag back to verification-needed. Since this is being fixed in two releases the tag verification-done-precise or verification-done-trusty should be added to the bug report. ** Tags removed: verification-done ** Tags added: verification-needed -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
TWC Service, which package and version did you test? -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
This resolves our issue, so +1 on the migration from proposed. -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
I have verified this on my machines, although I still wait for a verification from a user. I will update this issue after getting the confirmation. -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Hello Dariusz, or anyone else affected, Accepted udev into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/udev/175-0ubuntu9.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: udev (Ubuntu Precise) Status: In Progress = Fix Committed -- 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: Fix Committed Status in “systemd” source package in Trusty: Fix Committed 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
** Branch linked: lp:ubuntu/precise-proposed/udev -- 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: Fix Committed Status in “systemd” source package in Trusty: Fix Committed 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
This bug was fixed in the package systemd - 208-8ubuntu4 --- systemd (208-8ubuntu4) utopic; urgency=medium * debian/tests/boot-and-services: Accept lower-case spelling of command line in dmesg log. Curiously the case differs between amd64 and i386.. -- Martin Pitt martin.p...@ubuntu.com Thu, 18 Sep 2014 21:10:42 +0200 ** Changed in: systemd (Ubuntu Utopic) Status: Fix Committed = Fix Released -- 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 Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Released 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Hello Dariusz, or anyone else affected, Accepted systemd into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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: In Progress Status in “systemd” source package in Trusty: Fix Committed 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Thanks Martin for taking a look. In my precise (12.04.5) install the default kernel is 3.13.0-32-generic, which is affected by the issue: $ grep FB_VESA /boot/config-3.13.0-32-generic CONFIG_FB_VESA=y In fact initially this has been reported by a CTS customer for 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
I'm still not fully convinced about the SRUs -- this might have a potential to break existing setups if they run custom kernels? It's ok to add the expectancy to build in vesafb for a new release (utopic), but not for existing stables? Or is it impossible to build vesafb as a module now? -- 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: 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 -- 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Ah right, that's the backported trusty kernels I figure (12.04.4 or later). ** Changed in: udev (Ubuntu Precise) Status: Incomplete = Triaged ** Changed in: udev (Ubuntu Precise) Importance: Undecided = Low -- 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: 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 -- 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Trusty had vesafb build in the kernel from the very first release, so I believe the assumption is safe here. Well no, one could still run a self-built kernel. So I think for an SRU it would be safer to not drop the script, but instead do some 2/dev/null to quiesce the error. -- 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: 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 -- 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
do some 2/dev/null to quiesce the error. or if that's not possible (because it's the kernel who spits out errors, but that's unlikely), it could also do if modinfo vesafb /dev/null 21; then modprobe -q vesafb; fi -- 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: 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 -- 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
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 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: 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 -- 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Right, protecting this with || true sounds perfectly fine and safe for an SRU. -- 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: 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 -- 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
I have uploaded new patches updated as agreed. -- 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: 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 -- 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Adding new SRU proposal for Precise. ** Patch removed: systemd_204-5ubuntu20.7.debdiff https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4201485/+files/systemd_204-5ubuntu20.7.debdiff ** Patch removed: udev_175-0ubuntu9.7.debdiff https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4201483/+files/udev_175-0ubuntu9.7.debdiff ** Patch added: udev_175-0ubuntu9.7.debdiff https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4202152/+files/udev_175-0ubuntu9.7.debdiff -- 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: 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 -- 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Adding new SRU proposal for Trusty. ** Patch added: systemd_204-5ubuntu20.7.debdiff https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4202154/+files/systemd_204-5ubuntu20.7.debdiff -- 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: 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 -- 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
I sponsored these with changing the changelog to * udev-fallback-graphics.conf: Avoid failure if vesafb module is compiled in. (LP: #1367241). as removed the script isn't true with those. ** Changed in: systemd (Ubuntu Trusty) Status: Triaged = In Progress ** Changed in: udev (Ubuntu Precise) Status: Triaged = In Progress -- 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: In Progress Status in “systemd” source package in Trusty: In Progress 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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: New Status in “udev” package in Ubuntu: Confirmed 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
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Dariusz Gadomski (dgadomski) -- 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: New Status in “udev” package in Ubuntu: Confirmed 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
