Hi
Upgrade to 14.04 from 13.10 Sorry application stopped unexpepectedly
How do I release the upgrade and install
other softwear download in synaptic no problem but not upgrade 14.04
A new version of Kubuntu is available on task bar
Click on
NO download
Still searching to upgread to 14.04

OK. Exactly what application stopped unexpectedly? Was this Update Mangler?

If you were in the middle of a version upgrade you are going to be having some problems for sure.

Try running;
This will probably take several tries. At the end it will list the packages that it failed with. Read them and count them.

Then re run the command. Will hopefully pick up some more. Do this rinse and repeat until the list of failed packages stays the same.

Boot to recovery and get the pleasure of a root prompt with no authentication required. Run the command from there. This will be running without any extra resources being used and will be running as actual root. This will, many times, pick up more packages.

When that finally has a repeating list of failed packages run, still at the root prompt in recovery mode;
No matter what the results of that is, success, partial success or complete failure, run;
apt-get upgrade
[/code]
If this runs without error you may have a system.

If any packages are listed as held back run;
If you are still getting errors post them completely.

Hi Widget
Update manager is OK
ma@ma:~$ sudo apt-get dist-upgrade
[sudo] password for ma:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
ma@ma:~$

ma@ma:~$ sudo apt-get update
[sudo] password for ma:
Ign http://nz.archive.ubuntu.com saucy InRelease
Ign http://security.ubuntu.com saucy-security InRelease
Ign http://nz.archive.ubuntu.com saucy-updates InRelease
Ign http://archive.canonical.com saucy InRelease
Ign http://extras.ubuntu.com saucy InRelease
Ign http://nz.archive.ubuntu.com saucy-backports InRelease
Get:1 http://security.ubuntu.com saucy-security Release.gpg [933 B]
Hit http://extras.ubuntu.com saucy Release.gpg
Hit http://archive.canonical.com saucy Release.gpg
Hit http://nz.archive.ubuntu.com saucy Release.gpg
Get:2 http://security.ubuntu.com saucy-security Release [49.6 kB]
Hit http://extras.ubuntu.com saucy Release
Hit http://archive.canonical.com saucy Release
Hit http://nz.archive.ubuntu.com saucy-updates Release.gpg
Hit http://extras.ubuntu.com saucy/main Sources
Hit http://archive.canonical.com saucy/partner amd64 Packages
Get:3 http://security.ubuntu.com saucy-security/main Sources [43.6 kB]
Hit http://nz.archive.ubuntu.com saucy-backports Release.gpg
Hit http://nz.archive.ubuntu.com saucy Release
Hit http://extras.ubuntu.com saucy/main amd64 Packages
Hit http://archive.canonical.com saucy/partner i386 Packages
Get:4 http://security.ubuntu.com saucy-security/restricted Sources [14 B]
Hit http://nz.archive.ubuntu.com saucy-updates Release
Get:5 http://security.ubuntu.com saucy-security/universe Sources [8,836 B]
Hit http://extras.ubuntu.com saucy/main i386 Packages
Hit http://nz.archive.ubuntu.com saucy-backports Release
Get:6 http://security.ubuntu.com saucy-security/multiverse Sources [1,827 B]
Get:7 http://security.ubuntu.com saucy-security/main amd64 Packages [115 kB]
Hit http://nz.archive.ubuntu.com saucy/main Sources
Hit http://nz.archive.ubuntu.com saucy/restricted Sources
Get:8 http://security.ubuntu.com saucy-security/restricted amd64 Packages [14 B]
Get:9 http://security.ubuntu.com saucy-security/universe amd64 Packages [38.5 kB]
Hit http://nz.archive.ubuntu.com saucy/universe Sources
Get:10 http://security.ubuntu.com saucy-security/multiverse amd64 Packages [3,437 B]
Hit http://nz.archive.ubuntu.com saucy/multiverse Sources
Get:11 http://security.ubuntu.com saucy-security/main i386 Packages [114 kB]
Hit http://nz.archive.ubuntu.com saucy/main amd64 Packages
Get:12 http://security.ubuntu.com saucy-security/restricted i386 Packages [14 B]
Ign http://archive.canonical.com saucy/partner Translation-en_NZ
Hit http://nz.archive.ubuntu.com saucy/restricted amd64 Packages
Get:13 http://security.ubuntu.com saucy-security/universe i386 Packages [38.8 kB]
Ign http://archive.canonical.com saucy/partner Translation-en
Hit http://nz.archive.ubuntu.com saucy/universe amd64 Packages
Get:14 http://security.ubuntu.com saucy-security/multiverse i386 Packages [3,634 B]
Ign http://extras.ubuntu.com saucy/main Translation-en_NZ
Hit http://nz.archive.ubuntu.com saucy/multiverse amd64 Packages
Ign http://extras.ubuntu.com saucy/main Translation-en
Hit http://nz.archive.ubuntu.com saucy/main i386 Packages
Hit http://security.ubuntu.com saucy-security/main Translation-en
Hit http://nz.archive.ubuntu.com saucy/restricted i386 Packages
Hit http://nz.archive.ubuntu.com saucy/universe i386 Packages
Hit http://security.ubuntu.com saucy-security/multiverse Translation-en
Hit http://nz.archive.ubuntu.com saucy/multiverse i386 Packages
Hit http://security.ubuntu.com saucy-security/restricted Translation-en
Hit http://nz.archive.ubuntu.com saucy/main Translation-en
Hit http://nz.archive.ubuntu.com saucy/multiverse Translation-en
Hit http://security.ubuntu.com saucy-security/universe Translation-en
Hit http://nz.archive.ubuntu.com saucy/restricted Translation-en
Hit http://nz.archive.ubuntu.com saucy/universe Translation-en
Hit http://nz.archive.ubuntu.com saucy-updates/main Sources
Hit http://nz.archive.ubuntu.com saucy-updates/restricted Sources
Hit http://nz.archive.ubuntu.com saucy-updates/universe Sources
Hit http://nz.archive.ubuntu.com saucy-updates/multiverse Sources
Hit http://nz.archive.ubuntu.com saucy-updates/main amd64 Packages
Hit http://nz.archive.ubuntu.com saucy-updates/restricted amd64 Packages
Hit http://nz.archive.ubuntu.com saucy-updates/universe amd64 Packages
Ign http://security.ubuntu.com saucy-security/main Translation-en_NZ
Hit http://nz.archive.ubuntu.com saucy-updates/multiverse amd64 Packages
Ign http://security.ubuntu.com saucy-security/multiverse Translation-en_NZ
Hit http://nz.archive.ubuntu.com saucy-updates/main i386 Packages
Ign http://security.ubuntu.com saucy-security/restricted Translation-en_NZ
Ign http://security.ubuntu.com saucy-security/universe Translation-en_NZ
Hit http://nz.archive.ubuntu.com saucy-updates/restricted i386 Packages
Hit http://nz.archive.ubuntu.com saucy-updates/universe i386 Packages
Hit http://nz.archive.ubuntu.com saucy-updates/multiverse i386 Packages
Hit http://nz.archive.ubuntu.com saucy-updates/main Translation-en
Hit http://nz.archive.ubuntu.com saucy-updates/multiverse Translation-en
Hit http://nz.archive.ubuntu.com saucy-updates/restricted Translation-en
Hit http://nz.archive.ubuntu.com saucy-updates/universe Translation-en
Hit http://nz.archive.ubuntu.com saucy-backports/main Sources
Hit http://nz.archive.ubuntu.com saucy-backports/restricted Sources
Hit http://nz.archive.ubuntu.com saucy-backports/universe Sources
Hit http://nz.archive.ubuntu.com saucy-backports/multiverse Sources
Hit http://nz.archive.ubuntu.com saucy-backports/main amd64 Packages
Hit http://nz.archive.ubuntu.com saucy-backports/restricted amd64 Packages
Hit http://nz.archive.ubuntu.com saucy-backports/universe amd64 Packages
Hit http://nz.archive.ubuntu.com saucy-backports/multiverse amd64 Packages
Hit http://nz.archive.ubuntu.com saucy-backports/main i386 Packages
Hit http://nz.archive.ubuntu.com saucy-backports/restricted i386 Packages
Hit http://nz.archive.ubuntu.com saucy-backports/universe i386 Packages
Hit http://nz.archive.ubuntu.com saucy-backports/multiverse i386 Packages
Hit http://nz.archive.ubuntu.com saucy-backports/main Translation-en
Hit http://nz.archive.ubuntu.com saucy-backports/multiverse Translation-en
Hit http://nz.archive.ubuntu.com saucy-backports/restricted Translation-en
Hit http://nz.archive.ubuntu.com saucy-backports/universe Translation-en
Ign http://nz.archive.ubuntu.com saucy/main Translation-en_NZ
Ign http://nz.archive.ubuntu.com saucy/multiverse Translation-en_NZ
Ign http://nz.archive.ubuntu.com saucy/restricted Translation-en_NZ
Ign http://nz.archive.ubuntu.com saucy/universe Translation-en_NZ
Ign http://nz.archive.ubuntu.com saucy-updates/main Translation-en_NZ
Ign http://nz.archive.ubuntu.com saucy-updates/multiverse Translation-en_NZ
Ign http://nz.archive.ubuntu.com saucy-updates/restricted Translation-en_NZ
Ign http://nz.archive.ubuntu.com saucy-updates/universe Translation-en_NZ
Ign http://nz.archive.ubuntu.com saucy-backports/main Translation-en_NZ
Ign http://nz.archive.ubuntu.com saucy-backports/multiverse Translation-en_NZ
Ign http://nz.archive.ubuntu.com saucy-backports/restricted Translation-en_NZ
Ign http://nz.archive.ubuntu.com saucy-backports/universe Translation-en_NZ
Fetched 419 kB in 39s (10.6 kB/s)
Reading package lists... Done
ma@ma:~$




