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 GadomskiFri, 12 Sep 2014
13:29:08 +0200
** Changed in: udev (Ubu
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
Bugs, which
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367241
Title:
Incorrect udev-fallback-graphics
** Tags added: cts
--
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
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 GadomskiFri, 12 Sep 2014
13:31:52 +0200
** Changed in:
** Tags removed: verification-needed
** Tags added: verification-needed-precise
--
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 notifica
TWC Service verified trusty. Adding correct tag.
** Tags added: verification-done-trusty
--
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 manag
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 applie
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-do
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367241
Title:
Incorrect udev-fallback-
TWC Service, which package and version did you test?
--
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:
This resolves our issue, so +1 on the migration from proposed.
--
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
seems like the changes got uploaded, unsubscribing sponsors
--
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/136724
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 PittThu, 18
** Branch linked: lp:ubuntu/precise-proposed/udev
--
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:
ht
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.u
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://
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 (U
I have uploaded new patches updated as agreed.
--
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
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
Bugs, which is
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367241
Title:
Incorrect udev-fallback-graphics.conf
To manage notific
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
> 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
> 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
2>&1; then modprobe -q vesafb; fi"
--
You received this bug notification because you are a member of Ubuntu
Bu
Building vesafb as a module should still be possible.
Trusty had vesafb build in the kernel from the very first release, so I
believe the assumption is safe here.
Regarding precise:
Instead of removing the script I could leave it but alter it to check the
feature (e.g. kernel version number or t
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
Bug
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
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
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
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
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 man
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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 notificati
Adding SRU proposal for Trusty.
** Patch added: "systemd_204-5ubuntu20.7.debdiff"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4201485/+files/systemd_204-5ubuntu20.7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
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).
+
Adding SRU proposal for Utopic.
** Patch added: "systemd_208-8ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4201487/+files/systemd_208-8ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Adding SRU proposal for Trusty.
--
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.launchp
** Changed in: udev (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: udev (Ubuntu)
Status: New => Confirmed
--
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:
Incor
39 matches
Mail list logo
