Update-manager hata ile sonlandırıldı

[Erto06]

ubuntu 14.04 versiyon için

Yükseltme hesaplanamadı

An unresolvable problem occurred while calculating the upgrade.

 This can be caused by:
 * Upgrading to a pre-release version of Ubuntu
 * Running the current pre-release version of Ubuntu
 * Unofficial software packages not provided by Ubuntu

Eğer bunlardan hiçbiri olmazsa lütfen bu hatayı uçbirimden izleyen komut ile bildirin: 'ubuntu-bug ubuntu-release-upgrader-core'.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.14.11
ProcVersionSignature: Ubuntu 3.8.0-35.52~precise1-generic 3.8.13.13
Uname: Linux 3.8.0-35-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CurrentDmesg.txt:
 [ 3.243688] vboxpci: IOMMU not found (not registered)
 [ 3.537740] init: plymouth-stop pre-start process (1463) terminated with status 1
 [ 307.986799] audit_printk_skb: 42 callbacks suppressed
 [ 307.986802] type=1400 audit(1391158270.011:25): apparmor="DENIED" operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=1040 comm="cupsd" pid=1040 comm="cupsd" capability=36 capname="block_suspend"
 [ 321.991273] type=1400 audit(1391158284.034:26): apparmor="DENIED" operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=1040 comm="cupsd" pid=1040 comm="cupsd" capability=36 capname="block_suspend"
Date: Fri Jan 31 10:50:36 2014
GsettingsChanges:
 com.ubuntu.update-manager first-run false
 com.ubuntu.update-manager launch-time 1391158012
 com.ubuntu.update-manager show-details true
 com.ubuntu.update-manager window-height 500
 com.ubuntu.update-manager window-width 600
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: update-manager
Symptom: ubuntu-release-upgrader-core
UpgradeStatus: Upgraded to precise on 2014-01-31 (0 days ago)

[Seth Arnold (seth-arnold)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.