You are here

PDF Arranger crash on startup

9 posts / 0 new
Last post
g-npho
Offline
Last seen: 1 year 2 months ago
Joined: 2009-01-24 10:02
PDF Arranger crash on startup

Hello all,
When starting PDF Arranger after first installation and startup it throws the following:
cx_freeze: Python error in main script
Traceback (most recent call last): file
Z:\mingw64\lib\python3.9\site-packages\pikepdf\__init__.py, line 13, in
Import error: DLL load failed while importing _qpdf: Die angegebene Prozedur wurde nicht gefunden. (The called procedure was not found.)

This happens on two different machines in standard installation path (C:\PortableApps\PDFArrangerPortable\PDFArrangerPortable.exe)
running on Windows 10 x64 22H2 German edition (Version 10.0.19045.2251).
Greetings, g_npho

John T. Haller
John T. Haller's picture
Online
Last seen: 5 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
German

Are you running the app directly or via the PA.c Platform? I'll see if I can get my VM configured for German to see if that's playing a role, too, as I think the app tries to match the OS.

Also, as a test, would you please try running the app directly in local mode by browsing to PDFArrangerPortable\App\PDFArranger and running pdfarranger.exe to see if the error occurs there as well?

Sometimes, the impossible can become possible, if you're awesome!

g-npho
Offline
Last seen: 1 year 2 months ago
Joined: 2009-01-24 10:02
Hello John,

Hello John,
the result is the same whether I run the app from PortableApps loader or calling from an explorer window. I use to call the apps from an icon on the taskbar of Total Commander (Ghisler), and the result is the same there.
And if I change the language of PortableApps to English for all apps it does not change.
Greetings, Gerhard

John T. Haller
John T. Haller's picture
Online
Last seen: 5 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Run Directly?

Did you try to run the app directly bypassing everything else as I mentioned above? This would mean not running PDFArrangerPortable.exe but running the app itself in local mode.

Sometimes, the impossible can become possible, if you're awesome!

g-npho
Offline
Last seen: 1 year 2 months ago
Joined: 2009-01-24 10:02
Sorry, I didn' follow your

Sorry, I didn' follow your explanation !
When starting the app in local mode as you mentioned it works. Also, on a third computer running Windows 10 x64 22H2 the behavior is like on the other two.
Greetings, Gerhard

g-npho
Offline
Last seen: 1 year 2 months ago
Joined: 2009-01-24 10:02
I just tried under Wine on

I just tried under Wine on Manjaro (German language version, rolling release, updated). It opens up as it is supposed to, but then freezes. On opening document or on just staying open.
Greetings, Gerhard

John T. Haller
John T. Haller's picture
Online
Last seen: 5 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Working Here

I switched one of my virtual machines to German. It's running Windows 10 Pro x64, 22H2 19045.2251. I installed PDF Arranger to C:\PortableApps\PDFArrangerPortable. It started up without issue in German. So, this is something specific to your PC.

Please try opening up the file C:\PortableApps\PDFArrangerPortable\App\AppInfo\Launcher\PDFArrangerPortable.ini in your favorite text editor. Create a new line after the ProgramExecutable=PDFArranger\pdfarranger.exe line as follows:

WorkingDirectory=%PAL:AppDir%\PDFArranger

Then save the file. Try running it again.

Sometimes, the impossible can become possible, if you're awesome!

g-npho
Offline
Last seen: 1 year 2 months ago
Joined: 2009-01-24 10:02
Hello John,

Hello John,
this does the job ! on all my machines.
The file now looks like

[Launch]
ProgramExecutable=PDFArranger\pdfarranger.exe
WorkingDirectory=%PAL:AppDir%\PDFArranger
DirectoryMoveOK=yes
SupportsUNC=yes

[FilesMove]
config.ini=%PAL:AppDir%\PDFArranger

The only question is why this is so.
Greetings and thanks,
Gerhard

John T. Haller
John T. Haller's picture
Online
Last seen: 5 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
PATH remnants

I'd wager there are some Python remnants in your Windows PATH environment variable that are interfering. Maybe an incompatible or incomplete install. Setting the working directory ensures that the app looks there first for stuff. This setting will be included in subsequent releases for folks with similar setups.

Sometimes, the impossible can become possible, if you're awesome!

Log in or register to post comments