Upgrade raring to saucy #428

schnie opened this Issue Oct 17, 2013 · 25 comments


None yet

9 participants

schnie commented Oct 17, 2013

Now that 13.10 is officially out, what is the best way (if any) to upgrade a chroot from 13.04? The software updater is showing the upgrade as available, but I'm hesitant to let it upgrade. Is there a better way to do this? Any advice would be appreciated!


I can't say for sure what will work the best, but I'd try one of two things:

Plan A (might result in a larger chroot and some unwanted packages):

  1. Back up your chroot using sudo edit-chroot -b chrootname. This backup is an exact copy of your chroot, so if things go wrong you can restore it without losing anything.
  2. Run the Ubuntu upgrader.
  3. Update your chroot using the latest crouton -u to make sure all of the crouton-related scripts are still in place.

Plan B (might not install essential packages, remove obsolete ones, or migrate some data):

  1. Back up your chroot a la plan A.
  2. Update the chroot using the latest crouton but with two -u's and the new release specified, i.e., crouton -uu -r saucy -n chrootname. This will update apt-get's sources.list to point to saucy and upgrade all packages.

Either way, when you're done and everything's working, feel free to rename the chroot (edit-chroot -m) to match the new release name, so that it's less confusing.


I have tried to update raring to saucy on my Acer C7 Chromebook.
Won't work.

I now use Ubuntu 12.04 LTS insted.


What about it doesn't work? What method did you use?


I just runt upgrade the system with the GUI-metod. I don't remeber what the GUI software name, but i remeber that the program asked me to remove something from X and replace it with other thing.

I think i will try to update my 12.04 to 12.10 to 13.04 to 13.10 and come back with results.


Did you update the chroot using crouton after you upgraded it?
Also, don't start from 12.04 if you're just going to upgrade; install the proper release with -r.


I tried to update from 12.04 LTS to 12.10. It works OK!
I tried to update from 12.10 to 13.04. It works OK! But it asking if you want to remove upstart-xseasion. Just keep that.

Updating from 13.04 to 13.10 gave me this error message:

"Welcome to crosh, the ChromeOS developer shell.
If you got here by mistake, don't panic! Just close this tab and carry on.
Type 'help' for a list of commands.
crosh> shell
chronos@localhost / $ sudo startunity
Entering /usr/local/chroots/precise...
X.Org X Server 1.14.3
Release Date: 2013-09-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-37-generic i686 Ubuntu
Current Operating System: Linux localhost 3.4.0 #1 SMP Thu Sep 12 16:21:05 PDT 2013 i686
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-1 roo
twait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="2 vboot none ro 1,0 2129920 bootcache
8f0592c2-8bc8-384a-8153-0473fac22097+1 2129920 bca73df932908d5163132e14db1cb8305ca29758 512 20000 100000, vroot none ro
1,0 2097152 verity payload=254:0 hashtree=254:0 hashstart=2097152 alg=sha1 root_hexdigest=a6b66bad5a622a3038b7da16656de
c7d99ad9ad0 salt=0e0679e91e30fdcd79b416411730db9f2cfeb08e9db40f2abd4a0e8fd4cab96b" noinitrd vt.global_cursor_default=0 k
ern_guid=8f0592c2-8bc8-384a-8153-0473fac22097 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 t
pm_tis.interrupts=0 nmi_watchdog=panic,lapic
Build Date: 15 October 2013 09:23:29AM
xorg-server 2:1.14.3-3ubuntu2 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Wed Oct 23 12:06:07 2013
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
setversion 1.4 failed
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
setversion 1.4 failed
The XKEYBOARD keymap compiler (xkbcomp) reports:

Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols
Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(II) AIGLX: Suspending AIGLX clients for VT switch"

And inside the Ubuntu i got this message:

And some GLX problems.


If i update with sudo sh -e ~/Downloads/crouton -u -n precise i got this message:

"The following packages have unmet dependencies:
libsbc-dev : Depends: libsbc1 (= 1.1-1) but 1.1-2 is to be installed
E: Unable to correct problems, you have held broken packages.
Failed to complete chroot setup.
Unmounting /usr/local/chroots/precise..."


I only did this to help you. My ubuntu is brokend now beacuse of this updates.
Im going back the 12.04 LTS insted. Its safe and perfekt for the chrommebok Acer C7! :)


The libsbc-dev problem is due to the following:

  • On quantal and previous releases, install_mirror_package installs the latest version of libsbc1 that it can find on the mirror. That is 1.1-2, provided by Ubuntu Trusty (14.04).
  • raring only uses 1.0-2
  • saucy only uses 1.1-1 (hence the failure)

This could be fixed by matching 1.0-2 only in install_mirror_package, or forcing a downgrade.

Probably affects other usage of install_mirror_package as well (touch, xephyr).


What if we add a call to sudo apt-get install -y -f in core?


Nope (this is on a broken quantal->raring->saucy upgrade).

