Problem with Team Viewer after upgrading from 12.04 to 14.04

[Cindy-Sue Causey]

On 8/29/14, Pep3ts <pep3ts at gmail.com> wrote:
>
> This is the output:
>
> sudo apt-get teamviewer:
> no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package teamviewer is not available, but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
> However the following packages replace it:
>    teamviewer9
>
> E: Package 'teamviewer' has no installation candidate
>
< snipped for brevity >
>
> I remember that on 12.04 I downloaded the .deb package from the web site...
>
> It seems that are absolutely neededthe packages lib32asound2 and
> ia32-libs but I cant'install them (outputs in my previus mail).
>
> Does anyone know what are these packages and if there are any equivalent
> alternatives?


This may or may not help but... I've run into this more than a few
times and seriously beat my head up against the wall over it.. What
was happening for me was my brain would lock down as soon as I'd read
the first part of the error message.. One day I FINALLY read the whole
thing and comprehended this part:

"is only available from another source"

Ohhhh, "another **source**", it says. That was my clarity moment. This one, too:

"E: Package 'teamviewer' has no installation candidate"

One translation of that part is "has no installation candidate" based
on the limited personal choice of repository sources we each
singularly pick for our systems to use..

So....

What kind of shape are your repository /etc/apt/sources.list,
/var/lib/apt/lists, and anything similar in? I'm command lining apt,
dpkg, wget for my installations, upgrades, etc and so am not versed in
the rest if anyone else can suggest other locations to look.

Your subject line says "upgrading" re the entire system so there's
potential for your old repository choices that used to work to have
been quietly overwritten.. It's possible reviewing your sources.list
type entries, making even one change such as toggling something like
third party software to on/active/yes/checkmarked/un-hash marked, and
then updating MIGHT correct this..

If that turns out to be at least part of your problem and you're a
novice at all at this, don't to do what I did.. I listened to people
online about going in and manually moving things around and deleting
things like the content of /var/lib/apt/lists.. I got lucky in that
the system I actually *destroyed* was replaced one 20 minute
re-install later. It was an irreplaceable personal learning experience
but others might not end up so lucky..

One Life Lesson learned the hard way as a tip for anyone new at this
and who's scouring the Net for how-to's: Whatever CHOICE you're making
for package installs, come at any necessary changes from the outside
in. Follow "due process".

Don't start any changes by chipping away at your package manager's gut
(e.g. deleting all the files in /var/lib/apt/lists).. Doing so throws
a monkey wrench in our package managers' thought processes, leaves a
huge hole smack in the middle of the computational process that
regulates literally tens of thousands of software packages.. It can
easily end up game over at that point with a complete new re-install
becoming the primary rational solution..

Sorry about the extended ramble. Figured I might as well say it to
prevent anyone from having to go through what I did.. If you've
already addressed the above suggested angle on this particular
question, my apologies.. In that case, I have NO CLUE. *grin*

Hope this helps someone.. :)

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *