Bug 28489 - Installing 3rd party app Anydesk throws up error on libpangox
Summary: Installing 3rd party app Anydesk throws up error on libpangox
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://anydesk.com/en/downloads/linux
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-28 12:30 CET by isadora
Modified: 2021-02-28 21:46 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description isadora 2021-02-28 12:30:58 CET
Description of problem:

Trying to install anydesk_6.1.0-1_x86_64.rpm downloaded from https://anydesk.com/en/downloads/linux

Just after starting installation following message appears:
Some requested packages cannot be installed:
anydesk-6.1.0-1.x86_64 (due to unsatisfied libpangox-1.0.so.0()-(64bit))
Continue installation anyway?

I have lib64pango1.0_0 installed which provides /usr/lib64/libpangx-1.0.so.0
As well as libpango1.0_0 which provides /usr/lib/libpangx-1.0.so.0
Jani Välimaa 2021-02-28 13:19:10 CET

Summary: Installing Anydesk throws up error on libpangox => Installing 3rd party app Anydesk throws up error on libpangox

Comment 1 Jani Välimaa 2021-02-28 13:26:05 CET
The real error msg is:
"A requested package cannot be installed:
anydesk-6.1.0-1.x86_64 (due to unsatisfied libpangox-1.0.so.0()(64bit))
Continue installation anyway? (Y/n)"

libpangox-1.0.so.0 was provided by pangox-compat which was dropped because it was failing to build:
https://svnweb.mageia.org/packages?view=revision&revision=1568259
Comment 2 isadora 2021-02-28 14:15:03 CET
I installed an older version: anydesk-5.0.0-1.mga5.x86_64.rpm
which installed fine.
Comment 3 Lewis Smith 2021-02-28 21:46:42 CET
Thanks Jani for the insight.

I think this can be closed; please excuse the 'invalid', since it involves a 3rd party application.

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.