Thank you for the paste and copy your commands
No Upgrade 14.04

What type of computer do you have?
One of my computers is an AMD Athalon 64. The installation of Ubuntu 14.04 failed on that computer. For me it was an irritating inconvenience, since I was planning to do a clean install anyway. Did a clean reinstall of 13.10 - will wait on trying to install 14.xx till later.

Your computer never tried to do the version upgrade. Your sources.list still obviously is set for 13.10 as can be seen in the output of apt-get update. All references are to "saucy".

If everything is working I would leave it alone. There will be problems for a while longer with 14.10 that will be worked out.

On the other hand what shows in the apt-get update output looks good. One thing that kills version upgrades is the presence of 3rd party repos and ppa's. There is the package ppa-purge that will remove the ppa's and the packages from them and attempt to replace them with packages from the repos but mainy people seem unaware of it or don't use it. This, in spite of fairly good documentation and the recommendatin of Ubuntu to use it, is the cause for a lot, if not most version upgrades.

Now that we can be fairly sure that your system is stable, is there some pressing need to upgrade?

It could be that you simply want to. This, of coarse, is up to you. The recommended version upgrade path is to use Update Mangler. You should look at the Ubuntu documentation on using that to make sure you get it right.

You say that you are getting a message that the upgrade for Kubuntu 14.04 is available. This could be. I am not certain what the arraingement is in regard to Kubuntu at all. Never used it but know that it is handled under agreement with some company outside Canonical. Would still, I am sure, be hosted on Canonical servers.

There was a post here on LQ that the upgrade for 12.04 to 14.04 will not be ready until the step release of 14.04.1 in July. That should not affect you as that is a very long jump, LTS to LTS and they both need some packages added to make it work. In the past all that work was done in the last 6 weeks of development of the new LTS.

It could well be that there are some issues with that upgrade even from 13.10. There seem to be some threads indicating some problems. This is not unusual close to the release of a new version.

Ubuntu strongly discourages the use of any upgrade paths other than Update Mangler. They may have some good reason for this.

I have not used Ubuntu for some time. You can not, however, upgrade to the next dev release (Ubuntu-testing) before the start of the production of dailies or the release of Alpha 1 using Update Mangler. All experienced testers were upgraded to the next version about 3 days after the release of a version though. We used the Debian way of upgrading.

I also used it for stable version to stable version upgrades. This can be very messy. Ubuntu is designed in a rather strange way and there can be some very stuborn packages and configurations that resist upgrading vigorously. Update Mangler has been modified to fight this out in the "clean up" phase of a version upgrade. Basically running "dpkg --configure -a" over and over again. Can take quite a while.

You can try this if you want. The fact that there seems to be some trouble should give you a pause.

Your sources list must be edited to call for 14.04 instead of 13.10. So all instances of "sausy" need replaced with "trusty". This can be done manually in a text editor. A lot of text editors have a search and replace function that will work. Or;
should work as long as I have the name "trusty" correct (I think it is but I am not going to an Ubuntu site to check).

You want to make sure to make sure that 13.10 is full upgraded before doing any of this.

Once you change the sources.list you just run;
updates you list of available packages from the 13.10 repo contents to the contents of the 14.04 repo.
will list all packages that need upgraded. Will hold back any that need to remove existing packages or install other new packages. Will upgrade everything else.
will upgrade the held back packages, removing any packages needing removal and adding an needed additional packages.

This can all be done at once with;
Repeating, Ubuntu thinks this is a bad idea. I never had it go smoothly with version upgrades but I only did it with LTS to LTS upgrades. The upgrades from a new release to a new dev version were all very smooth but there is really very little difference in the 2 versions at that time.

Worked fine for me for the Squeeze to Wheezy upgrade that I did just to try it. I did a clean install of Wheezy to actually use.

A clean install will clear out any cruft that has built up in your system. Also gives you a chance to improve your partitioning scheme. If you are installed on one partition this would be a good opportunity to install on / and /home.

