Calendar

[Mark Greaves (PCNetSpec)]

OK, can you post the output from both

Code Select Expand

for APT in `find /etc/apt/ -name *.list`; do grep -o "^deb http://ppa.launchpad.net/[a-z0-9\-]\+/[a-z0-9\-]\+" $APT | while read ENTRY ; do USER=`echo $ENTRY | cut -d/ -f4` PPA=`echo $ENTRY | cut -d/ -f5` ; echo ppa:$USER/$PPA ; done ; done
and

Code Select Expand

for APT in `find /etc/apt/ -name *.list`; do grep -o "deb http://ppa.launchpad.net/[a-z0-9\-]\+/[a-z0-9\-]\+" $APT | while read ENTRY ; do USER=`echo $ENTRY | cut -d/ -f4` PPA=`echo $ENTRY | cut -d/ -f5` ; echo ppa:$USER/$PPA ; done ; done

[pooky2483]

The first one, nothing happens.
The second one, I get;

ppa:ffmulticonverter/stable
ppa:upubuntu-com/chat
ppa:kubuntu-ppa/backports
ppa:libreoffice/libreoffice-4-0
ppa:libreoffice/ppa
ppa:webupd8team/tribler
ppa:stebbins/handbrake-snapshots
ppa:n-muench/vlc
ppa:danielrichter2007/grub-customizer
ppa:paul-climbing/ppa
ppa:otto-kesselgulasch/gimp
ppa:flacon/ppa
ppa:vokoscreen-dev/vokoscreen
ppa:noobslab/apps
ppa:relan/exfat
ppa:stellarium/stellarium-releases
ppa:debfx/virtualbox
ppa:webupd8team/tor-browser
ppa:sunab/kdenlive-release

[arochester]

Have you seen? http://askubuntu.com/questions/512848/tex-common-troubleshooting-on-ubuntu-14-04-lts (http://askubuntu.com/questions/512848/tex-common-troubleshooting-on-ubuntu-14-04-lts)
Which mentions a bug: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1236951 (https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1236951)

[pooky2483]

Yeah, I did a search and found the ask Ubuntu one and thought, Great, NOT the solution I wanted.

[pooky2483]

So Mark, what do you suggest? or are you still searching for a solution?

[chemicalfan]

If you open "Software Sources" (use the search function in the KDE menu), you should be able to uncheck all of the PPAs. Then, you can drop into a terminal and run:

Code Select Expand

sudo apt-get update && sudo apt-get dist-upgrade
Post the output here

Edit: I don't think this will work, but it will give us a good clue of where to go next. I think this will require some use of aptitude to fix, as it can work around dependency issues

[Mark Greaves (PCNetSpec)]

OK, I'm thinking the best way to do this would probably be to change all instances of "precise" to "trusty" in the contents of all the files in:
/etc/apt/sources.d

re-enable all the PPA's

try an update

disable any that are broken (nothing in them for trusty)

do a full system update

then see where we're at



If you agree, run:

Code Select Expand

cd /etc/apt
then

Code Select Expand

sudo tar cvf sources.list.d-backup.tar.gz sources.list.d
then

Code Select Expand

cd /etc/apt/sources.list.d
then

Code Select Expand

grep -rl 'precise' ./ | sudo xargs sed -i 's/precise/trusty/g'
now post the output from:

Code Select Expand

for X in /etc/apt/sources.list.d/*; do echo; echo; echo "** $X:"; echo; cat $X; done

[pooky2483]

Done it, here's the list;
What's next?

[pooky2483]

Code Select Expand

sudo apt-get update && sudo apt-get dist-upgrade

[Mark Greaves (PCNetSpec)]

Fire up synaptic and re-enable all the PPA'a

then run:

Code Select Expand

sudo apt-get update
and post if it errors.

BTW, please stop adding command output as an attachment unless specifically asked to do so .. include the text "inline", if you're worried about long output, put it between spoiler tags.

[pooky2483]

BTW, please stop adding command output as an attachment unless specifically asked to do so .. include the text "inline", if you're worried about long output, put it between spoiler tags.

I DO but there is a SIZE LIMIT of 65535 characters (or something similarly large) but that is not enough. Check the size yourself by trying to post the same text between spoiler tags which I am sending as an attachment.

[Mark Greaves (PCNetSpec)]

If necessary, split the output across 2 (or more) posts.

--

[chemicalfan]

Were there any errors from apt-get update?