Package Details: pdfstudio-bin 2022.0.1-1

Git Clone URL: (read-only, click to copy)
Package Base: pdfstudio-bin
Description: Review, annotate, and edit PDF Documents
Upstream URL:
Licenses: custom
Conflicts: pdfstudio
Provides: pdfstudio
Replaces: pdfstudio
Submitter: alerque
Maintainer: alerque (flamusdiu, simonzack)
Last Packager: simonzack
Votes: 32
Popularity: 0.125871
First Submitted: 2020-04-10 22:40 (UTC)
Last Updated: 2022-06-21 12:27 (UTC)

Dependencies (1)

Required by (0)

Sources (3)

Latest Comments

mamauriz commented on 2022-07-02 07:51 (UTC)

OK, now it works .. thanks very much

simonzack commented on 2022-07-01 15:49 (UTC) (edited on 2022-07-01 15:51 (UTC) by simonzack)

@mamauriz If you want to run it with the latest JRE, comment out these lines in /usr/bin/pdfstudio:

  # if [ "$ver_major" -gt "17" ]; then
  #   return;
  # fi

mamauriz commented on 2022-07-01 15:29 (UTC) (edited on 2022-07-01 15:33 (UTC) by mamauriz)

hi everyone, when i launch pdfstudio i answer this.

[mauri@ChZh ~]$ pdfstudio

No suitable Java Virtual Machine could be found on your system. The version of the JVM must be at least 1.8 and at most 17. Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.

java --version

openjdk 2022-04-22 OpenJDK Runtime Environment (build OpenJDK 64-Bit Server VM (build, mixed mode)

thank you

simonzack commented on 2022-06-19 08:11 (UTC)

The latest release officially uses JRE 17. It works with the latest JRE 18.

simonzack commented on 2022-04-15 06:57 (UTC)

@Iawa42 Good point. An easier way is to just modify pdfstudio.desktop to say something like:

Exec=INSTALL4J_JAVA_HOME_OVERRIDE=/usr/lib/jvm/java-11-openjdk/bin/ pdfstudio %f

I'm not really sure what I can do here to modify the package, as people can choose different versions of JRE.

lawa42 commented on 2022-04-11 14:33 (UTC)

Does not work with the new (default) java-18. Can be fixed in the first line of the shell script by providing the correct path to the (required) jre17-openjdk (or older)

wolfyrion commented on 2022-03-14 11:10 (UTC)

Just posting my solution if for some people is not working...

If I install google-fonts from AUR

somehow pdfstudio is not working but if I install adobe-source-code-pro-fonts and remove google-fonts from AUR it works

simonzack commented on 2021-12-10 13:43 (UTC) (edited on 2021-12-10 13:43 (UTC) by simonzack)

@TomZander Good point. -XX:+UseConcMarkSweepGC is pretty ancient. Now this line is automatically commented out in the PKGBUILD.

TomZander commented on 2021-12-09 19:12 (UTC)

@simonzack thank you for your answer. I indeed missed that comment.

I would argue that suggesting people change a system file is not the solution, though. Its a rather advanced work-around.

What about making sure that the default install doesn't have this line there? Because the default JVM doesn't accept it (anything later then 14 will fail with the defaults today).

I would guess a simple patch can be applied to comment out the line. That would actually solve it for new users.

simonzack commented on 2021-12-09 10:53 (UTC)

@TomZander Read the pinned comment, to comment out -XX:+UseConcMarkSweepGC in /usr/share/pdfstudio/pdfstudio2021.vmoptions.

TomZander commented on 2021-12-09 10:51 (UTC)

Starting this with the arch standard 'jre-openjdk' gives me an error on startup;

$ pdfstudio
Unrecognized VM option 'UseConcMarkSweepGC'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

At the time of writing the above package gives one version 17.0.1.u12-1.

alerque commented on 2021-07-06 15:36 (UTC)

@simonzack Good catch, now fixed.

simonzack commented on 2021-07-04 09:50 (UTC)

The pdfstudio.desktop file still shows "PDF Studio 2019" instead of "PDF Studio 2021". Can this be updated? Thanks.

alerque commented on 2021-07-02 18:44 (UTC)

@flamusdiu This package is always expected to be the latest stable. People can cap their system at a certain version if that's what they want. Additionally package to facilitate patches to old packages or new installs of old versions can be made as pdfstudio-binN, but that's up to somebody else that wants them. They can be made from checking out an old commit from this package, but we don't have to create them in order to bump this one.

Also I don't see i686 builds any more so I've gone ahead with just the x86_64 build update. If they ever post binaries for old platforms we cat adjust, but again there is no reason to hold back the package for that.

flamusdiu commented on 2021-07-02 17:27 (UTC)

@simonzack: nice find. I'll have to move the install to another package then update this one so those who do not want to install the newest version can fall back to that one.

I'll see what I can do about that if I get a chance soon. Being an adult sucks sometimes. ;)

simonzack commented on 2021-07-02 17:05 (UTC) (edited on 2021-07-07 01:41 (UTC) by simonzack)

I've also emailed PDF Studio to have them put the .deb link at the same place as before. So now if you just change:


everything should work fine. I don't think there's a x86 package anymore.

yochananmarqos commented on 2021-07-02 16:59 (UTC)

A new .deb link is up, see

simonzack commented on 2021-07-01 16:52 (UTC)

@caleb I emailed PDF Studio, who did give me a .deb link, but said "we are not publishing this publically yet". I'm hoping they publish it publicly soon.

alerque commented on 2021-06-26 17:44 (UTC)

@gr211 Thanks, but I looked through that script and decided it was so intrusive I didn't even want to risk running it as a test except in a disposable container of some kind. If it comes down to that being the only way to package this I'll probably take my name off and walk away.

For now if people really trust the upstream with their system I guess folk are welcome to run that snippet themselves. Packaging it doesn't do much at that point if you've let the script have the run of your system!

gr211 commented on 2021-06-26 16:49 (UTC) (edited on 2021-06-26 16:50 (UTC) by gr211)

obviously not ideal, but the pkgbuild could do something like

bash -q -dir ${pkgdir}/pdfstudio2021/

flamusdiu commented on 2021-06-25 13:29 (UTC)

Yeah, they change the URLs sometimes. I'll see if I can locate it again.

alerque commented on 2021-06-25 11:58 (UTC) (edited on 2021-06-25 13:50 (UTC) by alerque)

@simonzack et all, I'll be happy to update this when somebody finds a directly link to the *.deb download upstream. So far I only see the self installing java/gz/shell blob monstrosity version for download and I couldn't guess the right URL for a cleaner download.

Anonymo commented on 2021-03-19 18:18 (UTC)

New version seems to work with -XX:+UseConcMarkSweepGC" commented out again.

gr211 commented on 2021-01-28 13:38 (UTC) (edited on 2021-01-29 23:00 (UTC) by gr211)

Thanks for packaging this application. Tiny typo here It reads 2019 when it should be 2020. Thx!

alphazo commented on 2021-01-15 08:35 (UTC)

Thanks a lot @yangtsesu ! Commenting "-XX:+UseConcMarkSweepGC" in /usr/share/pdfstudio/pdfstudio2020.vmoptions made pdfstudio to work with Java runtime 15.

yangtsesu commented on 2021-01-14 14:29 (UTC)

@alphazo Remove -XX:+UseConcMarkSweepGC from pdfstudio2020.vmoptions

flamusdiu commented on 2021-01-13 13:14 (UTC)

@alphazo: can you DM me on twitter at @azuleonyx? I do not have the older version of the software and I think they might have broken all the DL links without manually downloading the software with a valid key.

flamusdiu commented on 2021-01-12 14:18 (UTC)

@alphazo: looks like I probably need to check on that.

flamusdiu commented on 2021-01-12 14:18 (UTC)

Oops, I apparently forgot to create a v19 package as I did all the other major versions.

alphazo commented on 2021-01-12 10:58 (UTC)

Recent update of Java runtime (jre/jdk) to version 15 prevents pdfstudio to start. I had to downgrade jre/jdk to version 14 in order to get pdfstudio to work again.

Anonymo commented on 2020-11-23 23:12 (UTC)

@josete check out the coming soon:

josete commented on 2020-10-27 18:51 (UTC)

It's a good suggestion but then I would simply be postponing the problem. If a new program is released in 2021, it will obviously have a different license so it will require a different package. I have already tried the 2020 version and it has a problem with HDPI resolutions. They say they know this happens with some Desktop Enviroments. Mine is KDE. I prefer to wait for a version where the problem with HDPI is completely solved. In the meantime I will have to keep seeing messages that I have pending updates knowing that it is not true. Greetings and thanks again!

Anonymo commented on 2020-10-27 17:30 (UTC)

@josete I recommend upgrading. the 2020 version is so much better and the upgrade is like $40, I think. They had a special going on when I bought it.

josete commented on 2020-10-21 11:22 (UTC)

Great! It's an advance, far from being a perfect solution, but it's something. The system still indicates that there are updates when it's not true.

I humbly consider that all applications that handle licenses should split when the license refers to a different program. This is the way all other packages I have with licenses work (jriver-media-center, softmaker-office ...) I respect and admire a lot the job all mainteiners do so I just request this for a future consideration.


alerque commented on 2020-10-21 10:40 (UTC)

@josete Add it to your HoldPkg or IgnorePkg lists in /etc/pacman.conf.

josete commented on 2020-10-20 00:09 (UTC)

1) I unistalled the package I had in my system. It was installed with "yay -S ..." 2) I created the package following all the steps. Everything worked perfect. 3) I installed it again using sudo pacman -U pdfstudio... I thought this way my system wouldn't tell me I have an update but it keeps saying it. Is there any way to break this "link" between the package I have installed and the AUR updates? Now, every time I run "yay -Syu" I have to answer that I don't want this update. Greetings!

josete commented on 2020-10-19 20:46 (UTC)

Great! Thanks a lot. I'll try it.

BTW, I install AUR applications with: yay -S package_name That's why I didn't know anything about git, clone, makepkg ...

Thanks again!

alerque commented on 2020-10-19 07:18 (UTC)

@josete: There is only one step different from a manual AUR installation. You clone the repository, enter it (same so far), then checkout the revision you want to build (this step is different, the 0f0cf1f commit I looked up in "view changes" from this page as the last 2019 revision), then build and install as usual.

$ git clone
$ cd pdfstudio-bin
$ git checkout 0f0cf1f
$ makepkg -i

josete commented on 2020-10-17 13:19 (UTC)

I'm afraid I have no idea how to do anything of that.

alerque commented on 2020-10-09 08:07 (UTC)

@josete The packaging is a Git repository with full history. Just use the URL at the top of the page to clone this, then git checkout whichever commit has the version you want to build, then run makepkg. This package already has a long tail of split off AUR packages for many versions along the way and I think catering to that licensing issue is crazy. If you don't have a license and don't want to use just the free parts don't upgrade the package past the version you want to use. One you build the version you want, you can pass around the built packages to your other machines to save the trouble building the right one.

josete commented on 2020-10-09 07:09 (UTC)

In my humble opinion there should be 2 different packages, one for version 19 and one for version 20. I have a license for PDF Studio Pro 19 but not for the new one. My system keeps saying I have 1 update available and that's not true.

yochananmarqos commented on 2020-10-07 15:43 (UTC) (edited on 2020-10-07 15:43 (UTC) by yochananmarqos)

@caleb: You make a valid argument. Point taken.

See Nonfree applications package guidelines:

Use the suffix -bin always unless you are sure there will never be a source-based package

In this case I'm pretty sure it's safe to say there will never be a source-based package, but there's nothing wrong with using the -bin suffix.

