[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream

2024-05-31 Thread Launchpad Bug Tracker
[Expired for pdfarranger (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pdfarranger (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream

2024-04-01 Thread Fabio M. Panico
UPGRADE pdfarranger via SNAP: I'm on Ubuntu 22.04.04 and I was facing the same issue, having installed pdfarranger 1.8.2 via command line apt install. Removing it (with sudo apt remove --purge pdfarranger) and reinstalling via snap (sudo snap install pdfarranger) I got version 1.10.1 and fixed

[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream

2024-03-17 Thread Sudip Mukherjee
Thanks for the information Jens. You have pikepdf installed via pip which is causing the problem. I can now reproduce the same problem you have and the same version as your is now showing in my "About" box. All I had to do was: sudo pip install pikepdf==8.10.1 Please use the command "pip list"

[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream

2024-03-16 Thread Jens
First and foremost, thank you for your support! I think I have found the root issue, but I have no idea how I got here. Probably a manuall installation of some other tool via "pip install"? $ sudo find / -name "libqpdf*.so*" 2>/dev/null [sudo] password for jens:

[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream

2024-03-15 Thread Sudip Mukherjee
I have been trying to reproduce the issue on Jammy and I could not. And, I also checked for libqpdf, 11.6.4 has never been in Jammy. Lets chech few things, pdfarranger depends pikepdf. Can you please run these 2 commands and paste the output: 1. sudo find / -name "libqpdf*.so*" 2>/dev/null 2.

[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream

2024-03-15 Thread Fabio M. Panico
Hi, I would like to say that I'm facing the same problem. Hope it's ok to add this comment into this bug report. I recently made a fresh install of ubuntu 22.04-04. And when trying to combine 2 pdfs, PDF-Arranger gives me this error: "use pikepdf.PDF.pages interface to copy pages from one PDF

[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream

2024-03-14 Thread Jens
Actually, I was mistaken. Sorry for the confusion, this was a typo. I do have pdfarranger 1.8.2 (one eight two) installed, but (!) built against libqpdf 11.6.4, it seems. See attached image. I also have libqpdf 10.6.3-1 installed as a package from Jammy. So why is my pdfarranger (incorrectly)

[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream

2024-03-14 Thread Sudip Mukherjee
Thanks for the information. So, it seems you have pdfarranger from somewhere else other than Ubuntu sources. You can see at https://launchpad.net/ubuntu/+source/pdfarranger that Jammy has pdfarranger 1.8.2. I also tested on my Jammy and attaching the screenshot of the "About" for your

[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream

2024-03-13 Thread Jens
Hello, "apt policy libqpdf28" shows me version 10.6.3-1 from archive.ubuntu.com, I have nothing else installed. The "About" page in PDFarranger 1.9.2 shows it was built with libqpdf 11.6.4, GTK 3.24.33 and Python 3.10.12. Is this statically linked? Thanks, Jens -- You received this bug

[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream

2024-03-13 Thread Sudip Mukherjee
Thanks for reporting the bug. I am seeing the only libqpdf available in Jammy is "libqdf28" which has a version of "10.6.3-1". There is no "libqpdf 11.6.4" in Jammy. Can you please check and confirm if you have installed libqpdf 11.6.4 from some other source. I am marking this bug as