(quantal)nicolas@localhost:~$ sudo apt-get install -y -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

This also doesn't work:

(quantal)nicolas@localhost:~$ sudo apt-get install -f libsbc1 libsbc-dev
Reading package lists... Done
Building dependency tree       
Reading state information... Done
libsbc1 is already the newest version.
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:
 libsbc-dev : Depends: libsbc1 (= 1.1-1) but 1.1-2 is to be installed
E: Unable to correct problems, you have held broken packages.

So this will probably be fixed by 1) changing the install_mirror_package regex to only install 1.0.*, and 2) suggesting that you do a crouton update both before and after an Ubuntu upgrade.


Well, xephyr is also broken. For some reason the apt-preference pinning is not working as it should (I have no idea why), and xserver-xephyr never gets updated after quantal (it stays at 2:1.11.4-0ubuntu10.14).

I tried a number of different combinations in that file, but I found nothing that allows updating on releases after quantal (when I look at apt-cache policy xserver-xephyr it seems all versions are affected by the pinning)...

I guess the easiest option would be to remove /etc/apt/preferences.d/xserver-xephyr on each update...


Can't you hackers just create a BIOS or something so it will be possible to install linux by USB. :)
Install ubuntu and drive it via chroot seems to bee a little bit buggy.

ChromeOS will be a good OS if it will be possible to compile own source like codeblocks or Arduino IDE.
Or install java. I know why i can't install java. I cannot create a folder in /etc beacuse the disk is write protected.


Those options are already available. Search the web for "Chrubuntu" or "Chromebook SeaBios". If you just want ChromeOS with compilation capabilities, that's a perfectly good use of crouton; you don't have to run a full-fledged desktop environment.

New distro releases will always be buggy at first, but the bugs will get squashed. You can either continue to contribute and help resolve the issues on the bugtracker, or you can use something not quite so bleeding-edge like raring, which works great.


Crouton is the best choise beacuse it's more updated and have great support. I stay with crouton and helping you to find bugs.

I have tested raring and it works great. But i think precise is more a perfect distro for Acer C7. It should be the default distro from crouton. It has long update time to April 2017, and going to Ubuntu 14.04 will only give a slower laptop(Acer C7) due to the hardware system req of 14.04 and future.
In April 2017, Google certainly will no longer dropping support for chrome book of this version, and also the Acer C7 would simply be too outdated.

But Google should make it possible for chromebook user to compile own source code and not be locked to cheap apps, that you only can run in the webbrowser.


With the latest crouton, upgrading should work via the following steps:

  1. Upgrade via Ubuntu's update manager.
  2. Download the latest crouton and update the chroot with -u.
@dnschneid dnschneid closed this Nov 1, 2013

A worked example so I don’t forget for the next time

  1. Backup chroot - after logging out of raring:
    chronos@localhost:~$ sudo edit-chroot -b raring
  2. Upgrade to new Distribution Release:
    me@localhost:~$ sudo do-release-upgrade
  3. Update your chroot using the latest crouton -u to make sure all of the crouton-related scripts are still in place.
    me@localhost:~$ croutonversion -u -d -c
  4. chronos@localhost:~$ sudo sh -e ~/Downloads/crouton -t xfce -t chrome -n raring -u
  5. Rename the chroot (edit-chroot -m) to match the new release name:
    chronos@localhost:~$ sudo edit-chroot -m saucy raring

Works a treat just need to run synaptic or software-center as root or I get errors:
gksudo synaptic-pkexec

PolicyKit error when trying to install/remove programs in the software center



reeved commented Apr 21, 2014

hey @SilverWave, did your policykit problem get fixed or did you still have to run them as root?


Hi reeved I still have to run them as root.

coreyp commented May 2, 2014

My chroot is installed on an SD card. I'm trying to upgrade saucy to trusty (xfce). When I try to upgrade via Plan B, above (and described in #119 ), I get an error:

/usr/local/chroots/saucy does not exist; cannot update.

When I try to point the -n flag to the actual location of the chroot, ie

sudo sh -e ~/Downloads/crouton -uu -r trusty -n /media/removable/SD\ Card/chroots/saucy

I get a different error:

Invalid chroot name '/media/removable/SD Card/chroots/saucy'.

Ideas? In the meantime, I'll try Plan A.


See the wiki for upgrading.
You would specify the chroot with -p /media/removable/SD\ Card/ -n saucy


I upgraded from Saucy (Unity) to Trusty (Unity) using the instructions in the upgrade wiki. Everything went perfectly. The only problem is I don't have any of the icons on the right hand side of the top panel giving the power/shutdown/logout button, the time/calendar, the Internet connection indicator, battery indicator, etc. Is there a way to restore these to the panel, or to upgrade the panel?

Thanks for your help.


Where is this ubuntu upgrader? Is it a command line tool? Do I have to download it? Which distro is it in, or is it in all of them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment