Arch Linux User Repository

The next person who discusses keygens will have their account suspended indefinitely.

@asamarin I'm not sure of how this patch should work, I'm used to get and install those packages with yay, so I don't really have the method to apply it

However if it fixes for everyone I guess that it should be fine. The maintainer should push it and I will try it when he will do so, and if a new problem arises I will make a new comment here and we will think about it

If it's not an automatic update, the maintainer last intervention look like been at 2020-04-07 19:28 on chromium-widevine, and his last comment at 2020-03-29 14:14 in grass. So i don't know where he is but he should see our comments, if he's fine

@asamarin The patch wasn't chopped off. If it were, the patch tool would complain because the line counts in the hunk would not match. The end of it is the "if [...] then" statement in the existing file - because you're looking at a diff of a diff. The sha1 sum discrepancy is due to whitespace differences.

Hey guys @yannleretaille and @nursoda: I wanted to apply this same patch given the positive reactions towards it, but it turns out it's incomplete! Take a closer look at the last line, it seems to be chopped after an "if [ ... ] then" statement. That's likely the reason checksum didn't match, and I guess it was chopped without @bkb noticing due to some sort of comment size/line-count limit.

If @bkb or somebody else can get the last part of the patch posted here, that'd be great; on the other hand, it seems to not be terribly important since it still worked for you guys.

I can also confirm that the package installs fine on a newly installed arch with the patch installed. However, I had to adjust the second checksum, not sure why.

I can confirm wild34s patch fixes the issue. It would probably make sense to update the package accordingly (for now).

Alors ouiiii euhh, ça marche paaass euuhh

Ou devrais-je dire

Same as @unixtastic, it seems to be a problem related to C libraries and Qt

For reference: https://www.reddit.com/r/openSUSE/comments/fj9seb/masterpdfeditor5_cannot_be_launched_anymore/

@farseerfc consider the following git patch to fix the annoying issue with Qt libs.

diff --git a/PKGBUILD b/PKGBUILD
index cdfb30e..e0a6916 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -11,8 +11,13 @@ url='https://code-industry.net/free-pdf-editor/'
 arch=('x86_64')
 license=('custom')
 makedepends=('patchelf')
-source_x86_64=("https://code-industry.net/public/master-pdf-editor-${pkgver}-qt5.amd64.tar.gz")
-sha1sums_x86_64=('fd3e19479a298bfe6770b5dddd67b009742e9321')
+source_x86_64=("https://code-industry.net/public/master-pdf-editor-${pkgver}-qt5-all.amd64.tar.gz" "masterpdfeditor.sh.patch")
+sha1sums_x86_64=('bff9d66b531e60603a9221cf6bd2595c6bf602d6'
+                 'bc98283763d229f6d0d0a50350fb02daeba9238c')
+prepare() {
+    cd "$srcdir/master-pdf-editor-${pkgver%%.*}"
+    patch -p1 -i "$srcdir/masterpdfeditor.sh.patch"
+}

 package() {
   depends=('gcc-libs' 'glibc' 'libgl' 'nspr' 'nss' 'qt5-base' 'qt5-svg' 'sane')
@@ -21,7 +26,7 @@ package() {
   cp -a --no-preserve=ownership master-pdf-editor-${pkgver%%.*} "$pkgdir/opt/"

   cd "$pkgdir/opt/master-pdf-editor-${pkgver%%.*}"
-  ln -sr masterpdfeditor${pkgver%%.*} -t "$pkgdir/usr/bin/"
+  ln -sr masterpdfeditor${pkgver%%.*}.sh "$pkgdir/usr/bin/masterpdfeditor${pkgver%%.*}"
   install -Dm644 masterpdfeditor${pkgver%%.*}.desktop -t "$pkgdir/usr/share/applications/"
   install -Dm644 license.txt -t "$pkgdir/usr/share/licenses/$pkgname/"
   patchelf --remove-rpath masterpdfeditor${pkgver%%.*}
diff --git a/masterpdfeditor.sh.patch b/masterpdfeditor.sh.patch
new file mode 100644
index 0000000..7a31742
--- /dev/null
+++ b/masterpdfeditor.sh.patch
@@ -0,0 +1,12 @@
+--- a/masterpdfeditor5.sh  2020-03-27 10:57:36.818464325 +0100
++++ b/masterpdfeditor5.sh  2020-03-27 10:58:22.561935668 +0100
+@@ -1,7 +1,7 @@
+ #!/bin/sh
+  appname=`basename $0 | sed s,\.sh$,,`
+- libpath=$(cd "$(dirname "$0")"; pwd)
+- dirname=`dirname $0`
++ libpath="$(cd $(dirname "$(readlink -f "$0")"); pwd)"
++ dirname="$libpath"
+  tmp="${dirname#?}"
+  
+  if [ "${dirname%$tmp}" != "/" ]; then

@unixtastic Did you read what's below your comment ? Everything is explained. 1. remove Aur version 2. download the "all" version from Code Industry 3. Install it 4. run /opt/master-pdf-editor-5/masterpdfeditor5.sh 5. smile :)

This doesn't run.

• masterpdfeditor5: symbol lookup error: masterpdfeditor5: undefined symbol: _ZN10QMutexPool17globalInstanceGetEPKv

ldd doesn't show any missing libraries. The command mentioned below, /opt/master-pdf-editor-5/masterpdfeditor5.sh, doesn't exist.

@Chester A tar.gz file is just a compressed archive similar to a zip file, and it's universal across all linux platforms; i.e. there's nothing magic about installing it on Arch. Also note that this won't currently work unless you downloaded the "-all" version which includes the older Qt libraries. Here are the steps, which you'll need to run as root, and assuming you downloaded the masterpdfeditor5 tarball to /home/chester:

# cd /opt

# tar xvfp /home/chester/master-pdf-editor-5.4.38-qt5-all.amd64.tar.gz

# cd /usr/local/bin

• Now use your favorite text editor to create a shell script called masterpdfeditor5 with these contents: (You can skip this step if you only ever launch programs from the GUI)

#!/bin/sh

app_path="/opt/master-pdf-editor-5"

LD_LIBRARY_PATH=$app_path/lib:$app_path/platforms:$app_path/printsupport:$app_path/iconengines:$app_path/imageformats:$app_path/platformthemes:$LD_LIBRARY_PATH

export LD_LIBRARY_PATH

$app_path/masterpdfeditor5 "$@"

Finally,

# cp /opt/master-pdf-editor-5/masterpdfeditor5.desktop /usr/share/applications

# chmod 644 /usr/share/applications/masterpdfeditor5.desktop

If you uninstalled the AUR package using pacman -Rns you will probably have unmet dependencies. I had to install the sane package; you might run into other unmet dependencies. Warning: generally installing from tarball is something that should be left to those with a fair level of linux expertise -- a typo could screw up your system. Also if you go back to using the AUR package, you'll need to clean up after yourself by hand; i.e. remove everything you've created in the previous steps.