Generally, if a Linux system offers to remove packages during your process, it means no other installed application needs them either.
All right, I admit that your conclusion was correct:
Therefore, to answer your question there isn’t any miracle that synaptic can do if PureOS current repository doesn’t contain latest …
@Ralf, this is the story you’d like to read before you proceed (with my last post proposal, I recommended to you, as there is no other way around to solve your expectations as of today): https://davetardon.wordpress.com/author/davetardon/.
Indeed. Please close this application (if it is not to late already) as is.
Yes, I closed it right away. If I cannot remove the package causing trouble by itself, I am not taking chances and removing whatever.
It is obvious that I have to update this libc6 version. Why does the newer version not simply install over the old as it is common with so many software packages?
Quarnero,
Will your suggestion above take care of the update of libc6?
What does the “bookworm” do? That is an intriguing name.
1 Like
The ‘babbling of a code monkey’ as David has titled it himself, is a little deep for me. I am a simple user, not a coder.
Besides, a code is defined as something the outsider does not understand. 
1 Like
Yes.
This is work-in-progress version for Debian 12. As today explained within our Forum:
David is author that created tool that you are about to install (current one, the version that is working under your Linux environment) and use: libetonyek, nothing less and nothing more. Just wanted to point out that myself is simple user of tools that other people make for us.
sudo apt install gcc-11-base locales libc-bin libc6 libstdc++6 libetonyek-0.1-1
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
libetonyek-0.1-1 is already the newest version (0.1.10-3).
libetonyek-0.1-1 set to manually installed.
The following additional packages will be installed:
libc-dev-bin libc6-dev
Suggested packages:
glibc-doc manpages-dev
Recommended packages:
manpages manpages-dev libc-devtools
The following packages will be upgraded:
gcc-11-base libc-bin libc-dev-bin libc6 libc6-dev libstdc++6 locales
7 upgraded, 0 newly installed, 0 to remove and XXXX not upgraded.
Need to get 11.1 MB of archives.
After this operation, 1,138 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://ftp.debian.org/debian bookworm/main amd64 libc6-dev amd64 2.33-5 [2,274 kB]
Get:2 https://ftp.debian.org/debian bookworm/main amd64 libc-dev-bin amd64 2.33-5 [243 kB]
Get:3 https://ftp.debian.org/debian bookworm/main amd64 libc6 amd64 2.33-5 [2,831 kB]
Get:4 https://ftp.debian.org/debian bookworm/main amd64 libc-bin amd64 2.33-5 [834 kB]
Get:5 https://ftp.debian.org/debian bookworm/main amd64 gcc-11-base amd64 11.2.0-14 [207 kB]
Get:6 https://ftp.debian.org/debian bookworm/main amd64 libstdc++6 amd64 11.2.0-14 [577 kB]
Get:7 https://ftp.debian.org/debian bookworm/main amd64 locales all 2.33-5 [4,088 kB]
Fetched 11.1 MB in 2s (6,390 kB/s)
Reading changelogs… Done
Preconfiguring packages …
In short, all of those 2.33-5 packages are needed to support libetonyek-0.1-1_0.1.10-3_amd64.deb package. PureOS repo current (as of now) version of very same packages is 2.31-13 and those are obsolete or rather not relevant any more to libetonyek-0.1-1_0.1.10-3 package, latest one (and the only one that is able to open .pages documents).
Quarnero,
I did the bookworm and restarted my computer, but the images are still not showing up in libre office.
I got the idea to check the properties of the image anchor.
It appears that libre office has the image but does not place it into the document. Maybe there is a libre office function I need to execute.
Below is the bookworm actions so you can check if it worked properly:
sudo nano /etc/apt/sources.list
[sudo] password for ralf:
ralf@ralf-macbookpro11:~/Downloads$ sudo apt update
Ign:1 http://deb.debian.org/debian byzantium InRelease
Get:2 https://ftp.debian.org/debian bookworm InRelease [129 kB]
Err:3 http://deb.debian.org/debian byzantium Release
404 Not Found [IP: 151.101.186.132 80]
Get:4 https://ftp.debian.org/debian bookworm/main amd64 Packages [8,277 kB]
Get:5 https://repo.pureos.net/pureos byzantium InRelease [5,851 B]
Get:6 https://repo.pureos.net/pureos byzantium-security InRelease [4,581 B]
Get:7 https://repo.pureos.net/pureos byzantium-updates InRelease [4,580 B]
Get:8 https://ftp.debian.org/debian bookworm/main Translation-en [5,688 kB]
Get:9 https://ftp.debian.org/debian bookworm/main amd64 DEP-11 Metadata [4,199 kB]
Get:10 https://ftp.debian.org/debian bookworm/main DEP-11 48x48 Icons [3,451 kB]
Get:11 https://ftp.debian.org/debian bookworm/main DEP-11 64x64 Icons [7,198 kB]
Get:12 https://ftp.debian.org/debian bookworm/main all Contents (deb) [31.3 MB]
Get:13 https://ftp.debian.org/debian bookworm/main amd64 Contents (deb) [10.3 MB]
Reading package lists… Done
E: The repository ‘http://deb.debian.org/debian byzantium Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
ralf@ralf-macbookpro11:~/Downloads$ sudo apt install gcc-11-base locales libc-bin libc6 libstdc++6 libetonyek-0.1-1
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 18724 (synaptWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 18724 (synaptWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 18724 (synaptWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 18724 (synaptWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It iWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 18724 (synaptic) procWaitiReading package lists… Done 9s(sWaiting for Building dependency tree… Donevar/lib/dpkg/lock-frontend. It is held by process 18724 (synaptic)… 28sWaiting for cache locReading state information… Donekg/lock-frontend. It is held by process 18724 (synaptic)… 27siting for cache lock: Could nolibetonyek-0.1-1 is already the newest version (0.1.10-3).ess 18724 (synaptic)… 26sing for cache lock: Could not get lock /vlibetonyek-0.1-1 set to manually installed.ocess 18724 (synaptic)… 25sg for cache lock: Could not get lock /var/lib/dpkg/locYou might want to run ‘apt --fix-broken install’ to correct these. lock: Could not get lock /var/lib/dpkg/lock-frontend. It isThe following packages have unmet dependencies: lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 18 libc-dev-bin : Depends: libc6 (< 2.32) but 2.33-5 is to be installed
libc6-dev : Depends: libc6 (= 2.31-13) but 2.33-5 is to be installed
libetonyek-dev : Depends: libetonyek-0.1-1 (= 0.1.9-4) but 0.1.10-3 is to be installed
locales : Depends: libc-l10n (> 2.33) but 2.31-13 is to be installed
E: Unmet dependencies. Try ‘apt --fix-broken install’ with no packages (or specify a solution).
ralf@ralf-macbookpro11:~/Downloads$ sudo apt install gcc-11-base locales libc-bin libc6 libstdc++6 libetonyek-0.1-1
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
libetonyek-0.1-1 is already the newest version (0.1.10-3).
libetonyek-0.1-1 set to manually installed.
You might want to run ‘apt --fix-broken install’ to correct these.
The following packages have unmet dependencies:
libc-dev-bin : Depends: libc6 (< 2.32) but 2.33-5 is to be installed
libc6-dev : Depends: libc6 (= 2.31-13) but 2.33-5 is to be installed
libetonyek-dev : Depends: libetonyek-0.1-1 (= 0.1.9-4) but 0.1.10-3 is to be installed
locales : Depends: libc-l10n (> 2.33) but 2.31-13 is to be installed
E: Unmet dependencies. Try ‘apt --fix-broken install’ with no packages (or specify a solution).
ralf@ralf-macbookpro11:~/Downloads$ apt --fix-broken install
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
ralf@ralf-macbookpro11:~/Downloads$ sudo apt --fix-broken install
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Correcting dependencies… Done
The following package was automatically installed and is no longer required:
libc-devtools
Use ‘sudo apt autoremove’ to remove it.
The following additional packages will be installed:
gcc-11-base libc-bin libc-dev-bin libc-l10n libc6 libc6-dev libetonyek-dev libstdc++6 locales rpcsvc-proto
Suggested packages:
glibc-doc libnss-nis libnss-nisplus
Recommended packages:
libc-devtools
The following NEW packages will be installed:
gcc-11-base rpcsvc-proto
The following packages will be upgraded:
libc-bin libc-dev-bin libc-l10n libc6 libc6-dev libetonyek-dev libstdc++6 locales
8 upgraded, 2 newly installed, 0 to remove and 1171 not upgraded.
1 not fully installed or removed.
Need to get 12.1 MB of archives.
After this operation, 1,385 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://ftp.debian.org/debian bookworm/main amd64 libetonyek-dev amd64 0.1.10-3 [107 kB]
Get:2 https://ftp.debian.org/debian bookworm/main amd64 libc-l10n all 2.33-5 [864 kB]
Get:3 https://ftp.debian.org/debian bookworm/main amd64 locales all 2.33-5 [4,088 kB]
Get:4 https://ftp.debian.org/debian bookworm/main amd64 libc-dev-bin amd64 2.33-5 [243 kB]
Get:5 https://ftp.debian.org/debian bookworm/main amd64 libc6-dev amd64 2.33-5 [2,274 kB]
Get:6 https://ftp.debian.org/debian bookworm/main amd64 rpcsvc-proto amd64 1.4.2-4 [63.1 kB]
Get:7 https://ftp.debian.org/debian bookworm/main amd64 libc6 amd64 2.33-5 [2,831 kB]
Get:8 https://ftp.debian.org/debian bookworm/main amd64 libc-bin amd64 2.33-5 [834 kB]
Get:9 https://ftp.debian.org/debian bookworm/main amd64 gcc-11-base amd64 11.2.0-14 [207 kB]
Get:10 https://ftp.debian.org/debian bookworm/main amd64 libstdc++6 amd64 11.2.0-14 [577 kB]
Fetched 12.1 MB in 8s (1,472 kB/s)
Preconfiguring packages …
(Reading database … 147705 files and directories currently installed.)
Preparing to unpack …/0-libetonyek-dev_0.1.10-3_amd64.deb …
Unpacking libetonyek-dev:amd64 (0.1.10-3) over (0.1.9-4) …
Preparing to unpack …/1-libc-l10n_2.33-5_all.deb …
Unpacking libc-l10n (2.33-5) over (2.31-13) …
Preparing to unpack …/2-locales_2.33-5_all.deb …
Unpacking locales (2.33-5) over (2.31-13) …
Preparing to unpack …/3-libc-dev-bin_2.33-5_amd64.deb …
Unpacking libc-dev-bin (2.33-5) over (2.31-13) …
Preparing to unpack …/4-libc6-dev_2.33-5_amd64.deb …
Unpacking libc6-dev:amd64 (2.33-5) over (2.31-13) …
Replacing files in old package libc6:amd64 (2.31-13) …
Selecting previously unselected package rpcsvc-proto.
Preparing to unpack …/5-rpcsvc-proto_1.4.2-4_amd64.deb …
Unpacking rpcsvc-proto (1.4.2-4) …
Preparing to unpack …/6-libc6_2.33-5_amd64.deb …
Checking for services that may need to be restarted…
Checking init scripts…
Unpacking libc6:amd64 (2.33-5) over (2.31-13) …
Setting up libc6:amd64 (2.33-5) …
Checking for services that may need to be restarted…
Checking init scripts…
Restarting services possibly affected by the upgrade:
cups: restarting…done.
cron: restarting…done.
Services restarted successfully.
(Reading database … 147696 files and directories currently installed.)
Preparing to unpack …/libc-bin_2.33-5_amd64.deb …
Unpacking libc-bin (2.33-5) over (2.31-13) …
Setting up libc-bin (2.33-5) …
Selecting previously unselected package gcc-11-base:amd64.
(Reading database … 147696 files and directories currently installed.)
Preparing to unpack …/gcc-11-base_11.2.0-14_amd64.deb …
Unpacking gcc-11-base:amd64 (11.2.0-14) …
Setting up gcc-11-base:amd64 (11.2.0-14) …
(Reading database … 147701 files and directories currently installed.)
Preparing to unpack …/libstdc++6_11.2.0-14_amd64.deb …
Unpacking libstdc++6:amd64 (11.2.0-14) over (10.2.1-6) …
Setting up libstdc++6:amd64 (11.2.0-14) …
Setting up libc-l10n (2.33-5) …
Setting up libetonyek-0.1-1:amd64 (0.1.10-3) …
Setting up locales (2.33-5) …
Installing new version of config file /etc/locale.alias …
Generating locales (this might take a while)…
en_US.UTF-8… done
Generation complete.
Setting up rpcsvc-proto (1.4.2-4) …
Setting up libc-dev-bin (2.33-5) …
Setting up libetonyek-dev:amd64 (0.1.10-3) …
Setting up libc6-dev:amd64 (2.33-5) …
Processing triggers for man-db (2.9.4-2) …
Processing triggers for libc-bin (2.33-5) …
ralf@ralf-macbookpro11:~/Downloads$
Even in the preview libre office shows the picture.
So why would it not show when the document is opened?
Not seeing everything well, as not behind your laptop, but it is obvious that synaptic locked (blocked) apt install process:
Therefore folowing steps should help:
Please remove: bookworm main from your sources.list
sudo dpkg --configure -a −− will not produce any output if everything all right (as should be).
sudo apt update
sudo apt purge synaptic −− you can install it afterwards again.
sudo apt install -f
sudo apt upgrade
sudo apt autoremove
If above works smoothly your PureOS is back on track. If not: “Another potential way to get around this issue is to reboot the system and see if this still occurs.”
Rename your file to P7100_injection_pump.pages.zip (non spaces one).
unzip P7100_injection_pump.pages.zip -d /Documents/XXX
Try again to open P7100_injection_pump.pages file, hope this helps.
When I saw the synaptic block, I noticed that the app was still open and running. After I closed it, the install seemed to go well as you may see further down, where I tried again.
1 Like
libre office needs to have the pages document as a zip package. If you try to open the extracted folder it goes down into the folder in the opening process and looks for a single file document.
As I said before, the only way to even transfer a pages document from one computer to another is by creating a zip file first.
Pages as well as libre office open the zip file directly and treat it like the actual document.
I am still saying that something in the PureOS version of libre office is malfunctioning to keep the images from being displayed in the document.
But at the same time libre office does know which image needs to go where. I can right-click on the place holder of each image and look at its properties, like I did above, and there is the preview of the correct image, that needs to go there.
If libre office knows which image goes where in the document, it has all the information it needs, it just does not execute displaying it.
I’m not familiar with .pages documents, but did you try to open this file under LibreOffice by renaming it to P7100-injection-pump.pages.zip or even by just renaming it to P7100-injection-pump.pages (removing .zip extention)? I’m learning from you here as well.
Yes,I tried. The name change makes no difference.
Are those two questions (same ones, just solutions differ) relevant to your issue here: https://apple.stackexchange.com/questions/126903/how-can-i-upgrade-all-my-pages-09-documents-to-pages-13 and https://apple.stackexchange.com/questions/150771/how-do-i-convert-old-pages-documents-to-pages-13?
We’re going more and more advanced because nobody seems to have considered whether the problem might be simple. Have you checked the LibreOffice Writer Options to see if images are actually enabled? This can be found by opening up LibreOffice Writer and selecting Tools > Options >LibreOffice Writer > View from the Menu Bar. Obviously, you’re going to want the “Images and objects” box selected as seen here in this screenshot:
1 Like
Jack,
Thank you so much. I knew for a while, it had to be something within Libre Office, but had no idea where to look.
The images show up in my documents now.
No problem. Sometimes, the solutions to the most complicated problems are the simplest ones that first come to mind. 
Unfortunately, that would be very difficult to answer due to the fact that very few people outside of the Apple ecosystem would ever use Apple formats, let alone .pages. You might be able to get more help from the official LibreOffice forums. Might I suggest you start a thread there? 