Can't install applications. 13.2

Hello,

Lately I’m having problems installing applications. I’m using Opensuse 13.2 x86-x64 and i tried to install VirtualBox (downloaded from the site) but gave me an error “installation aborted by user”. After that i tried via repositories an after the install it didn’t open, i found that it was installed “vboxgtk” instead “vboxqt”, then it worked…

But the same is happening with TeamViewer. I tried the latest build and the older one and can’t install it. Funny is, in my wife’s PC, it’s the same problem.

Both systems are fully updated and working well (besides this problem).

Any thoughts?

P.S. I’m not using my nvidia driver 'cause it’s not important nowadays and in my wife’s pc there are no ATI drivers installed too. I hope think this is causing the problem.

Thanks in advance

On 2015-08-06 00:46, hugosyt wrote:
> site) but gave me an error “installation aborted by user”.

you are using apper. use YaST or zypper instead.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

Strange 'cause i always used Apper and always worked. How do i install it with YaST or/what is the command line for zypper?

Thanks

Appr at best is a toy. It is ok for notifications of updates but as an installer either yast or zypper are far better.

Also it is far better to install from the repos rather then download some rpm.

zypper in pathetorpm

On 2015-08-06 03:26, hugosyt wrote:
>>> site) but gave me an error “installation aborted by user”.
>>
>> you are using apper. use YaST or zypper instead.
>
> Strange 'cause i always used Apper and always worked. How do i install
> it with YaST or/what is the command line for zypper?

It is a known problem with apper, when it hits some dependencies issues.

What do you want to install, where is it? If it is in a repo, just start
yast, module software management, search for the package, install. You
can also create your own local repository with a local directory, or
feed the rpm via command line to “yast sw_single…” …here. Just read
this thread from a month ago, same question:

http://forums.opensuse.org/showthread.php?t=508500


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

I’m not trying to install applications through repos (i know how to do that, thanks anyway) but from a downloaded file from teamviewer site.

I used zypper in and got thir error:

"Header V4 DSA/SHA1 Signature, key ID 72db573c: NOKEY
V4 DSA/SHA1 Signature, key ID 72db573c: NOKEY

teamviewer-10.0.41499-0.i686(Plain RPM files cache): Signature verification failed [4-Signatures public key is not available]"

That’s no error, but a warning that the package is not signed with a known key (i.e. you install it at your own risk). And that’s probably also the reason why you couldn’t install it with Apper (although I do think it should be possible, there’s probably some other problem).

It should have been installed now though.

Type “zypper se -s teamviewer” or “rpm -q teamviewer” to verify.

Got this message:
**
Loading repository data…
Reading installed packages…
No packages found.

**

Well, then try with rpm instead:

sudo rpm -ivh teamviewer-10.0.41499-0.i686.rpm

Btw, you try to install a 32bit package on your 64bit system. Maybe you miss some necessary 32bit libraries?
But then zypper should have told you about that fact or even installed them automatically.

Got this one and some dependencies:

key ID 72db573c: NOKEY
error: Failed dependencies:
libjpeg.so.62 is needed by teamviewer-10.0.41499-0.i686
libpng12.so.0 is needed by teamviewer-10.0.41499-0.i686
libSM.so.6 is needed by teamviewer-10.0.41499-0.i686
libXtst.so.6 is needed by teamviewer-10.0.41499-0.i686

None of them show in YaST?
This 32bit package is the only one in their site so i have no other option.

The corresponding packages are:

  • libjpeg62-32bit
  • libpng12-0-32bit
  • libSM6-32bit
  • libXtst6-32bit

On 2015-08-06 15:26, hugosyt wrote:
> This 32bit package is the only one in their site so i have no other
> option.

Looking at the site
https://www.teamviewer.com/es/download/linux.aspx
I see that the .deb is multiarch, both 32 and 64 bit.
But I believe it is false, it is 32 bit.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

IIANM, “multiarch” practically means a 32bit package that can be installed on 64bit systems too, together with the 64bit package if available.
It’s something similar to openSUSE’s xxx-32bit packages.
It doesn’t mean that the package contains binaries for both architectures.

See also: https://wiki.debian.org/Multiarch/HOWTO

I managed to install the application (after installing the dependencies) with “zypper in” even with the warning of having “nokey” signed message.
So all this is because of Apper not recognising the dependencies, because of the “nokey” signed or both?

Can this overall method be used to install other apps that give me the same error?

Yeah, .deb packages seam to have the 32, 64bit option.

Thanks.

On 2015-08-06 16:56, wolfi323 wrote:

> IIANM, “multiarch” practically means a 32bit package that can be
> installed on 64bit systems too, together with the 64bit package if
> available.

I thought so.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

On 2015-08-06 17:06, hugosyt wrote:
> Can this overall method be used to install other apps that give me the
> same error?

Of course. It is quite common.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

It’s not that Apper does not recognize the dependencies. The “problem” is that PackageKit (Apper is just a frontend to that) cannot resolve dependency conflicts, i.e. it doesn’t support asking the user when there are conflicts but just aborts.

But at least zypper should have installed the dependencies automatically.
The only thing that I find “fishy” is that the dependency errors by rpm do have no indication that the 32bit versions are needed.
So maybe the package doesn’t correctly specify them.

OTOH, you didn’t post the whole zypper output, did you?

because of the “nokey” signed or both?

Might be that this was the actual problem, yes.

Can this overall method be used to install other apps that give me the same error?

In principle, yes.

Yeah, .deb packages seam to have the 32, 64bit option.

No, also for .deb there’s only the 32bit package. Again, in this case “multiarch” means that it can be installed on 64bit systems too.
It’s not different with the .rpms, it’s just not called “multiarch” here.