alerque commented on 2020-10-07 09:46 (UTC)

@yochananmarqos I actually really dislike that Arch packaging guidelines allow binary packages without -bin; I prefer to know up front when I search the AUR using yay --aur -Ss or similar tools whether a package I see is going to be a source build or an upstream binary. Last I checked the Arch guidelines allowed using -bin suffixes for these kind of things even if the sources was not available, it just doesn't require the -bin designation. Is that not still the case?

yochananmarqos commented on 2020-10-06 00:28 (UTC)

This should be called pdfstudio as there is no source code available; therefore no -bin designation is required.

Anonymo commented on 2020-10-06 00:15 (UTC)

Any way to use this app with the newest java without the top bar disappearing?

alerque commented on 2020-04-29 08:49 (UTC) (edited on 2020-04-29 08:51 (UTC) by alerque)

@Anonymo Please see the pinned comment, this package is obsolete and will not be updated (in fact it's scheduled for merger into the correct current package). I have bumped the pdfstudio-bin package to the latest release. Please feel free to flag that package as out of date in the future when you see *nix releases are available upstream. Thanks for the heads up.

Anonymo commented on 2020-04-28 15:17 (UTC)

2019.2.2 – April 27 2020 (macOS, Linux, Unix), Coming Soon (Windows) is out. Before Windows. LOL

alerque commented on 2020-04-24 22:10 (UTC)

@Anonymo This isn't out of date yet. The changelog link you sent says "coming soon" and the binary build files aren't posted yet. Please flag whet it's actually out.

baatochan commented on 2020-04-14 09:40 (UTC)

Thanks, gonna change.

Just a note, the link you put is incorrect and goes to this package.

The correct link is here.

alerque commented on 2020-04-14 08:38 (UTC) (edited on 2020-04-24 22:11 (UTC) by alerque)

@baatochan and other flaggers, this package is obsolete. The correct package name is pdfstudio-bin and this will be updated there. A merge is in progress to merge the two packages together, but you can start using the correctly named one now.

bennypr0fane commented on 2020-03-27 21:08 (UTC)

The .deb package that this downloads is v 19.2.1-1 and SHAsum is 73197a7caf6dcfe503ee7a4af0737b16c8cb24803b4b363d989bd2f8751c3029 Can we get the version number changed in the title (I don't know how to do this)?

petaramesh commented on 2020-03-25 10:11 (UTC)

Hello, x64 SHA256SUM is outdated and needs to be updated.

Anonymo commented on 2020-03-09 15:59 (UTC)

@j1simon just make your own package with another name like pdfstudio-current or something and stop trying to call out people who volunteer their time when they can. The package is easily update-able thanks to flamusdiu good work with the PKGBUILD. Plus I've been posting updated PKGBUILDS when I can.

j1simon commented on 2020-02-28 10:34 (UTC)

@flamusdiu If you can't keep this package up to date, it's better to give it up for someone else to adopt.

Anonymo commented on 2020-01-23 17:57 (UTC) 19.2.1

Anonymo commented on 2020-01-22 17:39 (UTC)

Not abandoned. Just not updated. There is a package you can use below. It can also be built by updating sha256sums and the version numbers to the version numbers found in the changelog linked in the pinned message. There is a new version coming soon according to the changelog.

josete commented on 2020-01-19 19:46 (UTC)

Is this package abandoned? It's flagged out-of-date for more than a month. Greetings!

Anonymo commented on 2019-12-06 19:05 (UTC)

baatochan commented on 2019-12-03 11:54 (UTC)

As for today (2019-12-03) you need to edit the PKGBUILD line sha256sums_x86_64 to sha256sums_x86_64=('4c78ead39e30ec72694318ee085945515473c317032ece076a4fc0daa3265ef2').

(for x64 package, don't know the 32bit package sum)

FXOjafar commented on 2019-12-03 05:21 (UTC) (edited on 2019-12-03 05:22 (UTC) by FXOjafar)

Hi. The latest version 19.1.4-1 fails validity check.

:: Parsing SRCINFO (1/1): pdfstudio
==> Making package: pdfstudio 19.1.4-1 (Tue 03 Dec 2019 13:19:17 AWST)
==> Retrieving sources...
-> Found pdfstudio.desktop
-> Found pdfstudio.install
-> Found pdfstudio.png
-> Found PDFStudio_linux64.deb
==> Validating source files with sha256sums...
pdfstudio.desktop ... Passed
pdfstudio.install ... Passed
pdfstudio.png ... Passed
==> Validating source_x86_64 files with sha256sums...
PDFStudio_linux64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: pdfstudio

dhux commented on 2019-06-11 02:33 (UTC)

FYI, I changed my java environment to 8 from 10 (archlinux-java set java-8-openjdk) and the program works as it should.

Thanks for maintaining this program. I use this every day at work. Much appreciated!

flamusdiu commented on 2019-06-05 15:49 (UTC)

hmm, I'll have to try and build it with java engine shipped with it. I strip it out so it uses the one installed but that might not been wise in the current versions.

Anonymo commented on 2019-06-05 14:04 (UTC) (edited on 2019-06-05 14:04 (UTC) by Anonymo)

@dhux @wolfyrion Try disabling

export _JAVA_OPTIONS='-Dsun.java2d.opengl=true' in /etc/profile.d/

I think it's a java issue

dhux commented on 2019-06-05 13:51 (UTC)

I'm seeing the same issue with V19 as wolfyrion with the invisible menus until rolling the mouse over them.

wolfyrion commented on 2019-06-05 08:21 (UTC)

Thanks for v19 but it seems to be buggy on my pc. Whenever I click on menus, menus dont appear and I have to roll over my mouse in order to show the menus.

flamusdiu commented on 2019-06-04 20:59 (UTC)

Added v18 package:

flamusdiu commented on 2019-06-04 17:38 (UTC)

@Anonmyo: FFS, let me update a few things and put up a v19 package. I just realized they jumped the version again after you posted the sums.

Anonymo commented on 2019-06-04 15:04 (UTC)

v18 links and sums





Anonymo commented on 2019-05-29 15:25 (UTC) (edited on 2019-05-30 15:52 (UTC) by Anonymo)

Here is a PKGBUILD that works with by changing 2018 to 2019 and updating the sha256sums. Have not tested, since I don't have the 2019 license yet but I ran makepkg and there were not errors. I'm sorry for not sending a PR but I haven't made the time to learn to use GIT

v19.0.0 sha256sums



gir861 commented on 2019-05-29 08:56 (UTC)

Not installing with Anonymo's recommendation.

flamusdiu commented on 2019-04-25 00:56 (UTC)

@antonjo: it's the trial/paid editor. I can add a package for the viewer. It shouldn't be much different from this one.

antonjo commented on 2019-04-21 17:00 (UTC)

is this the free viewer or trial editor?

ilinojkovic commented on 2019-04-05 08:20 (UTC)

Hi, previous @Anonymo's comment helped me install the program, however, I have now problem to start it. On my machine I have OpenJDK 11 installed, however, PDFStudio complains and is looking for JVM 1.8. Shouldn't the version 11 be backwards compatible, and is the problem with PDFStudio or with java itself? Anyone having similar issues? How to bypass this? Thanks!

wolfyrion commented on 2019-04-02 14:48 (UTC)

==> Validating source files with sha256sums... pdfstudio.desktop ... Passed pdfstudio.install ... Passed pdfstudio.png ... Passed ==> Validating source_x86_64 files with sha256sums... PDFStudio_linux64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check!

dschrempf commented on 2019-03-15 14:15 (UTC)

The sha256sum seems to be outdated again!

8398f016fb391422af2b96e428609627047f49c8b11df9a6d8dcaf8ba87370ef PDFStudio_linux64.deb

pkgbuild has ad54e71c40c1748fae20f1b8bead03a340a77aa1c8eba1a7a1389cdbea681520

a821 commented on 2019-02-14 21:32 (UTC)

@boustanihani there's a new version (2018.3.0) (*) with sha256sum (x86_64) ad54e71c40c1748fae20f1b8bead03a340a77aa1c8eba1a7a1389cdbea681520. You need to update the PKGBUILD.

(*) just download the deb file and unpacked it. Then look at the file control inside control.tar.gz.

boustanihani commented on 2019-02-12 12:01 (UTC) (edited on 2019-02-12 12:01 (UTC) by boustanihani)

I was having a similar checksum error with "freefilesync" but managed to install after cleaning and retrying for 6 times. This is crazy, why is this happening :(

I am still not able to install "pdfstudio 18.2.2-1", checksum error persists...

"sha256sums" error for "PDFStudio_linux64.deb"

Anonymo commented on 2019-01-22 16:54 (UTC) (edited on 2019-01-22 16:58 (UTC) by Anonymo)

Don't know what to tell you. Got to not use your AUR builder. Use makepkg -ics when that fails. The PKGBUILD is working, everything is correct. You must not be clearing some cache.

boustanihani commented on 2019-01-22 11:48 (UTC)

I also wiped my AUR builder cache and still getting the validity check error.

boustanihani commented on 2019-01-22 11:43 (UTC)

Getting the following error for the last version:

==> Überprüfe source_x86_64 Dateien mit sha256sums... PDFStudio_linux64.deb ... FEHLGESCHLAGEN ==> FEHLER: Eine oder mehrere Dateien überstanden nicht die Gültigkeits-Prüfung!

Anonymo commented on 2019-01-20 16:32 (UTC) (edited on 2019-01-20 16:32 (UTC) by Anonymo)

@Drew You have to make sure you wipe your AUR builder cache or have tried a makepkg -ics before you post that there is a validity check. It built fine for me.

Drew commented on 2019-01-18 04:02 (UTC)

==> Validating source_x86_64 files with sha256sums...
    PDFStudio_linux64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!

flamusdiu commented on 2018-12-16 14:01 (UTC)

Looks like the version got updated to 18.2.1. I'll get it updated.

dreieck commented on 2018-12-16 13:13 (UTC)

Checksum mismatch:

==> Validating source_x86_64 files with sha256sums...
    PDFStudio_linux64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!

bigred commented on 2018-11-14 14:07 (UTC)

The sha256 Sums are out of date, both for x64 and i686 versions

mahi commented on 2018-06-26 18:29 (UTC)

I could install pdfstudio when I modified PKGBUILD according JanusDC.

The link in /usr/bin was wrong and I had to correct it: sudo ln -s /opt/pdfstudio2018/pdfstudio2018 /usr/bin/pdfstudio

flamusdiu commented on 2018-06-24 21:38 (UTC)

Oops. I will get fixed.

JanusDC commented on 2018-06-23 13:18 (UTC) (edited on 2018-06-23 13:18 (UTC) by JanusDC)

The PKGBUILD has a typo. To fix it, you need to change:

    bsdtar xf "opt/pdfstudio/lib/pdfstudio.jar" resources/license.html

    rm -rf "opt/pdfstudio/jre"


    bsdtar xf "opt/pdfstudio2018/lib/pdfstudio.jar" resources/license.html

    rm -rf "opt/pdfstudio2018/jre"

cfr42 commented on 2018-06-22 22:34 (UTC) (edited on 2018-06-22 22:36 (UTC) by cfr42)

Complete output from makepkg:


==> Making package: pdfstudio 18.0.0-1 (Dydd Gwener 22 mis Mehefin 2018 23:34:16 BST)

==> Checking runtime dependencies...

==> Checking buildtime dependencies...

==> Retrieving sources...

-> Found pdfstudio.desktop

-> Found pdfstudio.install

-> Found pdfstudio.png

-> Found PDFStudio_linux64.deb

==> Validating source files with sha256sums...

pdfstudio.desktop ... Passed

pdfstudio.install ... Passed

pdfstudio.png ... Passed

==> Validating source_x86_64 files with sha256sums...

PDFStudio_linux64.deb ... Passed

==> Extracting sources...

-> Extracting PDFStudio_linux64.deb with bsdtar

==> Starting prepare()...

bsdtar: Error opening archive: Failed to open 'opt/pdfstudio/lib/pdfstudio.jar' ==> ERROR: A failure occurred in prepare().


alex.forencich commented on 2018-06-21 00:36 (UTC)

Package is broken, fails to build with:

bsdtar: Error opening archive: Failed to open 'opt/pdfstudio/lib/pdfstudio.jar'

mahi commented on 2018-06-19 19:24 (UTC)

I can not install pdfstudio. I tried to install it on 2 different computers and I always get this failure message: bsdtar: Error opening archive: Failed to open 'opt/pdfstudio/lib/pdfstudio.jar'

Anonymo commented on 2018-06-12 16:37 (UTC) (edited on 2021-09-08 23:36 (UTC) by Anonymo)

If anyone has java heap size error when doing OCR, check this:

Adding export _JAVA_OPTIONS='-Dsun.java2d.opengl=true'

to /etc/profile.d/ makes the PDFs load so much faster.

checksum errors: Check for recent updates to the program in changelog:

Commenting "-XX:+UseConcMarkSweepGC" in /usr/share/pdfstudio/pdfstudio2021.vmoptions made pdfstudio to work with Java runtime 15.

flamusdiu commented on 2018-06-09 08:30 (UTC)

Woops, How the heck did I miss that. =P

NoobAlice commented on 2018-06-08 22:12 (UTC) (edited on 2018-06-08 22:14 (UTC) by NoobAlice)

@flamusdiu: Try

It's linked under "Linux AMD 64 Instructions" in the text

"To install PDF Studio on multiple computers through command-line, you may use our 64 bit Debian package (right-click and save link as) . This package will install PDF Studio in the “/opt” directory."

below the rest of the regular downloads on page

flamusdiu commented on 2018-06-08 21:40 (UTC)

Okay, might take me a while to update this unless someone can post the .deb URLs. I need to locate the download files.

flamusdiu commented on 2018-06-08 11:00 (UTC)

I will be updating this package to v18 so be on the lookout for the older package when I migrate it over. Thanks!

hogar1977 commented on 2017-10-04 09:05 (UTC) (edited on 2017-10-04 09:07 (UTC) by hogar1977)

Agreed, please update to version 12.0.3 if possible... Besides this, with the current 12.0.0. version I experience a strange behavior for which I don't know if it's normal... Clicking on 'Open File' icon nothing happens, no dialog opens, it is only possible to click on a drop down button which offers recently opened files. I'm able to open a document from Nautilus file manager, but not from the application itself?! And furthermore, clicking on Document -> Rearrange pages -> Insert page gives me 'No document open' warning which is normal if I don't have a file open, but if I do open a file and perform the same action absolutely nothing happens and no dialog opens and it is not possible to insert a page from another pdf document for example?! Can anyone reproduce the same behavior? I'm using GTK+ look and feel because of Gnome DE and HiDPI...

n.vaughan commented on 2017-10-03 16:48 (UTC)

Hi, please update to use:

flamusdiu commented on 2017-06-19 03:09 (UTC)

Fixed now. I incorrectly assigned the wrong value to one of the vars in the PKGBUILD.

seblu commented on 2017-06-18 21:22 (UTC)

it's not working. sha256sums are invalid. When sums are fixed ==> Extracting sources... ==> Starting prepare()... bsdtar: Error opening archive: Failed to open 'data.tar.gz'

dhux commented on 2017-06-12 14:51 (UTC)

I really appreciate your time maintaining this. It's a great program, and I use it everyday at work. Thanks.

flamusdiu commented on 2017-06-12 13:55 (UTC)

dhux, I swear I uploaded properly. But, I notice and issue. I'll get it fixed later today.

dhux commented on 2017-06-12 12:19 (UTC)

I keep getting an error of: PDFStudio_v12.0.0_linux64.deb...FAILED did not pass the validity check

flamusdiu commented on 2017-06-07 11:21 (UTC)

Ooo...I'll have to update it and I'll check into gcc-libs-multilib as well.

Shaikh commented on 2017-06-07 06:18 (UTC)

v12 is out. And as @rgarcia mentioned, is 'gcc-libs-multilib' really necessary?

rgarcia commented on 2017-06-02 23:08 (UTC)

Is the dependency on gcc-libs-multilib really necessary given that there's a x86_64 upstream package? I've tested it locally and If I remove it on my x86_64 installation still works without having gcc-libs-multilib installed. If that is the case, could this package be updated to remove the supposed unnecessary dependency? Thanks

mani.zaeim commented on 2016-12-07 01:58 (UTC)

Fail on build, 404 / page not found curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading Aborting... ==> ERROR: Makepkg was unable to build pdfstudio.

sergey.orloff commented on 2016-11-08 16:40 (UTC)

11.0.1 versions of files are missing. For version 11.0.3 to fix these lines to the file. Thank you. PKGBUILD pkgver=11.0.3 _pkgver=v11_0_3 sha256sums_i686=('bc68e1a26be649e23f60898fe50d516bf4f472d7bae8cb3580a1329fee1b541f') sha256sums_x86_64=('ab19942604f29de120817a0ff68b0178eee576d83d83e42ff8cee3819510e2d6') .SRCINFO pkgver = 11.0.3 source_i686 = sha256sums_i686 = bc68e1a26be649e23f60898fe50d516bf4f472d7bae8cb3580a1329fee1b541f source_x86_64 = sha256sums_x86_64 = ab19942604f29de120817a0ff68b0178eee576d83d83e42ff8cee3819510e2d6

gjvnq commented on 2016-10-20 13:17 (UTC)

Patch for the new version: 4,5c4,5 < pkgver=11.0.1 < _pkgver=v11_0_1 --- > pkgver=11.0.3 > _pkgver=v11_0_3 22,23c22,23 < sha256sums_i686=('67d7fb962de2b7e6f6075c60ce213fbcaabbefea6e09613bce4649373b24a2e8') < sha256sums_x86_64=('e838fdcbbf1706b3148fb6f8168b8c615d9c897ef5ef17a73241bbe02f0ae226') --- > sha256sums_i686=('bc68e1a26be649e23f60898fe50d516bf4f472d7bae8cb3580a1329fee1b541f') > sha256sums_x86_64=('ab19942604f29de120817a0ff68b0178eee576d83d83e42ff8cee3819510e2d6')

flamusdiu commented on 2016-05-27 10:27 (UTC)

v10 moved =>

dhux commented on 2016-05-13 22:47 (UTC)

v11 is out.

flamusdiu commented on 2015-09-29 22:34 (UTC)

@rabarrett? This is v10 ... though just checked, I need to update it to 10.2. =P

rabarrett commented on 2015-09-29 18:18 (UTC)

v10 coming out soon?

flamusdiu commented on 2015-04-03 19:33 (UTC)

If you are looking for PDF Studio v9, please install this package: This one will be updated to v10 shortly.

flamusdiu commented on 2014-09-01 00:57 (UTC)

Another small change -- fixed depends.

flamusdiu commented on 2014-09-01 00:25 (UTC)

Fixed license install location.

flamusdiu commented on 2014-08-13 02:31 (UTC)

Fixed PKGBUILD to actually build for i686. Also, updated install file. Please note that you need to run "pdfstudio" instead of "pdfstudio9."

flamusdiu commented on 2014-07-20 14:02 (UTC)

If you are are looking for the legacy package (version 8), please look here: