This is not a mountall bug (there is no postinst!)
** Package changed: mountall (Ubuntu) = ubuntu
--
Release upgrade converts /dev/mapper entries in /etc/fstab to UUID
https://bugs.launchpad.net/bugs/563117
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm pretty sure this is deliberate. It allows you to move a filesystem
from a /dev/mapper device to a raw device later on (which is the kind of
thing we want to support)
--
Release upgrade converts /dev/mapper entries in /etc/fstab to UUID
https://bugs.launchpad.net/bugs/563117
You received
Steve: your log simply says that udev never issued an event for your
/home
--
Loops on mount failure when Plymouth not running
https://bugs.launchpad.net/bugs/553290
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Ok, this one is quite easy.
The fsck fails, and because it opened the block device for writing, udev
tells mountall to try it again - spawning fsck
We shouldn't spawn fsck or mount while mnt-error is set, and the
plymouth keys function should clear the error before running with fix
--
Aha, I see the problem!
- if (mnt-tag != TAG_SKIPPED)
- all = FALSE;
should be:
- if (mnt-tag != TAG_SKIPPED)
- all = FALSE;
+
** Changed in: mountall (Ubuntu Lucid)
Status: Triaged = Fix Committed
--
mountall needs to flush plymouth message queue before emitting upstart events
https://bugs.launchpad.net/bugs/559761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: mountall (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: mountall (Ubuntu)
Milestone: None = ubuntu-10.04
--
Infinite-loops in fsck when booting with damaged /
https://bugs.launchpad.net/bugs/501801
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 501801 ***
https://bugs.launchpad.net/bugs/501801
** This bug has been marked a duplicate of bug 501801
Infinite-loops in fsck when booting with damaged /
--
Infinite loop on root fs with Dupliate or bad block
https://bugs.launchpad.net/bugs/564627
You
You said:
* For each filesystem mentioned in fstab that depends on a an array
This is the problem; fstab only gives us a filesystem UUID or LABEL in
many cases, we simply *DO NOT KNOW* that's going to turn out to be on a
RAID array.
--
degraded NON-root raids never --run on boot
mountall now doesn't process any input itself and only uses plymouth to
do this
** Changed in: mountall (Ubuntu)
Status: Incomplete = Fix Released
--
lynx goes to a root shell
https://bugs.launchpad.net/bugs/492745
You received this bug notification because you are a member of Ubuntu
The assertion error that caused this has been fixed.
It's not supposed to be possible to ever get both a maintenance shell
and the getty (since that depends on mountall exiting) - you hit a rare
bug that's been fixed
** Changed in: mountall (Ubuntu)
Status: Confirmed = Fix Released
--
Thanks for the bug report, and sorry about the delay getting to it.
You haven't given much details here - what error does the filesystem
check fail with? What filesystem type are you using?
** Changed in: mountall (Ubuntu)
Status: New = Incomplete
** Summary changed:
- Filesystem check
Thanks for all your debugging work Anand, from the information you
collected I believe that Johan's hunch was right and your bug was that
mountall was locking up waiting for your root filesystem and never
continuing once it appeared
This bug was fixed recently, so hopefully your problems should
Thanks for the report.
From the information you've given, it simply looks like your /etc/fstab
is wrong; or your /boot is corrupted
** Changed in: mountall (Ubuntu)
Status: New = Invalid
--
Mounts in /etc/fstab cannot yet be mounted
https://bugs.launchpad.net/bugs/505751
You received
This will now prompt for you, asking whether you'd like to continue or
drop to a shell
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
boot stops due to failed mounting of a sshfs partition
https://bugs.launchpad.net/bugs/507613
You received this bug notification because
This has been changed rather a lot to use Plymouth - and reports of it
working properly are wide-spread
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
System freezes if some file systems cannot be mounted
https://bugs.launchpad.net/bugs/517602
You received this bug
Sorry, we simply do not support earlier kernel versions. The plumbing
layer is now tightly integrated with the kernel; we had an option to
either support kernel upgrades or downgrades, we chose to support
upgrades since updating a kernel is common
** Changed in: mountall (Ubuntu)
Status:
mount failures now result in a prompt whether to continue ignoring the
filesystem or to drop to a shell
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
Mount filesystem failed
https://bugs.launchpad.net/bugs/514871
You received this bug notification because you are a
From the bug description, this sounds like an issue with the karmic
mountall where it would continue when it shouldn't - this has been fixed
in Lucid
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
Startup in Karmic with unclean filesystems leaves system in a wrong state
On Fri, 2010-04-16 at 22:14 +, Paul Sladen wrote:
Scott: does that fix the -server case where plymouth was never
present/installed/enabled in the first place?
mountall Depends: plymouth
So this is an impossible situation to get into.
Scott
--
Scott James Remnant
sc...@ubuntu.com
Dear Reddit, the above does not mean I've marked it Won't Fix - it means
I've moved the bug status back to tracking outside of Lucid since this
is very unlikely to be fixed by the time Lucid releases ;-)
** Changed in: mountall (Ubuntu Lucid)
Assignee: Canonical Foundations Team
** Changed in: mountall (Ubuntu)
Status: New = Confirmed
** Changed in: mountall (Ubuntu)
Importance: Undecided = Medium
--
Mountall does not mount NFS file systems when booting from network
https://bugs.launchpad.net/bugs/519582
You received this bug notification because you are a
** Changed in: mountall (Ubuntu)
Importance: Undecided = Medium
** Changed in: mountall (Ubuntu)
Status: New = Confirmed
--
remounts don't work with mountall
https://bugs.launchpad.net/bugs/519380
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: mountall (Ubuntu)
Importance: Undecided = Medium
--
Filesystem check fails every boot
https://bugs.launchpad.net/bugs/505380
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: mountall (Ubuntu)
Importance: Undecided = Medium
--
/etc/init/mountall.conf fails when root is mounted using NFS instead of NBD
https://bugs.launchpad.net/bugs/485709
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Could you attach a copy of the /etc/fstab that fails for me?
** Changed in: mountall (Ubuntu)
Status: New = Incomplete
** Changed in: mountall (Ubuntu)
Importance: Undecided = Medium
--
[lucid] Adding vboxsf in fstab stops boot process
https://bugs.launchpad.net/bugs/530179
You
If partitions are not visible, this is a kernel issue
** Package changed: mountall (Ubuntu) = linux (Ubuntu)
--
[ubuntu lucid] SD card not recognized in netbook
https://bugs.launchpad.net/bugs/529447
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Will not be fixed in Lucid, move back to tracking in head
** Changed in: mountall (Ubuntu Lucid)
Status: Triaged = Won't Fix
--
/etc/init/mounted-tmp.conf uses find, which is in /usr/bin
https://bugs.launchpad.net/bugs/523587
You received this bug notification because you are a member of
Thanks for the report, unfortunately there really isn't enough
information here to determine what kind of problem you're having.
If you're seeing error messages on the screen, please copy them exactly
- there is no Failed to start error message anywhere in Ubuntu, which
means I can't begin to
** Changed in: mountall (Ubuntu)
Status: New = Confirmed
** Changed in: mountall (Ubuntu)
Importance: Undecided = Medium
--
mountall issues with nfsroots
https://bugs.launchpad.net/bugs/537133
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the report, while there isn't much information in it, it
seems you've had a problem with a filesystem failing to mount on boot.
This has been addressed in 10.04, with a much better recovery system for
these kinds of problems.
** Changed in: mountall (Ubuntu)
Status: New = Fix
Err, sorry, I appear to have confused two bugs - this is a network mount
so should be retried
** Changed in: mountall (Ubuntu)
Status: Fix Released = Confirmed
--
boot stops due to failed mounting of a sshfs partition
https://bugs.launchpad.net/bugs/507613
You received this bug
If you change the fstab line to:
sshfs#skip...@deep-thought:/home/skipper/archive /home/skipper/archive
fuse allow_other,ro,_netdev 0 0
does it work?
--
boot stops due to failed mounting of a sshfs partition
https://bugs.launchpad.net/bugs/507613
You received this bug notification because you
I've uploaded a new version of mountall (2.13~ppa1) to
https://launchpad.net/~scott/+archive/ppa
Please test and see whether it solves this problem
Thanks
--
mountall needs to flush plymouth message queue before emitting upstart events
https://bugs.launchpad.net/bugs/559761
You received this
I've uploaded a new version of mountall (2.13~ppa1) to
https://launchpad.net/~scott/+archive/ppa
Please test and see whether it solves this problem
Thanks
--
Loops on mount failure when Plymouth not running
https://bugs.launchpad.net/bugs/553290
You received this bug notification because you
James Remnant
sc...@ubuntu.com
--
Mounts in /etc/fstab cannot yet be mounted
https://bugs.launchpad.net/bugs/505751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
I've uploaded a new version of mountall (2.13~ppa1) to
https://launchpad.net/~scott/+archive/ppa
Please test and see whether it solves this problem
Thanks
--
Infinite-loops in fsck when booting with damaged /
https://bugs.launchpad.net/bugs/501801
You received this bug notification because you
Ok, according to the mount manpage, that's necessary for mount to *know*
it's a network device (since it's fuse)
** Changed in: mountall (Ubuntu)
Status: Confirmed = Invalid
--
boot stops due to failed mounting of a sshfs partition
https://bugs.launchpad.net/bugs/507613
You received this
Thanks for the report.
From the information you've given, it sounds like mountall is timing out
on the device and prompting for action - however in older versions, this
wouldn't continue to wait while prompting - this has been fixed
** Changed in: mountall (Ubuntu)
Status: New = Fix
Do you see the Plymouth splash screen?
Could you supply the output of ls -l /lib/plymouth/themes
Also could you modify /etc/init/mountall.conf - add --debug to the end of the
exec line, then after booting attach /var/log/boot.log
(with the usbfs entry in, obviously)
** Changed in: mountall
Thanks for your report.
While it's slightly confusing as to what your problem might be, I
believe this to be fsck being run 21 times? This has been recently
fixed
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
mountall:job failed to start couldn't access pid files
Thanks for the report.
From the information you've given, it seems that mountall has timed out
(assumedly the device hasn't been set up yet) - in Beta 1 this would
hang instead of continuing to wait and this has been fixed.
Zak: from your comment, it sounds like you have a different problem
*** This bug is a duplicate of bug 537133 ***
https://bugs.launchpad.net/bugs/537133
** This bug has been marked a duplicate of bug 519582
Mountall does not mount NFS file systems when booting from network
** This bug is no longer a duplicate of bug 519582
Mountall does not mount NFS
I have reassigned this bug to open-iscsi
From the report, it appears that mountall has actually run mount for
this device - and it's the mount that fails.
This implies an error with the event being sent too early?
** Package changed: mountall (Ubuntu) = open-iscsi (Ubuntu)
--
10.04 beta 1
(the assertion error has been fixed)
--
10.04 beta 1 mountall fails to mount iSCSI volume at boot
https://bugs.launchpad.net/bugs/547091
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 537133 ***
https://bugs.launchpad.net/bugs/537133
** This bug has been marked a duplicate of bug 537133
mountall issues with NFS root filesystem
--
Mountall does not mount NFS file systems when booting from network
https://bugs.launchpad.net/bugs/519582
Added a task for portmap; since that ships its configuration file and is
responsible for when portmap is started. Since portmap is only on the
root filesystem and only doesn't write to it, I think you're probably
correct that this should use virtual-filesystems
Obviously the root filesystem
I'd like to know why there was no SIGCHLD/wait() for the mount of the
root filesystem, are you sure that it wasn't still running?
--
mountall issues with NFS root filesystem
https://bugs.launchpad.net/bugs/537133
You received this bug notification because you are a member of Ubuntu
Bugs, which
The mountall portion of this bug is better described by bug #537133 -
however there's no way to only mark that task a dup
** Changed in: mountall (Ubuntu)
Status: Confirmed = Invalid
--
/etc/init/mountall.conf fails when root is mounted using NFS instead of NBD
Could you attach your /etc/fstab file?
** Changed in: mountall (Ubuntu)
Status: New = Incomplete
** Changed in: mountall (Ubuntu)
Importance: Undecided = Medium
--
Not performing fsck on startup
https://bugs.launchpad.net/bugs/549824
You received this bug notification because you are
nomnex: thanks for the tar files - I think you had a transient problem
which has been since fixed - changing to the label was enough to get the
device mounted and fix the problem
** Changed in: ubuntu
Status: New = Fix Released
--
One or more of the mounts listed in /etc/fstab cannot yet
of this one?
Thanks!
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Mounts in /etc/fstab cannot yet be mounted
https://bugs.launchpad.net/bugs/505751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Ah, thanks very much Endolith
What's happened is that when /boot was created, it wasn't properly
cleaned up so it's not possible for blkid to determine the filesystem
type (and thus the UUID)
Here's how to fix that:
sudo -s
(will give you a root shell)
# tar czf /boot.tar.gz /boot
#
Invalid Argument from aufs sounds kernely to me
** Package changed: mountall (Ubuntu) = linux (Ubuntu)
--
(initramfs) mounting aufs on /root failed: Invalid argument aufs mount failed
https://bugs.launchpad.net/bugs/560954
You received this bug notification because you are a member of Ubuntu
This was caused by a deadlock flushing the 100% message out to
plymouth which has been recently fixed
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
file system check hangs during boot for raid1 devives
https://bugs.launchpad.net/bugs/557375
You received this bug
*** This bug is a duplicate of bug 501801 ***
https://bugs.launchpad.net/bugs/501801
** This bug has been marked a duplicate of bug 501801
Infinite-loops in fsck when booting with damaged /
--
fsck infinite loop at boot time / complains about -a and -p options
The flashing should be fixed now
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
Text message when hard drive as an UNEXPECTED INCONSISTENCY flashes
https://bugs.launchpad.net/bugs/553721
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The keys are not ever printed to the screen - and are intended to be
fixed; these should not be translated
** Changed in: mountall (Ubuntu)
Status: New = Invalid
--
Hotkeys not marked for translation
https://bugs.launchpad.net/bugs/563732
You received this bug notification because you
Could you please add those cryptic numbers to the bug report? They
could be important!
Note that it's intended that an error mounting a filesystem *is* output
to the boot screen, with a choice of how to proceed. Since this isn't
happening for you, I will need more details to debug your problem.
Could you please describe what you mean by failed to boot.
You say that you see a message about the filesystem, what is that
message? (Please copy it exactly)
If the message offers you to wait, what happens if you wait?
What happens if you press each of the keys?
** Changed in: mountall
Thanks for the bug report, unfortunately it's really not clear to me
what problem you're attemping to report here. If you're having an X
server crash, then that should be filed against the X server.
Please take a read of
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
** Changed in:
Marking Invalid due to lack of information from the reporter.
Please read http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
** Changed in: mountall (Ubuntu)
Importance: Undecided = High
** Changed in: mountall (Ubuntu)
Status: Incomplete = Invalid
--
Pressing F to fix hard drive
I don't see any evidence of a mountall bug here - this sounds like an
lvm2 issue
** Package changed: mountall (Ubuntu) = lvm2 (Ubuntu)
--
When snapshots exists, mountall will not mount the parent partition
https://bugs.launchpad.net/bugs/563902
You received this bug notification because you are
Sorry, slipped on the status there.
** Changed in: mountall (Ubuntu)
Status: Confirmed = Invalid
** Changed in: mountall (Ubuntu)
Status: Invalid = Triaged
** Changed in: mountall (Ubuntu)
Importance: Undecided = Low
** Changed in: mountall (Ubuntu)
Status: Triaged =
Unfortunately without the crash report, it's impossible to debug this
further. This should have appeared in /var/crash (and given you a popup
on login)
** Changed in: mountall (Ubuntu)
Status: Incomplete = Invalid
--
Boot fails when you use hex code in /etc/fstab
** Package changed: mountall (Ubuntu) = plymouth (Ubuntu)
--
could not write byte broken pipe
https://bugs.launchpad.net/bugs/521298
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Could you supply a copy of your /etc/fstab
--
boot fails [...] ureadahead [...] terminated with status 5
https://bugs.launchpad.net/bugs/542334
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: ureadahead (Ubuntu)
Status: New = Triaged
** Changed in: ureadahead (Ubuntu)
Importance: Undecided = Wishlist
--
Trace should ignore files in /var/log
https://bugs.launchpad.net/bugs/559525
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks for the info; need to look through this
** Changed in: ureadahead (Ubuntu)
Status: Incomplete = Confirmed
--
Boot speed increased from 30s to 50s when ureadahead enabled
https://bugs.launchpad.net/bugs/552165
You received this bug notification because you are a member of Ubuntu
Clearly not relative paths then ;-/
** Changed in: ureadahead (Ubuntu)
Status: Incomplete = Confirmed
** Summary changed:
- not all files in /home not profiled/traced (relative paths?)
+ not all files in /home not profiled/traced
--
not all files in /home not profiled/traced
** Package changed: e2fsprogs (Ubuntu) = mountall (Ubuntu)
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
Spelling error in startup Disk Check
https://bugs.launchpad.net/bugs/564205
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Package changed: e2fsprogs (Ubuntu) = plymouth (Ubuntu)
--
Fsck does not respond to C key (to cancel disk scan)
https://bugs.launchpad.net/bugs/555753
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
When fsck fails, you see a message giving you the option to try again
with -y (to fix) or drop to a root shell
** Changed in: e2fsprogs (Ubuntu)
Status: New = Invalid
--
when fsck finds a problem during boot, there is no possibility to run it
manually to fix it.
** Package changed: e2fsprogs (Ubuntu) = plymouth (Ubuntu)
** Changed in: plymouth (Ubuntu)
Status: New = Fix Released
--
system hang on init, start screen (automatic check 80%)
https://bugs.launchpad.net/bugs/554753
You received this bug notification because you are a member of Ubuntu
** Package changed: e2fsprogs (Ubuntu) = mountall (Ubuntu)
** Changed in: mountall (Ubuntu)
Status: Confirmed = Fix Released
--
fsck complains some errors can't be fixed, then loops
https://bugs.launchpad.net/bugs/554349
You received this bug notification because you are a member of
** Package changed: e2fsprogs (Ubuntu) = mountall (Ubuntu)
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
fsck doesn't finish
https://bugs.launchpad.net/bugs/543583
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since cron is clearly invoking sendmail and that invokes postfix, I'm
guessing it goes missing inside postfix somewhere
** Package changed: cron (Ubuntu) = postfix (Ubuntu)
--
cron doesn't send mail
https://bugs.launchpad.net/bugs/520273
You received this bug notification because you are a
** Package changed: module-init-tools (Ubuntu) = ndiswrapper (Ubuntu)
--
does not terminate at computer shutdown
https://bugs.launchpad.net/bugs/561480
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Seem like a valid request to me, I'll add this as a wishlist to Upstart
** Summary changed:
- start debug options do not work
+ initctl: debugging start should show commands run
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New =
** Package changed: module-init-tools (Ubuntu) = mountall (Ubuntu)
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
lucid kernel hangs during boot when viafb is inserted
https://bugs.launchpad.net/bugs/556184
You received this bug notification because you are a member of
The module itself says what it should be used for
** Package changed: module-init-tools (Ubuntu) = linux (Ubuntu)
--
Dlink DWA-125 (07d1:3c0d) is processed by wrong module
https://bugs.launchpad.net/bugs/546653
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bear in mind that Upstart would have to be the initramfs /init just as
its the real system /sbin/init - it has to be PID 1
One of the main pre-requisites for this is state passing; so that the
upstart in the initramfs would be able to re-exec itself once the root
is mounted and then pass its
Neither 7.04 nor 7.10 are supported anymore
** Changed in: module-init-tools (Ubuntu)
Status: New = Invalid
--
Server upgrade from 7.04 to 7.10 fails
https://bugs.launchpad.net/bugs/187316
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Vistaus: by setting this bug to Confirmed, you actually prevented the
kernel team from seeing this bug -- this is why this has been held up
for so long
one obvious solution is that -generic should have a desktop-y
swappiness, while -server should have a server-y one
** Changed in: linux (Ubuntu)
We do not ordinarily backport changes to released versions of Ubuntu;
unfortunately module-init-tools has changed too much recently (many
rewrites) to be consider for an SRU
** Changed in: module-init-tools (Ubuntu)
Status: In Progress = Fix Released
--
module-init-tools post-install
*** This bug is a duplicate of bug 501801 ***
https://bugs.launchpad.net/bugs/501801
looping on failing fsck is bug #501801 which has the needed debug
information, so marking as dup
** This bug has been marked a duplicate of bug 501801
Infinite-loops in fsck when booting with damaged /
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) = Scott James Remnant (scott)
--
Infinite-loops in fsck when booting with damaged /
https://bugs.launchpad.net/bugs/501801
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Robert: that's not a nasty hack - that's the canon way to work around
this issue - this should be identical to just doing:
[options]
broken_system_clock = true
which will set preen_ok for those two problems
--
there is no way to tell fsck to ignore broken clocks on embedded systems
This is not a mountall issue, if e2fsck's broken_system_clock=true
option is not working, that's an e2fsck bug
** Changed in: mountall (Ubuntu Lucid)
Status: Confirmed = Invalid
--
there is no way to tell fsck to ignore broken clocks on embedded systems
)
Assignee: (unassigned) = Scott James Remnant (scott)
--
there is no way to tell fsck to ignore broken clocks on embedded systems
https://bugs.launchpad.net/bugs/563618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
the hardware clock again, so we do it all over
again in a loop.
There isn't a fix for this :-(
** Changed in: util-linux (Ubuntu Lucid)
Assignee: Scott James Remnant (scott) = (unassigned)
** Changed in: util-linux (Ubuntu Lucid)
Milestone: ubuntu-10.04 = None
** Changed in: util-linux (Ubuntu
Steve: to confirm, it caused mountall to never mount any of your
filesystems even if plymouth was running?
Or just when Plymouth isn't running?
--
Loops on mount failure when Plymouth not running
https://bugs.launchpad.net/bugs/553290
You received this bug notification because you are a member
Oh, when plymouth is running is certainly not intended.
When plymouth isn't running - I'd expect it to not mount any filesystem
that took too long
Can you get --debug from the machines where you reproduced please
--
Loops on mount failure when Plymouth not running
This is an LVM issue - mountall doesn't get involved in LVM bring-up *at
all*, it only mounts the resulting filesystems once they appear.
It's up to LVM to activate devices as it goes
--
power g5 does not boot lucid beta
https://bugs.launchpad.net/bugs/554478
You received this bug notification
** Changed in: plymouth (Ubuntu Lucid)
Status: Triaged = Fix Committed
--
script splash needs to expose the renderer's bpp
https://bugs.launchpad.net/bugs/558352
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
New 16-color artwork committed
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) = Scott James Remnant (scott)
** Changed in: plymouth (Ubuntu)
Milestone: None = ubuntu-10.04
** Changed in: plymouth (Ubuntu)
Status: Triaged = Fix Committed
--
ubuntu-logo on VGA fb
Have given up with this SRU. Anyone affected can upgrade to Lucid soon
enough.
** Changed in: mountall (Ubuntu Karmic)
Status: Triaged = Won't Fix
** Changed in: mountall (Ubuntu Karmic)
Assignee: Scott James Remnant (scott) = (unassigned)
** Changed in: mountall (Ubuntu Karmic
** Changed in: upstart
Status: New = Fix Released
--
doc: Upstart lacks documentation
https://bugs.launchpad.net/bugs/60429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On Mon, 2010-04-12 at 13:52 +, Simon Oosthoek wrote:
I'd like to see this bug re-opened, because there's still not sufficient
documentation and some aspects of upstart indicate that it may be
immature for a LTS release (IMHO).
If there are key areas of missing documentation that should
I'm not sure why you've filed this on Upstart, since you seem sure it's
a Kernel issue and your description to me does sound like it's a kernel
driver bug hanging the machine if the resolution is wrong
Reassigning over to the kernel
** Package changed: upstart (Ubuntu) = linux (Ubuntu)
--
401 - 500 of 6846 matches
Mail list logo
