Karmic Latest - upstart kept back - missing mountall

[David Favor]

Binary package hint: upstart

root@hive1:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  initscripts upstart
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

root@hive1:~# apt-get install upstart
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  upstart: PreDepends: mountall but it is not installable
E: Broken packages

root@hive1:~# apt-get install mountall
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package mountall is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package mountall has no installation candidate

[Kevin Fries (kevin-kevinfries)]

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

[MADevil (madevil)]

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 installed, 0 to remove and 2 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done

 aptitude install initscripts
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following packages are BROKEN:
  initscripts upstart
2 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 615kB of archives. After unpacking 16.4kB will be used.
The following packages have unmet dependencies:
  upstart: PreDepends: mountall which is a virtual package.
  initscripts: Breaks: rsyslog (< 4.2.0-2ubuntu3~boot1) but 4.2.0-2ubuntu2 is installed.
               Breaks: udev (< 146-2~boot6) but 146-1 is installed.
open: 2; closed: 61; defer: 88; conflict: 24 oUnable to resolve dependencies! Giving up...
The following packages are BROKEN:
  initscripts upstart
2 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 615kB of archives. After unpacking 16.4kB will be used.
aptitude failed to find a solution to these dependencies. You can solve them yourself by hand or type 'n' to quit.
The following packages have unmet dependencies:
  upstart: PreDepends: mountall which is a virtual package.
  initscripts: Breaks: rsyslog (< 4.2.0-2ubuntu3~boot1) but 4.2.0-2ubuntu2 is installed.
               Breaks: udev (< 146-2~boot6) but 146-1 is installed.
Resolve these dependencies by hand? [N/+/-/_/:/?]

aptitude install upstart
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following packages are BROKEN:
  upstart
1 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 542kB of archives. After unpacking 111kB will be used.
The following packages have unmet dependencies:
  upstart: PreDepends: mountall which is a virtual package.
Unable to resolve dependencies! Giving up...
The following packages are BROKEN:
  upstart
1 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 542kB of archives. After unpacking 111kB will be used.
aptitude failed to find a solution to these dependencies. You can solve them yourself by hand or type 'n' to quit.
The following packages have unmet dependencies:
  upstart: PreDepends: mountall which is a virtual package.
Resolve these dependencies by hand? [N/+/-/_/:/?]

And don't know if it's related to these errors , but after reboot , on X launching , HAL don't detect my USB Keyboard (e...

[Bruno Gomes (blfgomes)]

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 a matter of time before the package appears again in Karmic.

[Scott James Remnant (Canonical) (canonical-scott)]

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.

[Tiago Hillebrandt (tiagohillebrandt)]

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 pode significar que
você solicitou uma situação impossível ou, se você está usando a
distribuição instável, que alguns pacotes requeridos não foram
criados ainda ou foram retirados da "Incoming".
A informação a seguir pode ajudar a resolver a situação:

The following packages have unmet dependencies:
  upstart: PreDepends: mountall which is a virtual package.
E: Pacotes quebrados
-----------------------------------------------
$ sudo invoke-rc.d gdm start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service gdm start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start gdm
start: Não foi possível conectar ao Upstart: Failed to connect to socket /com/ubuntu/upstart: Conexão recusada
invoke-rc.d: initscript gdm, action "start" failed

[Bruno Gomes (blfgomes)]

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.

[surlyjake (surlyjake-deactivatedaccount)]

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.

[Tiago Hillebrandt (tiagohillebrandt)]

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.

[MarlonChalegre (marlonchalegre)]

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.

[Tiago Hillebrandt (tiagohillebrandt)]

MarlonChalegre, I setted your report as duplicate of this, ok?

[MarlonChalegre (marlonchalegre)]

Okay dude.

[Bruno Gomes (blfgomes)]

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. Reinstall using the .deb and hit Ctrl+D to proceed with the boot. You won't get gdm, but you will have a functional prompt with network. Wait a few hours and then try to upgrade again. Don't reboot or you will have to go through the same procedure again.

[MarlonChalegre (marlonchalegre)]

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.

[Bruno Gomes (blfgomes)]

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 everything will work fine if we try to upgrade tomorrow.

[MarlonChalegre (marlonchalegre)]

Bruno Gomes, Do you think that solution will come just tomorrow? maybe today, no? Or no chance?

[MADevil (madevil)]

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 /mnt/tmp/proc/bus/usb
mount -o bind /sys /mnt/tmp/sys
chroot /mnt/tmp

now you can launch sshd or directly

aptitude update
aptitude safe-upgrade

and reboot

