** Branch linked: lp:ubuntu/sysvinit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/203323
Title:
fsck/usplash: device names not fully reported
To manage notifications about this bug go to:
** Branch unlinked: lp:~ubuntu-branches/ubuntu/karmic/sysvinit/karmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/203323
Title:
fsck/usplash: device names not fully reported
--
ubuntu-bugs
** Branch linked: lp:ubuntu/karmic/sysvinit
--
fsck/usplash: device names not fully reported
https://bugs.launchpad.net/bugs/203323
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for the logsave patch. It's probably a good idea to apply it (in
Debian, preferably), but I think I'll stick to the direct fsck.ext[23]
killing in the usplash fsck integration. If I would kill the entire fsck
-A, then one ESC would abort *all* checks, not just the one on the
current
This bug was fixed in the package e2fsprogs - 1.40.8-2ubuntu2
---
e2fsprogs (1.40.8-2ubuntu2) hardy; urgency=low
* Fix progress information when fsck'ing multiple partitions. (LP: #203323)
* Treat ext4 and ext4dev file systems as fsck'able.
* Patches taken from upstream bug
The logsave patch is in the e2fsprogs maint branch so it will be in the
next release of Debian unstable's e2fsprogs, and/or e2fsprogs 1.40.9.
Best regards,
-- Ted
--
fsck/usplash: device names not fully reported
https://bugs.launchpad.net/bugs/203323
You received this bug notification because
Ah, this happens if fstab specifies different check order priorities for
different partitions (by default all non-root FSes are priority 2 and
thus checked in parallel).
--
fsck/usplash: device names not fully reported
https://bugs.launchpad.net/bugs/203323
You received this bug notification
In the case where several devices are e2fsck'ed in parallel, using fsck
-A -C3 only reports progress for the first device; there is no further
output on FD 3 for the other devices. This causes usplash to not report
any progress in this case, which is difficult to work around in the
usplash
** Bug watch added: SourceForge.net Tracker #1926023
http://sourceforge.net/support/tracker.php?aid=1926023
** Also affects: e2fsprogs via
http://sourceforge.net/support/tracker.php?aid=1926023
Importance: Unknown
Status: Unknown
--
fsck/usplash: device names not fully reported
This bug was fixed in the package sysvinit - 2.86.ds1-14.1ubuntu42
---
sysvinit (2.86.ds1-14.1ubuntu42) hardy; urgency=low
* debian/initscripts/lib/init/usplash-fsck-functions.sh:
- When pressing ESC, do not kill the logsave command (since this does not
reliably kill the
- When pressing ESC, do not kill the logsave command (since this does not
reliably kill the subprocess), but the fsck.ext[23] processes directly.
(LP: #203322)
The following attached bug should address this issue in logsave as well.
It may help you since otherwise you're probably
** Changed in: sysvinit (Ubuntu)
Status: New = In Progress
--
fsck/usplash: device names not fully reported
https://bugs.launchpad.net/bugs/203323
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
12 matches
Mail list logo
