Package Details: pdf-xchange 8.0.343.0-1

Git Clone URL: https://aur.archlinux.org/pdf-xchange.git (read-only, click to copy)
Package Base: pdf-xchange
Description: Feature-rich PDF editor/viewer. Create, view, edit and annotate plus much more.
Upstream URL: https://www.tracker-software.com/product/pdf-xchange-editor
Licenses: custom
Submitter: swearchnick
Maintainer: swearchnick
Last Packager: swearchnick
Votes: 18
Popularity: 0.004775
First Submitted: 2014-07-04 12:51
Last Updated: 2020-11-19 06:35

Dependencies (111)

Required by (0)

Sources (1)

Latest Comments

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

swearchnick commented on 2020-11-21 08:23

@bkb Can you please stop spamming (or are you trolling?). Your aur helper will never be supported. PKGBUILD shall never clear old files. It's your responsibility to do a clean build. This is my final warning to you regarding aur helper support.

bkb commented on 2020-11-20 10:12

After resolving the problem, it reoccurs after a new release

==> Making package: pdf-xchange 8.0.343.0-1 (ven. 20 nov. 2020 11:10:52)
==> Retrieving sources...
  -> Found EditorV8.x64.msi
==> Validating source files with sha256sums...
    EditorV8.x64.msi ... FAILED
==> ERROR: One or more files did not pass the validity check!
error downloading sources: pdf-xchange

After performing a new time rm -rf /home/$USER/.cache/yay/pdf-xchange the problem is a new time resolved. I will repeat myself but it's not normal and the PKGBUILD should clear old files itself like all others PKGBUILDs over here, anyway

swearchnick commented on 2020-10-13 05:35

@bbk It was clear from the beginning that you don't use aur as intended because you deliberately and repeatedly did not post complete error messages. Clear some AUR helpers cache in the installation script is just ridiculous. My advice to you is to ask for a refund.

bkb commented on 2020-10-12 17:52

If the maintainer was intelligent enough to perform a rm -rf /home/$USER/.cache/yay/pdf-xchange in the installation script automatically, any change in the package would not produce an error

Anyway

"blahblah not everyone use yay, blahblah AUR guidelines"

swearchnick commented on 2020-09-12 07:41

@bkb Checksum is ok and it builds just fine. Your problem is still the same as 2020-04-18 15:13. And again, please post complete error messages. "Full output of any command involved - don't just select what you think is relevant": https://bbs.archlinux.org/viewtopic.php?id=57855.

bkb commented on 2020-09-11 19:18

==> Making package: pdf-xchange 8.0.341.0-1 (fri. 11 sept. 2020 21:17:50)
==> Retrieving sources...
  -> Found EditorV8.x64.msi
==> Validating source files with sha256sums...
    EditorV8.x64.msi ... FAILED
==> ERROR: One or more files did not pass the validity check!
error downloading sources: pdf-xchange

micman commented on 2020-05-02 13:51

I use PCManFM and rarely Thunar on XFCE4. I have tried this last, but the problem persists. In the case this can be useful to understand something, this is the message received by winepath :

# winepath -s /home/linux_cheatsheet_by-RedHat.pdf
00d4:err:seh:setup_exception stack overflow 432 bytes in thread 00d4 eip 000000007bcbc023 esp 0000000000131460 stack 0x130000-0x131000-0x230000
/home/LINU~R3J.PDF

And this is the result when I launch pdf-xchange from the terminal:
# /usr/bin/pdf-xchange /home/linux_cheatsheet_by-RedHat.pdf
001b:err:ntoskrnl:ZwLoadDriver failed to create driver L"\Registry\Machine\System\CurrentControlSet\Services\wineusb": c0000142
000f:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 1114
0029:fixme:ntdll:server_ioctl_file Unsupported ioctl 24000 (device=2 access=1 func=0 method=0)
0029:fixme:ntdll:server_ioctl_file Unsupported ioctl 24000 (device=2 access=1 func=0 method=0)
002d:fixme:process:RegisterApplicationRestart (L"/Recover",0)
002d:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
002d:fixme:imm:ImmGetOpenStatus (00000000024DE320): semi-stub
002d:fixme:imm:ImmReleaseContext (0000000000010070, 00000000024DE320): stub
002f:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFFFFFFFFFA, 0000000004C6FDA0
002f:fixme:resource:GetGuiResources (0xffffffffffffffff,0): stub
002f:fixme:heap:RtlCompactHeap (0x10000, 0x0) stub
002d:fixme:nls:SetThreadPreferredUILanguages 8, 0x3a0e3d0, 0x22eb68
002d:fixme:msxml:domdoc_setProperty Ignoring property L"ProhibitDTD", value 0x22eb70 {VT_BOOL: ffffffff}
002d:fixme:msxml:domdoc_setProperty Ignoring property L"ProhibitDTD", value 0x22eb80 {VT_BOOL: ffffffff}
002d:fixme:font:GetCharacterPlacementW flags 0x0000003a ignored
002d:fixme:font:GetCharacterPlacementW flags 0x0000003a ignored
002d:fixme:font:GetCharacterPlacementW flags 0x0000003a ignored
...
002d:fixme:msg:ChangeWindowMessageFilter 4a 00000001
002d:fixme:msg:ChangeWindowMessageFilter c065 00000001
002d:fixme:msg:IsGUIThread 0: stub
002d:fixme:font:GetCharacterPlacementW flags 0x0000003a ignored
002d:fixme:font:GetCharacterPlacementW flags 0x0000003a ignored
002d:fixme:font:GetCharacterPlacementW flags 0x0000003a ignored
...
002d:fixme:win:RegisterTouchWindow (0x200c0 00000000): stub


It seems to me that the problem concerns the driver ("failed to create driver ").
In any case, thank you for the info.

swearchnick commented on 2020-05-02 07:28

@micman "winepath -s" is responsible for converting paths before using them with pdf-xchange. If you run winepath -s in the terminal, with your path as argument, you maybe can get a clue what is going on. I cannot reproduce the problem with the context menu, all documents I open this way works. I'm testing in nautilus (Files).

micman commented on 2020-05-01 17:54

When I try to launch a pdf file by the context menu from a file manager I receive this error message: "Cannot open the document. An error occured while opening a document from the file: Z:\run\media\STORAGE\UNIX\Kernel_Parameters_Command_Line.pdf Error [Operating system]: Invalid name." If I try to open it from PDF-XChange (Open>Browse>Path-to-the-File], it works. I think that the problem concerns the slashes of the path. They have not been converted from Windows () to Linux (/). My Wine version is wine 5.6-1. I have downgraded it after that the new version gave me this error message, but the problem persists. I have looked for the solution in the Wine forum, but I have not found it. Can someone help me?

bkb commented on 2020-04-18 16:00

It's not a "natural" way of doing things, this update should update this file aswell