it won't let me upgrade saying it's 3rd party software even though it says it disabled them.

Bug #1335003 reported by ser nerd
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

it won't let me upgrade saying it's 3rd party software even though it says it disabled them. i found someone else on the ubuntu site http://askubuntu.com/questions/451616/answer/submit but i couldn't follow the fix they suggest. i got a y ppa manager in case it was sources.lists talked about in the thread, but no joy. i'm lost. i've never had this problem with an upgrade before. don't think i have added any 3rd party software since last upgrade

how do i fix this upgrade issue. i appreciate any help especially since i am only a geekling. i am in way over my head. and i need this upgrade for things have stopped working properly like my mic so i looks like i need the the new version. i am currently 13.10 trying to get 14.04

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-release-upgrader-core 1:0.205.6
ProcVersionSignature: Ubuntu 3.11.0-24.41-generic 3.11.10.11
Uname: Linux 3.11.0-24-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
CrashDB: ubuntu
Date: Fri Jun 27 00:51:58 2014
InstallationDate: Installed on 2012-10-16 (618 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to saucy on 2014-06-27 (0 days ago)

Revision history for this message
ser nerd (searchnetinfo) wrote :
Revision history for this message
ser nerd (searchnetinfo) wrote :

was trying to follow the txt above and the last one says i have broken packages but the y ppa manager says i have no broken packages so i am not sure what's the what with that. the y ppa manager i got came from this thread http://askubuntu.com/questions/42895/is-there-a-tool-to-update-my-ppa-sources-list-entries-after-upgrading

Revision history for this message
ser nerd (searchnetinfo) wrote :

oh, it occurs to me to add that i did have a problem with the video driver a while ago (was trying to find one that played videos better, they are slow jerky and laggy ) and it took some poking in packages and other places to stop getting a black screen when i tried to log in. can't for the life of me remember how i fixed it. took hours and i was really brain dead by then. not sure if that helps for it has been working fine since i sorted it. followed some how to on ubuntu site.

that's all i can thing of...

Revision history for this message
ser nerd (searchnetinfo) wrote :

ok have been doing some more hunting and others seem to have video driver issues fixed with sudo apt-get remove xserver-xorg-video-* and while i am not using that xorg driver (i checked) so it shouldn't be an issue (using propreitory fglrx-updates amd graphics acceloraters) l i did find lots of broken stuff with those names and removed them and am going to try this again...once more into the breach =P

did it and then tried upgrade again and it did go farther than before before it got cranky. looked like it was going to abort the upgrade again, actually got a msg it was but then it continued on with the regular error msg that i tried to write down. it had to do with debconf, something like unable to initialize front end, dialogue front end requires screen at least 13 lines tall and 31 columns wide. that makes no sense to me for my screen is pretty big. any way it kept saying something like revert to front end at the end and then just kept going. things look like they are working but i have no idea why this upgrade was so problematic. i have never had a problem like this before.

if it helps AMD C-50 Processor × 2 since it looked like there were some broken drivers. it is good to note that i only got my video drivers, when i was trying to get a better one for video, from the unbuntu software updater.

thanks for all your hard work on all the various upgrades over the years. i think it's ok now but if you need to contact me if it helps with bug fixing things then feel free.

warm wishes
ser

Revision history for this message
ser nerd (searchnetinfo) wrote :

ok one more thing occurs to me that might have caused the upgrade problems is a bug that popped up when i upgraded to 13, which was that wifi wont' connect when waking from suspend. it took a lot of hunting on the forums to find a workaround and i am darned if i remember what i ended up doing. i think of it now for it has reoccured with this upgrade which is a huge drag for i mostly use suspend. it connects fine with a reboot but will not connect to wifi in any way shape or form from suspend

Revision history for this message
ser nerd (searchnetinfo) wrote :

wait i found it. a slightly different version of this sorted it last time and this version sorted it this time down vote

sudo touch /etc/pm/sleep.d/wakenet.sh

sudo chmod +x /etc/pm/sleep.d/wakenet.sh

sudo gedit /etc/pm/sleep.d/wakenet.sh

Insert the following lines:

#!/bin/bash
case "$1" in
thaw|resume)
nmcli nm sleep false
pkill -f wpa_supplicant
;;
*)
;;
esac
exit $?

And then save.

hope that helps with bug fixings. i know you all work so hard and i wanted to help as much as my geeklingness could allow.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
Revision history for this message
Nick Rosbrook (enr0n) wrote :

This is probably no longer relevant, but was caused by PPA packages. E.g,

Installing libosmesa6 as Recommends of wine1.6-i386
  MarkInstall libosmesa6 [ i386 ] < none -> 10.1.3-0ubuntu0.1 > ( libs ) FU=0
  libosmesa6:i386 Depends on libglapi-mesa [ i386 ] < 10.3.0~git20140618.88b887fa-0ubuntu0ricotz~saucy > ( libs ) (= 10.1.3-0ubuntu0.1) can't be satisfied!

Changed in ubuntu-release-upgrader (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.