If you are already installed on / and /home you could make room for a new / partition, install with a different user name than is currently used in 13.10 and point the installer at the existing /home with instructions not to format that partition. This would give you a clean install of 14.04 using the same /home partition as your working installation of 13.10.

This is a good way to try out the install of an unknown version. Makes sure you still have a working OS.

You could also add a couple partitions and do a traditional dual boot with 13.10 and 14.04.

It is up to you what you do. I quit using Ubuntu for what I think are very good reasons and feel that I should mention that option too. You really could try and install a Linux OS that doesn't do things like modify the file system in rather strange and arbitrarey ways. A distro that can be trusted to be there for the user and maintain services that it incorporates into its OS. A distro that has a relatively smooth version upgrade path. Those 3 things apply to nearly all Linux distros that are not Ubuntu or Ubuntu based.

Hi Widget and Steve
My computer is Asrock Fm1a55m-dgs r2.0
Thank you so much for all the information,your comments regarding Ubuntu and dual boot 13.10 and 14.04
Will now wait for new upgrade later on
Certainly worth useing your recomended commands
Regards
Maurice

Hi Widget
I have to confess I did not take your advice regarding leave system as is 13.02 was working no problem
I used command
Sudo aptitude update and Sudo aptitude full-grade
Now un able start system Kubuntu flashes on desktop then just a black screan with list
starting lightDM Display Manager stoping send an event to indicate plmouth is up, is just one of 4 lines
Re install from CD looks like to only whey to have Kubuntu on desktop
Maurice

Back sometime before 10.04, when Squeeze became testing, the Debian recommended upgrade tool was aptitude. Since Squeeze the recommended tool is apt-get.

They are quite different. Both are great tools. Aptitude has some very nice functions that you have to hunt for in the apt-get family of tools. Haven't ever found a good apt-get command like the aptitude "why" and "why-not" commands to find out why a package is installed or why you can't install a package.

Have never done a version upgrade with aptitude. It should work but they removed it from the repos and so you are not going to get a lot of sympathy from the folks at Canonical.

Have you booted to recovery?

Have you run;
That will attempt to rerun the install script on any packages that are not properly installed. May have to run it several times. Just watch the list at the end of packages that it couldn't handle. When it stays the same it is time to go to something else.

Like;
Which tries to force install of all uninstalled/malinstalled packages.

Just booting to recovery triggers some fault detection and mild repair so it is always worth a shot and running those commands from that root prompt doesn't have to deal with Xorg being started and using resources and mounting certain files so they are a bit more powerful.

The only KDE install I have is on my loaner drive to show Linux to folks that may be interested. That is under Mageia 3 which has both Gnome and KDE. I am an old Gnome user and actually dislike KDE intensely. Just don't like it. Embarrassing to find I prefer to boot to KDE in the Mageia installs (have 32bit and 64bit installs on the loaner for 4 different systems). I may dislike KDE but I am getting to really hate Gnome 3.

This does mean that I don't pay much attention to KDE problems but haven't seen a lot of them lately so that shouldn't be the problem.

You didn't have ANYTHING from a third party installed or from a ppa did you? This will screw you just about everytime. This is true of any distro as far as third party packages although Ubuntu is pretty tender about upgrades anyway. Ppa's are their contribution to complicating the process.

To be fair this is well documented on their site.

Hopefully you cleared the ~./foo files out before trying that. Should have removed them to some directory so that the new ones could be put in with no resistence. KDE was a new DE and so getting it along with a version upgrade could be tricky. You could then put your ~./foo files back for the other DE.

It is your box and there is no need to follow any advice from anyone. You break it you even get to keep the pieces. I am an expert when it comes to breaking systems. Have done a lot of it anyway. It is educational.

If you are on a / and /home install a clean install of anything should work using the same /home. Move those ~./foo files out first. I put them in a /home/<user name>/HIDDEN directory so they are easy to find as they can save you a lot of time configuring your new install having all those things like your browser config and bookmarks and email client account with all the user directories with your email in them. Also things like the playlists for your music player.

You wouldn't need the config files for your other DE but you can clear out the ones you don't want after your clean install is configured. Just delete the HIDDEN (or what ever you call it) directory when it has served its purpose.

You may want to resize some things if you can and put in a data partition. Don't know if you can have the Ubuntu installer write that into your fstab file or if you need to do it later manually so it mounts at boot. That kind of partition is nice because it gives a bit more protection against loss of data when installing. Backup is still a smart thing to do.

Installers are a complex set of scripts and all it takes is one to go wrong to totally screw you. Doesn't happen very often. Once would be all it took though.