[MarlonChalegre (marlonchalegre)]

The solution was released.
 apt-get update
apt-get upgrade

[MarlonChalegre (marlonchalegre)]

but no hostname :(

[starslights (starslights)]

it seem same for me, it can't resolve and update anymore ..

[meh (meh-deactivatedaccount)]

works now, thanks.
the dependencies mountall, hostname and rsyslog are now available.

[MarlonChalegre (marlonchalegre)]

How can I install that without internet?

[Daniel Holbert (dholbert)]

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.

[MarlonChalegre (marlonchalegre)]

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

[MarlonChalegre (marlonchalegre)]

Daniel Holbert way is better then my!!

[MarlonChalegre (marlonchalegre)]

Now, the NetworkManager is not running...

[Daniel Holbert (dholbert)]

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 persists after rebooting, I'd say it's unconnected to the original bug here. :)

[pablomme (pablomme)]

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 Ctrl-Alt-Delete

Now, I also get the NetworkManager problem (solved simply by running "sudo NetworkManager") after reboot. It'd be useful if whoever reports it posted a link here.

[MarlonChalegre (marlonchalegre)]

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 NetworkManager is not running.

I posted the bug here https://bugs.launchpad.net/ubuntu/+bug/430366

[Ryan (ubuntu-draziw)]

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 on their toes about promising Alpha having major breakage. ;) I think this one took the cake - eg grub-pc didn't go on upgrades due to the risk in leaving people with a system taking real manual recovery - and that's what happened for this roll out - so a bit inconsistent on the policy from my seats in the bleachers...

[Robbie Williamson (robbiew)]

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 started on how to possibly alert testers via update-manager when we know an update will break systems.

[MarlonChalegre (marlonchalegre)]

The bug was resolved.

[Hilario J. Montoliu (hjmf) (hmontoliu)]

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 didn't work for me.

[Hilario J. Montoliu (hjmf) (hmontoliu)]

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

[starslights (starslights)]

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

[pablomme (pablomme)]

@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 in alpha releases. Which
is a good thing, I suppose.

> With that said, a discussion has started on how to possibly alert testers via update-manager
> when we know an update will break systems.

Was it known that these packages were broken prior to uploading? I don't see the benefit
in uploading them in those circumstances, even in a pre-release distribution... Or are you
talking about a system to alert people about breakage once it's been reported?

[mabawsa (mabawsa)]

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.

[Lou Ruppert (louferd)]

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 available all morning, but the problem still persists.

[Colin Watson (cjwatson)]

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.

[Lou Ruppert (louferd)]

OK, I just reported it as 430667

[Alessandro Ghersi (alessandro-ghersi)]

There is an open udev bug also here #430654

[Christopher (soft-kristal)]

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.

[Scott James Remnant (Canonical) (canonical-scott)]

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

[Scott James Remnant (Canonical) (canonical-scott)]

 tag ubuntu-boot
--
Scott James Remnant
<email address hidden>

[Luke (lukekuhn)]

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 on it and can handle the LUKS partition that is my home partitiojn.

2: Before upgrading to an alpha, I made a dd copy of /dev/sda1, my operating system partition, put the image in my home directory, set it up on /dev/loop0, and checked it with fsck.

3: I then upgraded the laptop to Karmic and saved the packages. That day's upgrade worked. My first Jaunty Upgrade(in Alpha 4) did not, so I dd'd the old OS image back onto sda1 until Alpha 5 was out that time around. When the laptop worked this time around, I transferred the packages to the offline desktop and used dpkg -i force-all * to put them in, also giving dpkg the option to tolerate 1,000 errors instead of just 50. It worked again.

4: Next, I made another dd copy of /dev/sda1 (you can do this while booted on it, it need not be quiescent), checked it, made a tarball of the last one, and deleted the previous original image.

5: When that buggy mountall/upstart combo broke things, I tried reinstalling old packages, no dice. Instead, I booted from the flash drive, mounted the home partition on /media/HDsecurity, and used dd to putn my last good setup (the Sep 11 one) back on /dev/sda1. I then rebooted, took those saved packages, upgraded to just before the trouble, and saved another dd copy, deleting the previous one.

When I hear mountall works, I will first make a fresh OS copy, then install it and see.

Alphas break-nautilus quit in Hardy Alpha 4, a libc6 upgrade broke Gutsy, nvidia didn't work in early Jaunty, you name it! That's how the bufgs are found so they can be squashed.

When you use alphas, you must understand your system and budget time for repairs. You wil learn much-and soon be able to fix the shit that breaks because of your own mistakes.