An unresolvable problem occurred while calculating the upgrade.

[steve7233]

I just noticed they are all 64bit packages no 32 bit packages. I wonder what is really going on. I just checked the contents of main.log and it shows that apt tried to fix these by making assumptions. Since Synaptic package manager can't find any broken packages then I wonder if the 64bit upgrade is bugged. Maybe only the 32bit version works.

[steve7233]

See https://help.ubuntu.com/community/SaucyUpgrades/Kubuntu for instructions on upgrading to 13.10.

I already tried that several times.

[Spadge]

I was just looking back at the 1st few replies and noticed that you forgot to tell me to add the -i switch when getting the list of broken packages from apt.log.

My syntax was fine; you decided to change it and broke it with your 'BROKEN' instead of 'Broken'.

But yes, -i kinda works too.

You used to have xorg-edgers in your ppa? If all you did was remove it from your sources lists, put it back and use the ppa-purge cmd to remove it properly, replacing all the packages it installed with regular versions from canonical. I am not convinced that it's your intel drivers that are the problem.

Try this cmd to see where the problem packages come from:

spadge@Jupiter:~$ apt-cache policy xserver-xorg-video-all
xserver-xorg-video-all:
  Installed: 1:7.7+1ubuntu6
  Candidate: 1:7.7+1ubuntu6
  Version table:
 *** 1:7.7+1ubuntu6 0
        500 http://gb.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

[steve7233]

steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:/var/log/dist-upgrade$ apt-cache policy xserver-xorg-video-all
xserver-xorg-video-all:
  Installed: 1:7.7+1ubuntu4
  Candidate: 1:7.7+1ubuntu4
  Version table:
 *** 1:7.7+1ubuntu4 0
        500 [url]http://mirror.math.ucdavis.edu/ubuntu/[/url] raring/main amd64 Packages
        100 /var/lib/dpkg/status
steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:/var/log/dist-upgrade$

When I installed the Intel driver I first used the purge cmd to remove xorg-edgers then ran the intel-graphics-installer. I suspect the Intel driver isn't completely removed but I can't figure out how to reset to default Ubuntu graphics which is probably needed to do the upgrade.

[steve7233]

Since I am unable to upgrade from raring to Saucy then do I need to install Saucy from scratch?

[steve7233]

I still can't get the upgrade to work.

[steve7233]

Since none of the replies on this thread resulted in solving my problem (thanks for trying), then I did a google search and found a thread on the ubuntu forms that appears to have worked.

sudo apt-get remove xserver-xorg-video-ati:amd64

the name of the thread is http://askubuntu.com/questions/36029...te-the-upgrade . The upgrade is running now.

[steve7233]

Since none of the replies on this thread solved my problem -thanks for trying everyone - then I decided to do a google search and found this thread: http://askubuntu.com/questions/36029...te-the-upgrade . I tried several fixes and found this:

sudo apt-get remove xserver-xorg-video-ati:amd64

. I tried the upgrade again and it got further. Unfortunately after several minutes the upgraded failed:

Upgrading
Create a snapshot of '/tmp/apt-btrfs-snapshot-mp-msPOk_/@' in '/tmp/apt-btrfs-snapshot-mp-msPOk_/@apt-snapshot-release-upgrade-saucy-2013-10-29_12:10:04'
umount: /tmp/apt-btrfs-snapshot-mp-msPOk_: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))


A fatal error occurred 

Please report this as a bug and include the files 
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in 
your report. The upgrade has aborted. 
Your original sources.list was saved in 
/etc/apt/sources.list.distUpgrade. 

Traceback (most recent call last): 

File "/tmp/ubuntu-release-upgrader-pou8qt/saucy", line 10, in 
<module> 
sys.exit(main()) 

File 
"/tmp/ubuntu-release-upgrader-pou8qt/DistUpgrade/DistUpgradeMain.py", 
line 243, in main 
if app.run(): 

File 
"/tmp/ubuntu-release-upgrader-pou8qt/DistUpgrade/DistUpgradeController.py", 
line 1791, in run 
return self.fullUpgrade() 

File 
"/tmp/ubuntu-release-upgrader-pou8qt/DistUpgrade/DistUpgradeController.py", 
line 1756, in fullUpgrade 
if not self.doDistUpgrade(): 

File 
"/tmp/ubuntu-release-upgrader-pou8qt/DistUpgrade/DistUpgradeController.py", 
line 1123, in doDistUpgrade 
self._maybe_create_apt_btrfs_snapshot() 

File 
"/tmp/ubuntu-release-upgrader-pou8qt/DistUpgrade/DistUpgradeController.py", 
line 1105, in _maybe_create_apt_btrfs_snapshot 
res = apt_btrfs.create_btrfs_root_snapshot(prefix) 

File "/tmp/ubuntu-release-upgrader-pou8qt/apt_btrfs_snapshot.py", 
line 169, in create_btrfs_root_snapshot 
self.umount_btrfs_root_volume() 

File "/tmp/ubuntu-release-upgrader-pou8qt/apt_btrfs_snapshot.py", 
line 155, in umount_btrfs_root_volume 
os.rmdir(self._btrfs_root_mountpoint) 

OSError: [Errno 16] Device or resource busy: 
'/tmp/apt-btrfs-snapshot-mp-msPOk_' 


steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:/var/log/dist-upgrade$

Any ideas on how to proceed?

[steve7233]

I just used Apport to report this to Lauchpad > ubutu: Fatal error on upgrading from Raring Ringtail To Saucy Salemander. Saving snapshot to BTFRS partion failed. I am steve77 on Launchpad.net .

[SteveRiley]

Since none of the replies on this thread solved my problem -thanks for trying everyone - then I decided to do a google search and found this thread: http://askubuntu.com/questions/36029...te-the-upgrade . I tried several fixes and found this:

sudo apt-get remove xserver-xorg-video-ati:amd64

. I tried the upgrade again and it got further.

That command would be useful only if you knew that you had AMD/ATI graphics in your system.

I think you have an unstable package state that the upgrader can't figure out how to sort through. We could go a few rounds of messages where I'd walk you through a number of information gathering steps using apt-cache and dpkg. It might take a few days, as I have a lengthy rehearsal Wednesday (dress rehearsal, Seattle Wind Symphony) and I'm traveling to San Francisco all day Thursday. It might be faster for you to just reinstall.

[steve7233]

It did remove something. I am guessing that using the purge command to remove Exorg-edgers left that one file or maybe it was something left over from the generic Intel driver.

I tried the upgrade again and it started and ran for a bit until I got the error refered to in #38. After reporting the bug I found that some one else had the same fatal error and they discovered that cron had run another update at the same time they were updating to Saucy! I decided to try it again and it worked all the way until the Grub config file. It said there was a new version. I selected the optionI to compare the two files. I couldn't figure out how to get back to the update to finish. I tried typing [CTRL]z but unfortunatly that stopped the upgrade! I tried starting again hoping it would finish but it said there was no update. I tried a reboot hoping I hadn't broken my system. It seems to still work but network manager says there is no wired or wifi connection but there seems to be something since this works. So how do I finish configuring Saucy Salamander?

I just ran about in system settings and it shows that I am running Kubuntu 13.10 so it looks like the Salamander finally got hatched. It just didn't get configured properly.

[steve7233]

When I select leave from the KDE menu it only shows log out and lock. It does not have the options to restart or shut down. I had re enabled hibernate mode about 3 days ago and now that option is gone.

[steve7233]

Looks like font config needs to be run as logout via KDE menu and sudo halt via konsel do not work and the screen fills with font config errors in line x. The monitors settings have to be adjusted every time I boot up. It doesn’t seem to save them. Could this be related to font config not running?

[steve7233]

I think I got it fixed! I rebooted and selected recovery mode at the grub prompt and was able to fix the system. I am not sure if everything works right. As far as I can tell everything is working. I thought the new about in system settings would show all the hardware. It only shows the memory.

[steve7233]

Virtual Box might be broken as Windows Vista VM froze. The only thing I could do was press and quickly release the power button resulting in the shut down signal being sent. Then I restarted the computer and booted up Saucy.