Package Details: masterpdfeditor 5.4.38-1

Git Clone URL: (read-only, click to copy)
Package Base: masterpdfeditor
Description: A complete solution for creation and editing PDF files
Upstream URL:
Keywords: master-pdf-editor
Licenses: custom
Submitter: farseerfc
Maintainer: pgoetz
Last Packager: Scimmia
Votes: 159
Popularity: 3.32
First Submitted: 2016-12-05 01:50
Last Updated: 2019-07-10 14:54

Latest Comments

1 2 3 4 5 6 ... Next › Last »

jghodd commented on 2020-06-04 19:57

v5.1.68 still works with a rebuild. the originally built package (5.1.68-1) from november threw the same error, which went away with a package rebuild (in may). i can;t get rid of the undefined symbol error in the latest version. yet.


@pgoetz the problem will have to be fixed upstream. there is a reference to QMutexPool::globalInstanceGet in the masterpdfeditor source itself, vs. a library referenced by the app. i'm also finding online references to Qt5 changes where QMutexPool is/was to be removed. the newest version of the Qt5 API (therefore Qt libraries) no longer provides access to a QMutexPool class. we're going to need a new release from above before this'll work. v5.1.68 doesn't have the same reference and does still work.

masx13 commented on 2020-06-04 16:29

Like for OlehL the program doesn't start on my PC. But the issue exists with the original software as well

pgoetz commented on 2020-05-26 11:36

Yes, I'm in the process of rebuilding the package. The version available for download now doesn't work. At the moment I'm working through the dependencies, as it's not at all clear that all of them are actually necessary.

OlehL commented on 2020-05-26 11:31

It doesn't start.

$ masterpdfeditor5 masterpdfeditor5: symbol lookup error: masterpdfeditor5: undefined symbol: _ZN10QMutexPool17globalInstanceGetEPKv

jharrop commented on 2020-05-26 00:26

@j1simon your instructions worked nicely thank you. Just to note that first I had to move the old /opt/master-pdf-editor-5 etc files out of the way.

j1simon commented on 2020-05-24 09:42

@zwastik I have edited the PKGBUILD
This is all that should not be done but since the developers of this program do not do what they have to do, we (the users) have to do these dirty things in order to use their program.

First uninstall current masterpdfeditor-libs.
Download the new one with name PKGBUILD to a new folder and execute makepkg -sci in that folder.

From now on whoever has problems with this PKGBUILD should fix it himself or make a comment on the github page, not here.

This was supposed to be a temporary solution but it's been 5 months (maybe more) and it's still the same... In these cases I believe that the best solution is for users to move from companies of this type and look for other alternatives (which there are).

zwastik commented on 2020-05-23 19:25

> masterpdfeditor5

/bin/sh: warning: shell level (1000) too high, resetting to 1 /usr/bin/masterpdfeditor5: line 13: /usr/bin/masterpdfeditor5: Argument list too long

while running @j1simon PKGBUILD

jdegreef commented on 2020-05-20 21:16

Thanks for taking care of this package :)

nursoda commented on 2020-04-18 23:47

Thank you, it's always good to have statements directly from the devs.

My personal view is that the purpose of an AUR package is to ease installation of material provided by upstram. It should not break the system for sure but I applied the patch below and after that, all I had to do is " -S masterpdfeditor". That exactly matched my expectations. I'm happy that some folk look close and rant that it's not the way it shall me and perfect if the dev agrees and sets out to fix in in future releases. Thank you all!

dibadov commented on 2020-04-18 23:10

On behalf of Code Industry as we already replied in numerous emails, we don't consider package with Qt binaries a permanent solution. This is a temporary fix.

At the moment we work hard on the next version. In order not to rush it, we've made -all package as a workaround until the next release, so we have enough time to provide certain level of quality.

Some of our answers in email could have been misleading, sorry for that.