[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: ubuntu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/545536
Title:
Not able
http://ubuntuforums.org/showpost.php?p=9094227&postcount=11
After adding nomodeset to /etc/default/grub and running update-grub is
the problem fixed after finding the machine booted successfully if I
unplugged the HDMI cable. Still funny how it worked with modesetting
after I kill those 2 processe
I've just encountered this problem also. Luckily I can still SSH in to my
machine and browse all my mounts.
The following works for me
1. SSH in to machine
2. Kill both Plymouthd and upstart-udev-bridge
3. Alt-Ctl-Del to reboot
Upon reboot you should boot up successfully however it should need t
I would like to add that this problem may occur if the system fails to
mount a partition that is in fstab. Due to an apparent bug in upstart
the mount problem handling does only kick in every n-th boot, and n may
be >10 if you are out of luck. Otherwise only the above mentioned
ureadahed error mes
Jaromir,
In most times you don't have to reinstall the whole system.
Try to boot from Ubuntu LiveCD, then open your root partition in the file
manager (Places - Computer), then 'etc' folder, then edit 'fstab' file there.
Comment out lines referring to /proc/bus/usb and your FireWire drive (by
i
I didn't get any further .. I probably will reinstall the whole system
after, the final version is out, or wait for new pc with next ubuntu.
--
Not able to boot
https://bugs.launchpad.net/bugs/545536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Confirmed. I had this same issue. Ctrl alt del gave it the kick that it
needed to complete boot.
--
Not able to boot
https://bugs.launchpad.net/bugs/545536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I tried today to get the log, but with little success.
I am not able to get to the terminal session - the system is stuck with the
message about "... status 4".
I tried all possible combinations of keyboard shortcuts like ctrl c, ctrl
break, c-esc, esc, ctrl backspace ... and it just writes the c
I figured out my issue: I wasn't using the current kernel. When I
updated my kernel I choose to "keep my old menu.lst". This was the
source of many problems. I upgraded to Grub2, which automatically
grabbed my latest kernel, and my system seems to be working great now.
I was using 2.6.24, and no
Hello,
I will try the commands //I'm in win now// later.
I was trying some steps in the morning - was able to upgrade new packages,
which didn't help, but in recovery mode on the current kernel, I left the pc
running for a long time and a screen came through with the message same as
before with
I thought I had solved; however, today it represented in the form of forcing
me to Ctrl+Alt+Del it 5 or 6 times before having my system booted.
It always sticks at Waiting for /home [SM]
I'm updating now, and plymouth is one of the provided updates, so it _may_
be fixed now, but I don't really know
Claudio Moretti, even if the original poster doesn't have encrypted
volumes, I have encrypted volumes and am having this errror... what is
the solution that you found? Thanks.
--
Not able to boot
https://bugs.launchpad.net/bugs/545536
You received this bug notification because you are a member o
This leads me to a question: do you use encrypted volumes?
I had the same problem (even if it's now solved)
--
Not able to boot
https://bugs.launchpad.net/bugs/545536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
The ureadahead message is not relevant to your problems
** Summary changed:
- Not able to boot - ureadahead other main process terminated with status 4
+ Not able to boot
** Package changed: ureadahead (Ubuntu) => ubuntu
--
Not able to boot
https://bugs.launchpad.net/bugs/545536
You received t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 545536
This will help us to find and resolve the problem. Bear in mind that you
may need t
** Package changed: ubuntu => ureadahead (Ubuntu)
--
Not able to boot - ureadahead other main process terminated with status 4
https://bugs.launchpad.net/bugs/545536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I am not particulary strong with terminal, but If you tell me what I should do,
I could try some steps to get around this, or get some logs.
I have 2 internal driver + 1 external - Western Digital My Book.
--
Not able to boot - ureadahead other main process terminated with status 4
https://bugs.
17 matches
Mail list logo
