Bug 26865 - Mageia 7 LXQt - notepadqq: error while loading shared libraries: libhyphen.so.0
Summary: Mageia 7 LXQt - notepadqq: error while loading shared libraries: libhyphen.so.0
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: David GEIGER
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-26 18:41 CEST by psyca
Modified: 2020-06-26 22:20 CEST (History)
0 users

See Also:
Source RPM: notepadqq
CVE:
Status comment:


Attachments
Install selection (99.27 KB, image/png)
2020-06-26 18:42 CEST, psyca
Details

Description psyca 2020-06-26 18:41:15 CEST
Description of problem:
Install Mageia 8 (with onlinemedia activated) and LXQt Desktop, like in the attached screenshot.

If you want to run notepadqq it doesnt start.
If you try to run it via console you get the following output

----
notepadqq: error while loading shared libraries: libhyphen.so.0: cannot open shared object file: No such file or directory
----
Comment 1 psyca 2020-06-26 18:42:05 CEST
Created attachment 11721 [details]
Install selection
psyca 2020-06-26 18:46:25 CEST

Priority: Normal => High

psyca 2020-06-26 18:48:41 CEST

Priority: High => Normal

Comment 2 Lewis Smith 2020-06-26 20:18:50 CEST
Thank you for the report.
This package has not evolved for ages; last action in Feb Mageia 8 Mass Rebuild. Does this problem come from there?

Assigning to DavidG as having done the last version update.

Assignee: bugsquad => geiger.david68210
Source RPM: (none) => notepadqq
Severity: critical => normal

Comment 3 psyca 2020-06-26 22:20:23 CEST
Have to change it.
Its not MGA 8, its MGA 7 only. I installed from the wrong iso.

Summary: Mageia 8 LXQt - notepadqq: error while loading shared libraries: libhyphen.so.0 => Mageia 7 LXQt - notepadqq: error while loading shared libraries: libhyphen.so.0
Version: Cauldron => 7
Status: NEW => RESOLVED
Resolution: (none) => INVALID


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