How to safely follow an Alpha release.
I do, in fact, use Karmic on two media production machines-but I can
recover a dead OS in 30 minutes tops.
Here's how:
1: some time ago, I prepared a bootable flash drive with Ubuntu on it. Any
version will do, so long as
(in my case) it has cryptsetup
For me it isn't resolved yet.
I'm still stuck at boot (the boot stops after init-bottom however you
can reboot with ctrl-alt-supr) after applying all the upgrades (from
init=/bin/bash) that are available at this time from archives.ubuntu.com
The workaround of removing and reinstalling mountall
Btw I've posted in this thread as
https://bugs.edge.launchpad.net/bugs/430272 seems to been marked as a
dup of this one
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks Pablomme,
Now it can resolve name again and update.
It start but make some message when it boot, unknow symlink and a few
others but with the 4 cores are too quick ,to can see more infos.
Thanks very much for help
my best
--
Karmic Latest - upstart kept back - missing mountall
@Robbie Williamson:
I'd also like remind people that, Pre-releases of Karmic are *not*
encouraged for anyone
needing a stable system or anyone who is not comfortable running into
occasional, even
frequent breakage.
Well, we are spoilt by the fact that it's usually minor things that break
Had the same issues last night, puterfreeze!
This mornings updates done through aptitude and the emergency console got the
system booting again.
It does seem rather undtable and I had my first Kernel Panic in about 1 year.
I have the udevd symlink issues as well.
--
Karmic Latest - upstart kept
Had the same problems as Hilario reported on 430272. System boot hangs
after udevd reports errors on SYMLINK and ppc. My system is a PXE boot,
so I was able to apply updates after the initial mountall problem by
chrooting into the diskless root directory. I've been applying them as
they become
The specific reported problem of mountall not being available is now
fixed. I recommend that people with other problems report them as
separate bugs, otherwise it'll be impossible for us to keep track.
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
OK, I just reported it as 430667
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
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
There is an open udev bug also here #430654
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm up and running again - applied all the updates and then used the
'Repair broken packages' option.
No splash, but quick enough.
FYI - I enjoy testing Alphas, but on a partition with no important
files. I suggest others treat it the same way.
--
Karmic Latest - upstart kept back - missing
mountall has been published, and thus the packages should be installable
(which is the subject of this bug)
If you are still having boot issues with the init transition, then
please file new bugs so we can triage your problems independently
** Changed in: upstart (Ubuntu)
Status:
I have the same issue, but mine is also effecting sysv-rc. Otherwise, I
am seeing the exact same issue as above
The following packages have unmet dependencies:
sysv-rc: Breaks: initscripts ( 2.86.ds1-63) but 2.86.ds1-61ubuntu16 is to be
--
Karmic Latest - upstart kept back - missing mountall
Same issue here :
aptitude safe-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following packages have been kept back:
initscripts upstart
0 packages upgraded, 0 newly
I looked a few minutes ago and it seemed like the mountall package had
not been built successfully for any architecture (it said there was a
chroot problem). I looked again now and the problem has been corrected.
https://launchpad.net/ubuntu/+source/mountall/0.1.3/+build/1244254
Maybe it is just
Thanks the report, however this isn't a bug at the source package level
but merely a transitional artefact at the point you upgraded. It'll
sort itself out automatically over the next few hours.
** Changed in: upstart (Ubuntu)
Status: New = Invalid
--
Karmic Latest - upstart kept back -
** Changed in: upstart (Ubuntu)
Status: Invalid = Confirmed
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
gdm doesn't start after this last update. Now I am using a live cd to report
this bug.
-
# apt-get install initscripts upstart -y
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
Alguns pacotes não puderam ser instalados. Isto
Tiago, gdm doesn't start for me either. But like Scott said, just run
apt-get update in a few hours to see the missing package and solve this
dependency issue.
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification
I have the same problem, my system don't start anymore. I reported a bug
in https://bugs.launchpad.net/bugs/430263 but i think is the same bug.
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a
MarlonChalegre, I setted your report as duplicate of this, ok?
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
MarlonChalegre and surlyjake, here is a workaround... Add the init=/bin/bash to
your boot options in grub. Remount the filesystem RW and remove the mountall
package with:
# dpkg -r --force-depends mountall
Now, reboot. It will drop you to a prompt saying that mountall couldn't
be found.
Okay dude.
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
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
I installed the mountall deb package from
https://launchpad.net/ubuntu/+source/mountall/0.1.3/+build/1244254
manually... now i cant boot the system into any of the installed
kernels, not even in single user mode.
--
Karmic Latest - upstart kept back - missing mountall
I have accessed the prompt with terminal using the boot recovery mode. I
choose an option that allow you to use the prompt with network in root
mode.
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are
I think the problem here is that the latest version of initscripts
(https://launchpad.net/ubuntu/karmic/i386/initscripts/2.87dsf-4ubuntu3) breaks
udev ( 146-2~boot6), but udev 147~-1 wasn't released until a few minutes ago
(https://launchpad.net/ubuntu/karmic/i386/udev/147~-1).
I think
Bruno Gomes, Do you think that solution will come just tomorrow? maybe
today, no? Or no chance?
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
A suggestion: not is a good idea install the mountall package manually
(https://launchpad.net/ubuntu/+source/mountall/0.1.3/+build/1244254) to
after install upstart and initscripts, hehe. When I try to make this,
the aptitude wants to remove many essentials packages.
--
Karmic Latest - upstart
Boot from live cd/usb Kubuntu
open konsole :
sudo su -
mkdir /mnt/tmp
mount /dev/sd(your / partition) /mnt/tmp
mount -o bind /dev /mnt/tmp/dev
mount -o bind /dev/pts /mnt/tmp/dev/pts
mount -o bind /dev/shm /mnt/tmp/dev/shm
mount -o bind /proc /mnt/tmp/proc
mount -o bind /proc/bus/usb
The solution was released.
apt-get update
apt-get upgrade
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
but no hostname :(
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
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
it seem same for me, it can't resolve and update anymore ..
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
A quick summary of how to fix this:
- Boot
- When booting stops at a black screen with a blinking cursor, press
Ctrl-Alt-F2 and log in
- Type (assuming a wired connection on eth0):
sudo dhclient eth0
sudo apt-get update
sudo apt-get install mountall
sudo apt-get upgrade
- Press
NetworkManager (aka nm-applet) is running just fine for me, but I've
rebooted since my dhclient invocation -- if you haven't, it's possible
that NetworkManager got confused because you'd already configured your
network since bootup. Try rebooting?
In any case, if your NetworkManager problem
Now, the NetworkManager is not running...
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Daniel Holbert way is better then my!!
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Answering me:
Download from a computer with internet :) from here
https://launchpad.net/ubuntu/karmic/amd64/hostname/2.95ubuntu1 or
https://launchpad.net/ubuntu/karmic/i386/hostname/2.95ubuntu1 and
install it :D
--
Karmic Latest - upstart kept back - missing mountall
If you have a root shell, you should be able to auto-configure your network
connection by running:
dhclient eth0
(where eth0 would be the name of your network interface, as reported by
ifconfig)
This worked for me earlier today, when I only had a shell with no
networking.
--
Karmic Latest
How can I install that without internet?
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
works now, thanks.
the dependencies mountall, hostname and rsyslog are now available.
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
It's a new bug now!! hehehe
I restarted the system and the network manager continue not running! I have to
use dhcpclient to connect.
I tried to reinstall the package and the network manager started, but when i
restart the system the networkmanager don't start and the applet continue
saying
Sigh.
https://bugs.edge.launchpad.net/ubuntu/+source/debhelper/+bug/427356
hurt. i manually put in mountall (thanks for the link surlyjake) and as
~20 minutes ago - looks like all the rest of the packages needed to
'recover' are up now. Can now boot again - yey. I think this was to
keep people
This should be resolved with from the latest updates in the archive.
I'd also like remind people that, Pre-releases of Karmic are *not*
encouraged for anyone needing a stable system or anyone who is not
comfortable running into occasional, even frequent breakage. With that
said, a discussion has
The bug was resolved.
--
Karmic Latest - upstart kept back - missing mountall
https://bugs.launchpad.net/bugs/430125
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
44 matches
Mail list logo
