wait-for-root simply waits for the block device to be available; that
must be succeeding because you're seeing the resume fail:
[ 0.778970] PM: Checking image partition
UUID=f0e784ed-e140-4d73-87a3-8ef047012b9f
[ 0.785267] PM: Resume from disk failed.
I noticed that your resume= and root= lines
After booting, please attach your /etc/fstab and output of running sudo
blkid
This should allow us to figure out what your resume= line *should* be
--
Resume from disk (swapfile) fails
https://bugs.launchpad.net/bugs/554009
You received this bug notification because you are a member of Ubuntu
Oh, sorry, you say you're using a swap file - in which case how do you
know that the offset of that file doesn't change between reboots - or
how do you know it's contiguous. We don't really support resume from
swap files at the moment.
Assuming that it's correct to pass the UUID of the
There is no try_udev_device line in your debug log for laplv, this
implies that LVM has not set this device up and the underlying devmapper
devices have not been created and/or announced by the kernel/udev
** Package changed: mountall (Ubuntu) = lvm2 (Ubuntu)
--
filesystem not getting mounted
Could you attach /var/log/udev from this boot?
--
filesystem not getting mounted
https://bugs.launchpad.net/bugs/567910
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
Thanks.
Please add --verbose to your kernel command-line, then after booting
attach /var/log/boot.log /var/log/syslog and /var/log/messages
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
no virtual terminals on lucid
https://bugs.launchpad.net/bugs/567047
You received this bug notification
On Wed, 2010-04-21 at 04:17 +, Stephen Gildea wrote:
It has indeed been fixed. I upgraded to mountall 2.12, and now my
system mounts /tmp and doesn't hang.
Thanks for the confirmation!
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
randomly encrypted /tmp hangs mountall
https
-W mountall
Then reboot
Thanks,
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
On Tue, 2010-04-20 at 23:46 +, Steve Langasek wrote:
Scott, would 'start on mounting TYPE=vboxsf' also work here?
Yes!
That's a really good idea, I hadn't thought of that.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[lucid] vboxsf mounts defined on /etc/fstab cause errors on boot
.
The current recovery mode is being phased out in favour of every boot
being able to be used for recovery
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[lucid] vboxsf mounts defined on /etc/fstab cause errors on boot
https://bugs.launchpad.net/bugs/530179
You received this bug notification
low
Scott
--
Scott James Remnant
sc...@ubuntu.com
** Changed in: mountall (Ubuntu)
Importance: Undecided = Low
** Changed in: mountall (Ubuntu)
Status: New = Incomplete
--
Mountall fails following early X server crash
https://bugs.launchpad.net/bugs/561359
You received this bug
** Changed in: mountall (Ubuntu Lucid)
Importance: Undecided = Medium
** Changed in: mountall (Ubuntu Lucid)
Assignee: (unassigned) = Scott James Remnant (scott)
--
Plymouth doesn't show messages sent before the splash screen is visible
https://bugs.launchpad.net/bugs/507881
You
Your fix was wrong and introduced bugs (and it isn't at all obvious to
me why this would cause a segfault) - I've had to revert it
** Changed in: mountall (Ubuntu Lucid)
Status: Fix Committed = Triaged
--
[Lucid] fsck cannot be cancelled in Plymouth
https://bugs.launchpad.net/bugs/562811
On Wed, 2010-04-21 at 11:52 +, ceg wrote:
I can't tell if the metadata has been altered. Scott do the dd files
contain data that looks altered or irregular in any way?
I wouldn't know how to tell that.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
silently breaking raid: root
Please strace this running process, e.g.
sudo strace -p 347
(where 347 is the PID from ps)
Attach a sample of the output
** Changed in: mountall (Ubuntu)
Status: New = Incomplete
** Changed in: mountall (Ubuntu)
Importance: Undecided = Medium
--
mountall keeps on running
-W mountall
Then reboot
Thanks,
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
filesystem not getting mounted
https://bugs.launchpad.net/bugs/567910
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Chatted with Steve on IRC, and realised why there was a segfault; new
fix applied
** Changed in: mountall (Ubuntu Lucid)
Status: Triaged = Fix Committed
** Changed in: mountall (Ubuntu Lucid)
Assignee: Steve Langasek (vorlon) = Scott James Remnant (scott)
--
[Lucid] fsck cannot
*** This bug is a duplicate of bug 561390 ***
https://bugs.launchpad.net/bugs/561390
** Changed in: lvm2 (Ubuntu)
Status: New = Incomplete
** Changed in: lvm2 (Ubuntu)
Importance: Undecided = High
** This bug has been marked a duplicate of bug 561390
LVM - /var failed to mount
*** This bug is a duplicate of bug 561390 ***
https://bugs.launchpad.net/bugs/561390
Thanks!
Your comment about udev not being able to deliver the message was a big
clue that the buffer size was wrong in mountall
** This bug has been marked a duplicate of bug 561390
LVM - /var failed to
Hi, Thanks for the bug report. Unfortunately the crash reporter wasn't
able to gather enough information to debug this problem, however we'll
keep an eye out for further reports of this problem and if they should
come up, we may be able to reopen this
** Changed in: anacron (Ubuntu)
The correct fix for this is to migrate to Upstart, which always starts
services with the nice level defined in their conf file, not one
inherited from the environment
** Summary changed:
- apache is restarted with nice level of 10
+ services restarted from anacron have nice level of 10
**
The correct place to suggest this feature enhancement would be to
Debian; Ubuntu plans to replace anacron in the near term.
--
New feature (require a clean exit from job)
https://bugs.launchpad.net/bugs/311059
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Has this been reported to Debian? That seems the correct place to fix
this
** Changed in: anacron (Ubuntu)
Status: New = Incomplete
** Changed in: anacron (Ubuntu)
Importance: Undecided = Medium
--
Needs file rename to conform with pm-utils
https://bugs.launchpad.net/bugs/307493
You
*** This bug is a duplicate of bug 411796 ***
https://bugs.launchpad.net/bugs/411796
Merging with the other not run if suspended/off between 6am and 8am
bug - while this one is older, the other has a suggested workaround
** This bug has been marked a duplicate of bug 411796
anacron does
Simply using .* as the regex would introduce new bugs, as editor swap
files, dpkg backup files, etc. would all be run
A better regex is required
** Changed in: anacron (Ubuntu)
Status: New = Triaged
** Changed in: cron (Ubuntu)
Status: New = Triaged
** Changed in: anacron
Could you adjust/fiddle with the stamp file then run strace
/usr/sbin/anacron for me
** Changed in: anacron (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: anacron (Ubuntu)
Importance: Undecided = Medium
--
cron.daily doesn't execute scheduled scripts
Could you give more details here?
anacron should be run regularly by /etc/cron.d/anacron - so it certainly
should *not* fail for permanently running systems
** Changed in: anacron (Ubuntu)
Status: New = Incomplete
** Changed in: anacron (Ubuntu)
Importance: Undecided = Low
--
I'm slightly confused here.
Do you mean that anacron breaks cron's @midnight support or cron's
@daily support? Which are run at the wrong time?
** Changed in: anacron (Ubuntu)
Status: New = Incomplete
** Changed in: anacron (Ubuntu)
Importance: Undecided = Low
--
anacron breaks
*** This bug is a duplicate of bug 512705 ***
https://bugs.launchpad.net/bugs/512705
** This bug has been marked a duplicate of bug 512705
dpkg-reconfiguring autoconf fails with install-info: No dir file specified;
try --help for more information.
--
autconf warning Ignoring
* Removed debian/autoconf.postinst. Everything it did applied only to
pre-etch versions of autoconf, so we can be confident that no one is
upgrading from a system that needs any of this. (This was prompted by
a spurious lintian complaint about install-info.)
** Changed in:
2.65 is now in Lucid
** Changed in: autoconf (Ubuntu)
Status: New = Fix Released
--
Compiling for AVR targets with autoconf 2.64 broken in 9.10 (Karmic).
https://bugs.launchpad.net/bugs/506452
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
2.65 is now present in Lucid
** Changed in: autoconf (Ubuntu)
Status: New = Fix Released
--
2.64 is broken, please make 2.65 available
https://bugs.launchpad.net/bugs/497482
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Thanks for the report; however it seems that this is a request for a
design of the autotools. This is far out of scope for Ubuntu, and
should be discussed upstream instead
** Changed in: autotools-dev (Ubuntu)
Status: New = Invalid
--
autogen.sh/configure workflow improvement
Thanks for the report; however it seems that this is a request for a
design of the autotools. This is far out of scope for Ubuntu, and
should be discussed upstream instead
** Changed in: autotools-dev (Ubuntu)
Status: New = Invalid
--
autogen.sh/configure prints the wrong name for
Just changing the path won't help, since bootchart can't predict what
the right path would be.
For lucid, it's probably wisest to use the latest .tgz file in
/var/log/bootchart
** Package changed: bootchart (Ubuntu) = pybootchartgui (Ubuntu)
** Changed in: pybootchartgui (Ubuntu)
Status:
I believe this to have been caused by a bad mutual upgrade between 2.13
and 2.6x; forcing the upgrade should fix the problem, and new upgrades
should not replicate it
** Changed in: autoconf2.13 (Ubuntu)
Status: Triaged = Fix Released
--
package autoconf2.13 (not installed) failed to
We've switched to only supporting the Python version of the renderer now
- I expect this was a bug in the java one that's been dropped
** Changed in: bootchart (Ubuntu)
Status: Triaged = Fix Released
--
bootchart showing incorrect time but correct chart
Note that lucid now includes Plymouth, which logs all console messages
into /var/log/boot.log
** Changed in: boot (Ubuntu)
Status: New = Fix Released
--
No boot log available
https://bugs.launchpad.net/bugs/34165
You received this bug notification because you are a member of Ubuntu
Bugs,
** Package changed: boot (Ubuntu) = linux (Ubuntu)
--
system crashes after installation
https://bugs.launchpad.net/bugs/495434
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
This was fixed with the introduction of ureadahead into karmic-updates
** Changed in: boot (Ubuntu)
Status: New = Fix Released
--
regression in boot
https://bugs.launchpad.net/bugs/05
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: boot (Ubuntu) = linux (Ubuntu)
--
boot crash
https://bugs.launchpad.net/bugs/386914
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
You should take this up with SageTV whose deb you installed.
No support can be given by Ubuntu for packages not downloading from its
archives
** Changed in: boot (Ubuntu)
Status: New = Invalid
--
Installing Sagetv (without activation key) breaks ubuntu boot-up
*** This bug is a duplicate of bug 530779 ***
https://bugs.launchpad.net/bugs/530779
** This bug has been marked a duplicate of bug 530779
init: does not wait for parent to exit when following forks
--
Message Could not connect to Plymouth
https://bugs.launchpad.net/bugs/549831
You
** Package changed: boot (Ubuntu) = linux (Ubuntu)
--
mouse / keyboard not working
https://bugs.launchpad.net/bugs/433641
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
The e2fsprogs source package contains the up-to-date e2fsprogs.pot file
It does not need to be regenerated during build
** Changed in: e2fsprogs (Ubuntu)
Status: New = Triaged
** Changed in: e2fsprogs (Ubuntu)
Importance: Undecided = Medium
** Changed in: e2fsprogs (Ubuntu)
** Changed in: e2fsprogs (Ubuntu)
Status: New = Confirmed
** Changed in: e2fsprogs (Ubuntu)
Importance: Undecided = Medium
--
debugfs crashed with SIGFPE in ext2fs_open2()
https://bugs.launchpad.net/bugs/567353
You received this bug notification because you are a member of Ubuntu
From the sounds of it, the only e2fsprogs bug then is that the man page
is wrong by claiming it's the default?
** Changed in: e2fsprogs (Ubuntu)
Status: In Progress = Triaged
** Changed in: e2fsprogs (Ubuntu)
Assignee: Phillip Susi (psusi) = (unassigned)
** Changed in: e2fsprogs
** Changed in: e2fsprogs (Ubuntu)
Status: New = Confirmed
--
mkfs.ext4 crashed with signal 7 in ext2fs_set_rec_len()
https://bugs.launchpad.net/bugs/543761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Given the statement that you see I/O error messages in dmesg, the only
conclusion is that you are experiencing a hardware failure - this is
therefore not a software issue.
You should replace your hard drive
** Changed in: e2fsprogs (Ubuntu)
Importance: Undecided = High
** Changed in:
Fixed in 1.41.11
** Changed in: e2fsprogs (Ubuntu)
Status: New = Fix Released
--
debugfs: logdump -bblock show incorrect allocation status in block bitmap
https://bugs.launchpad.net/bugs/501686
You received this bug notification because you are a member of Ubuntu
Bugs, which is
already configured bug
** Package changed: hostname (Ubuntu) = apt (Ubuntu)
--
package hostname 2.94 failed to install/upgrade:
https://bugs.launchpad.net/bugs/383393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This crash is not caused by the hostname tool; unfortunately you haven't
given enough details to determine what did crash.
Next time this happens, please file bugs using the automated crash
report tool
** Package changed: hostname (Ubuntu) = ubuntu
** Changed in: ubuntu
Status: New =
I've no idea why this has been reassigned to hostname - dnshostname can
fail, it's a bug in the krb5-config package's postinst for not dealing
with that
** Package changed: hostname (Ubuntu) = kerberos-configs (Ubuntu)
--
upgrading to 8.10
https://bugs.launchpad.net/bugs/253895
You received
When called with -s, -l, -a, etc. hostname looks up the resulting names
using the resolver (as mentioned in the man page)
Thus if you change the hostname of the system without adding the new
name and IP to /etc/hosts, hostname will fail. This is quite normal.
This is why the installer always
** Changed in: xinetd (Ubuntu)
Status: New = Confirmed
--
when sysctl net.ipv6.bindv6only=1, xinetd can not bind to both IPv4 and IPv6 on
same port
https://bugs.launchpad.net/bugs/561475
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: libtool (Ubuntu)
Status: New = Confirmed
** Changed in: libtool (Ubuntu)
Importance: Undecided = Low
** Changed in: libtool (Ubuntu)
Status: Confirmed = Triaged
--
misbuilds when /bin/sh - bash
https://bugs.launchpad.net/bugs/299931
You received this bug
These doc package errors should be fixed in lucid now reading through
the changelog
** Changed in: libtool (Ubuntu)
Status: New = Fix Released
--
Problems during install
https://bugs.launchpad.net/bugs/327987
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks for the confirmation; no idea why this was left open
** Changed in: libtool (Ubuntu)
Status: New = Invalid
--
libtoolize: `argz_.h' not found in `/usr/share/libtool/libltdl'
https://bugs.launchpad.net/bugs/307392
You received this bug notification because you are a member of
Marking fixed since 2.2.6b is in lucid
** Changed in: libtool (Ubuntu)
Status: New = Confirmed
** Changed in: libtool (Ubuntu)
Importance: Undecided = Medium
** Changed in: libtool (Ubuntu)
Status: Confirmed = Fix Released
--
test programs created incorrectly when cross
Strictly speaking, converting it to an Upstart job would be better
** Changed in: xinetd (Ubuntu)
Status: Confirmed = Triaged
--
Needs Ubuntu-style init script
https://bugs.launchpad.net/bugs/43574
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
** Changed in: mountall (Ubuntu)
Status: Incomplete = Fix Committed
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
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: Medium = Low
--
Race with ureadahead can mean that /var/lib/ureadahead/debugfs appears in
/etc/mtab
https://bugs.launchpad.net/bugs/499773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mountall (Ubuntu)
Status: Incomplete = Triaged
--
degraded NON-root raids never --run on boot
https://bugs.launchpad.net/bugs/259145
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
present today.
Why? Software you install (as root) has permission to modify any part
of the system.
This is why there's a great big warning about installing software from
untrusted sources when you try and do it.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Installing Sagetv (without
You've filed the bug, so you clearly know more about the issue than
anyone else pertinent.
If I was just to echo your bug to Debian, and Debian were to ask a
question, I wouldn't know how to respond, etc.
--
Needs file rename to conform with pm-utils
https://bugs.launchpad.net/bugs/307493
You
*** This bug is a duplicate of bug 507881 ***
https://bugs.launchpad.net/bugs/507881
** This bug has been marked a duplicate of bug 507881
Plymouth doesn't show messages sent before the splash screen is visible
--
ubuntu does not start up with failed fstab mount
Something is clearly resetting the permissions of /dev/shm - I don't
think it'll be udev, udev would have removed the t as well
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 507881 ***
https://bugs.launchpad.net/bugs/507881
The apparent hang is a plymouth bug for not showing the messsage, marked
as a duplicate.
I've no idea why the mount command fails - but that's not a mountall bug
- that's a bug in whatever provides vboxsf?
This implies that the runlevel/rc scripts have not yet been run.
Could you reboot, I assume you end up in gdm as usual? From there, run
sudo initctl list and attach the output
Thanks
** Changed in: upstart (Ubuntu)
Status: New = Incomplete
** Changed in: upstart (Ubuntu)
Importance:
Could you add --debug to the exec line in /etc/init/mountall.conf then
attach /var/log/boot.log
** Changed in: mountall (Ubuntu)
Status: New = Incomplete
** Changed in: mountall (Ubuntu)
Importance: Undecided = Medium
--
After Upgrading to mountall 2.13 mountall consumes 100% CPU
Yes it does:
in main() src/mountall.c calls:
nih_main_init (argv[0]);
this is a macro in nih/main.h that expands out to:
setlocale (LC_ALL, ); \
bindtextdomain (PACKAGE_NAME, LOCALEDIR); \
textdomain (PACKAGE_NAME); \
?
Because I think the only fix is to start plymouth in the initramfs
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Plymouth doesn't show messages sent before the splash screen is visible
https://bugs.launchpad.net/bugs/507881
You received this bug notification because you are a member of Ubuntu
Bugs
.
** Package changed: plymouth (Ubuntu) = mountall (Ubuntu)
If you've been able to replicate this (I haven't), could you trace the
mountall side too? Alternatively let me know how to replicate it :-)
Scott
--
Scott James Remnant
sc...@ubuntu.com
** Changed in: mountall (Ubuntu)
Status
that should prevent a proper raid setup. One that will
--run unchanged arrays that come up degraded on reboot and are needed
for a clean boot.
Patches Welcome.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
degraded NON-root raids never --run on boot
https://bugs.launchpad.net/bugs/259145
You
mountall doesn't care about modular filesystems; it sounds like
virtualbox-guest-additions needs an Upstart job to load the module on
starting mountall
** Changed in: mountall (Ubuntu)
Status: Incomplete = Invalid
--
[lucid] vboxsf mounts defined on /etc/fstab cause errors on boot
** Also affects: mountall (Ubuntu)
Importance: Undecided
Status: New
--
Plymouth doesn't show messages sent before the splash screen is visible
https://bugs.launchpad.net/bugs/507881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Could you give more details here.
Did the remount of / to rw actually *fail*?
--
rm: cannot remove `/var/lib/urandom/random-seed': Read-only file system
https://bugs.launchpad.net/bugs/567592
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: upstart (Ubuntu) = mysql-dfsg-5.1 (Ubuntu)
--
mysqld does not start reliably...
https://bugs.launchpad.net/bugs/566736
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs
Thanks, marking as solved.
Note that you can work around a broken system clock by:
cat EOF | sudo tee /etc/e2fsck.conf
[options]
broken_system_clock=true
EOF
** Changed in: mountall (Ubuntu)
Status: Incomplete = Fix Released
--
Filesystem check fails every boot
Right, that's my understanding as well
The design of rsyslog made it very hard to fall back to not de-rooting
in the case of an unpatched kernel
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
You received this bug notification because you are a member of Ubuntu
On Sun, 2010-04-18 at 21:17 +, Sensiva wrote:
I tried it, it gave me the choice to press S to skip mounting the shared
folder, or to press M to drop to recovery console
And did either of these options work?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[lucid] Adding vboxsf
** Changed in: upstart (Ubuntu)
Status: New = Invalid
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New = Triaged
** Changed in: upstart
Importance: Undecided = Wishlist
** Summary changed:
- When starting on rescue mode
** Package changed: mountall (Ubuntu) = plymouth (Ubuntu)
** Changed in: plymouth (Ubuntu)
Status: Incomplete = Triaged
** Summary changed:
- Lucid alpha 2 fails to start up unless you remove /proc/bus/usb from the fstab
+ Plymouth doesn't show messages sent before the splash screen is
udev can't race with the kernel ... all udev does is respond to messages
*from* the kernel - the lvm system should send change events if the
original events were invalid
(there are sporadic reports something has broken in recent kernels wrt
this, but reassigning to lvm since that's where the
This was caused by the use of Pre-Depends, which have been removed
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
Could not perform immediate configuration. In schroot.
https://bugs.launchpad.net/bugs/566194
You received this bug notification because you are a member of
On Wed, 2010-03-03 at 16:52 +, Steve Langasek wrote:
Well, don't do that.
You can't say that on bug reports ;-) Reddit get upset.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Remove plymouth destroying system
https://bugs.launchpad.net/bugs/531331
You received this bug
*explicitly* support people doing that.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
degraded NON-root raids never --run on boot
https://bugs.launchpad.net/bugs/259145
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Can you remove your fix and reboot, then run cat
/proc/self/mountinfo and attach that?
Thanks
** Changed in: mountall (Ubuntu)
Importance: Undecided = Medium
** Changed in: mountall (Ubuntu)
Status: New = Incomplete
--
/dev/shm isn't writable, causing problems with glibc 2.2+ apps
** Package changed: upstart (Ubuntu) = mysql-dfsg-5.1 (Ubuntu)
--
mysqld does not start reliably...
https://bugs.launchpad.net/bugs/566736
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This confirms that fsck is being run - and is not checking the
filesystem
** Package changed: mountall (Ubuntu) = e2fsprogs (Ubuntu)
** Changed in: e2fsprogs (Ubuntu)
Status: Incomplete = Triaged
** Summary changed:
- Not performing fsck on startup
+ e2fsck not checking filesystem
Argh, that's a shame!
If it does happen, please do reopen the bug and post that information!
Thanks for the report
** Changed in: mountall (Ubuntu)
Status: Incomplete = Invalid
--
/dev/shm isn't writable, causing problems with glibc 2.2+ apps such as chromium
Thanks for the report.
In this situation (an unknown mount in /etc/fstab), mountall should
display an error message on the Plymouth splash screen and prompt
allowing you to skip this fileystem or drop to a maintenance shell.
Apparently this isn't working for you.
I need some debugging
For the record, this is what you're *supposed* to see ;-)
** Attachment added: Screenshot of error screen
http://launchpadlibrarian.net/44707171/2010-04-18%2009.46.53.jpg
** Changed in: mountall (Ubuntu)
Importance: Medium = High
--
Lucid alpha 2 fails to start up unless you remove
Could you try the following?
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
sudo update-initramfs -u
** Changed in: mountall (Ubuntu)
Status: Confirmed = Incomplete
--
[lucid] Adding vboxsf in fstab stops boot process
https://bugs.launchpad.net/bugs/530179
You
Also does the following fix this:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
sudo update-initramfs -u
--
Lucid alpha 2 fails to start up unless you remove /proc/bus/usb from the fstab
https://bugs.launchpad.net/bugs/507881
You received this bug notification because you
% at the very least.
This will entirely depend on your display, since the resolution of VGA
is 640x480 on a 23 display the images will look large.
If we scaled them down as you suggest, on a 12 display they would look
tiny.
So they are what they are.
status wontfix
Scott
--
Scott James Remnant
on older kernels is *DELIBERATE*
and will not be fixed.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
() is always called in the main loop;
the signal handler is just there to break the loop and even the default
signal handler should do that
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Loops on mount failure when Plymouth not running
https://bugs.launchpad.net/bugs/553290
You received this bug
On Sat, 2010-04-17 at 06:57 +, Steve Langasek wrote:
Similar results again, mountall waits forever for /home even though it's
clearly available. New mountall debug log attached.
The log indicates that fsck is running? Is it?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Loops
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
301 - 400 of 6846 matches
Mail list logo
