← Back to team overview

kernel-packages team mailing list archive

[Bug 1524191] Re: was attempting to upgrade to 15.04, yet it could not due to "software channels"?


** Package changed: linux-lts-vivid (Ubuntu) => ubuntu

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.

  was attempting to upgrade to 15.04, yet it could not due to "software

Status in Ubuntu:

Bug description:
  I don't know exactly if this is a bug or something in my network. I attempted to upgrade from 14.04(I believe, not sure) in the past before to utopic unicorn yet never successful. Now I am on a different PC that had windows previously installed(But is new and had win10 on it for like a week). Yet I am from the same location, but with different network info....While I am at it I might as well tell you that a while back, the last time I used Ubuntu which I have for years, but my friend got a hold of my password (He's really good with computer stuff, but he activated the SU and did all kinds of stuff that caused me to loose that PC) Anyway just said this cause in the back of my mind, the recent problems I've had .....anyway I know that there are some portraying/with microsoft based on the things that have happened ....just reporting I don't know if this is a bug or not, but will ask on askubuntu too. 
  Thank You, 

  Have a Happy Day, 
  Nathan C. Steward

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-39-generic 3.19.0-39.44~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec  8 23:34:58 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-06 (2 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: Upgraded to trusty on 2015-12-09 (0 days ago)

To manage notifications about this bug go to: