Printed File Has No Data
fatalkarma100 opened this issue · comments
I had this installed and working great. Updated to rM sw 3.0 which updated the IP address. I deleted the original install and reinstalled the native printer hack, chose existing driver, and then went back to chnage driver to MS Print to PDF. Now I am getting only one page no matter how many pages (tried in Excel and Word) and with no data - blank one page. Checked the MS Print to PDF printer and it printed a test page with printer data.
Appreciate thoughts on how to fix this.
Me too. I have the same problem.
Yep, try with the latest version and report back. If it still doesn't work try the Debugging section of the README and paste the log here.
Yep, try with the latest version and report back. If it still doesn't work try the
Debuggingsection of the README and paste the log here.
Updated with latest version, still printing only one blank page, please see log below:
reMarkable: ~/ journalctl --unit printer -f
-- Logs begin at Sat 2023-01-14 06:55:07 UTC. --
Jan 21 07:28:01 reMarkable systemd[1]: printer.service: Failed with result 'exit-code'.
Jan 21 07:28:01 reMarkable systemd[1]: printer.service: Scheduled restart job, restart counter is at 2.
Jan 21 07:28:01 reMarkable systemd[1]: Stopped Native printing to reMarkable.
Jan 21 07:28:01 reMarkable systemd[1]: Started Native printing to reMarkable.
Jan 21 07:28:01 reMarkable printer.arm[254]: Listening on 0.0.0.0:9100
Jan 21 07:33:03 reMarkable printer.arm[254]: Saving PDF to /home/root/.local/share/remarkable/xochitl/9796700c-80c6-4acc-b0f9-aeb46db68be1.pdf
Jan 21 07:33:03 reMarkable printer.arm[254]: [%PDF-1.7
Jan 21 07:33:03 reMarkable printer.arm[254]: ]
Jan 21 07:33:03 reMarkable printer.arm[254]: [PDF begin]
Jan 21 07:33:03 reMarkable printer.arm[254]: Saving metadata to /home/root/.local/share/remarkable/xochitl/9796700c-80c6-4acc-b0f9-aeb46db68be1.metadata
Jan 21 07:38:00 reMarkable printer.arm[254]: Saving PDF to /home/root/.local/share/remarkable/xochitl/a07cc4ef-6028-47ed-84af-a4eaecba406a.pdf
Jan 21 07:38:00 reMarkable printer.arm[254]: [%PDF-1.7
Jan 21 07:38:00 reMarkable printer.arm[254]: ]
Jan 21 07:38:00 reMarkable printer.arm[254]: [PDF begin]
Jan 21 07:38:00 reMarkable printer.arm[254]: Saving metadata to /home/root/.local/share/remarkable/xochitl/a07cc4ef-6028-47ed-84af-a4eaecba406a.metadata
Does the metadata file have the fields lastOpened and LastOpenedPage?
Commit 621cbee fixed this for me.
I actually compiled from source; I didn't use the release.
Does the metadata file have the fields lastOpened and LastOpenedPage?
I can't find the folder .local. It's not under /home/root.
It's a "hidden" directory. Your file browser application should have a configuration parameter which controls their visibility.
Alternatively,
cat /home/root/.local/share/remarkable/xochitl/a07cc4ef-6028-47ed-84af-a4eaecba406a.metadata
when you're logged into the tablet via ssh
Does the metadata file have the fields lastOpened and LastOpenedPage?
Here's the log:
{
"deleted": false,
"lastModified": "1674288795464",
"lastOpened": "1674286383000",
"lastOpenedPage": 0,
"metadatamodified": true,
"modified": true,
"parent": "trash",
"pinned": false,
"synced": false,
"type": "DocumentType",
"version": 0,
"visibleName": "Printed"
}
It's a "hidden" directory. Your file browser application should have a configuration parameter which controls their visibility.
Alternatively,
cat /home/root/.local/share/remarkable/xochitl/a07cc4ef-6028-47ed-84af-a4eaecba406a.metadatawhen you're logged into the tablet via
ssh
Any help would be appreciated. lastOpenedpage:0 - does this mean nothing was opened for print?
Can you compare that file to one of the .metadata files of a document that displays correctly? Each document has other files besides .metadata, so you might look for differences there, too.
I'm not running the latest xochitl version so I can't check this myself.
I've attached a zip file of what is stored on my rm2 when printing to the tablet via this driver. I can view it properly on the rm2.
You can try a couple of things:
- scp the zip file to your rm2, unzip it, and make sure that you can view the resultant PDF. I presume you'll have to reboot or whatever magic is required to get the rm2 to scan the directory.
- print the PDF to the rm2 and compare the resulting files on the rm2 to the ones in the zip file.
I ran into this issue as well. The problem seems to be that the .content file is being detected as invalid and is overwritten with the fileType set to notebook instead of pdf. If I ssh in and edit the content file manually to change the fileType back to pdf, the file can then be opened as a pdf.
I guess the CONTENT_TEMPLATE needs to be changed.
@bsvh Can you paste an example of a good .content file here? What's invalid in CONTENT_TEMPLATE?
Looking at the source, CONTENT_TEMPLATE only sets the fileType, and I'm guessing the new firmware decided that's not enough? In any case, here's the .content of a test document I uploaded using the official app
{
"coverPageNumber": 0,
"customZoomCenterX": 0,
"customZoomCenterY": 936,
"customZoomOrientation": "portrait",
"customZoomPageHeight": 1872,
"customZoomPageWidth": 1404,
"customZoomScale": 1,
"documentMetadata": {
"title": "My Test Document"
},
"extraMetadata": {
},
"fileType": "pdf",
"fontName": "",
"formatVersion": 1,
"lineHeight": -1,
"margins": 125,
"orientation": "portrait",
"originalPageCount": 1,
"pageCount": 1,
"pageTags": [
],
"pages": [
"6c797d30-ee46-46fa-9adf-e6fad66e722b"
],
"redirectionPageMap": [
0
],
"sizeInBytes": "81034",
"tags": [
],
"textAlignment": "justify",
"textScale": 1,
"zoomMode": "bestFit"
}
And here's what it looks like after using the printer driver
{
"coverPageNumber": -1,
"customZoomCenterX": 0,
"customZoomCenterY": 936,
"customZoomOrientation": "portrait",
"customZoomPageHeight": 1872,
"customZoomPageWidth": 1404,
"customZoomScale": 1,
"documentMetadata": {
},
"extraMetadata": {
},
"fileType": "notebook",
"fontName": "",
"formatVersion": 1,
"lineHeight": -1,
"margins": 125,
"orientation": "portrait",
"originalPageCount": -1,
"pageCount": 1,
"pageTags": [
],
"pages": [
"5d1af207-b572-4b97-9b0f-d1ba294f64b7"
],
"redirectionPageMap": [
],
"sizeInBytes": "0",
"tags": [
],
"textAlignment": "justify",
"textScale": 1,
"zoomMode": "bestFit"
}
If I change the filetype to pdf and restart xochitl, I can then open it.
I'm puzzled by this, as I'm having zero problems (even w/ the latest bump to 3.2). The .contents files have a proper filetype of PDF when I print them to the tablet.
I did recompile the executable rather than use the one on the releases page. Maybe that's the difference...
AHA. The dates of the files in the release.zip for 11.0.1 file are older than the relevant commit on Jan 5, 2023:
$ unzip -l /tmp/release.zip
Archive: /tmp/release.zip
Length Date Time Name
--------- ---------- ----- ----
3388094 2022-12-11 21:36 printer.arm
3749171 2022-12-11 21:36 printer.x86
165 2020-12-29 01:08 printer.service
--------- -------
7137430 3 files
I think an older version is in the released zip file.
I must've forgotten to make clean before making the last release. @djerius Could you try with 11.0.2?
@Evidlo It works!
For the record:
/tmp $ unzip -l release.zip
Archive: release.zip
Length Date Time Name
--------- ---------- ----- ----
2992129 2023-03-10 19:51 printer.arm
3057960 2023-03-10 19:51 printer.x86
165 2020-12-29 01:08 printer.service
--------- -------
6050254 3 files
/tmp $ unzip release.zip
Archive: release.zip
inflating: printer.arm
inflating: printer.x86
inflating: printer.service
/tmp $ sha256sum printer.arm
77ef9c2ae7d0ad3fdd4a1982f9ae5cb46744d6486bcc526a359ef75d78a4e645 printer.arm
On the tablet:
root@reMarkable:~/bin# sha256sum /home/root/bin/printer.arm
77ef9c2ae7d0ad3fdd4a1982f9ae5cb46744d6486bcc526a359ef75d78a4e645 /home/root/bin/printer.arm
Thanks for the help everyone! I'll reopen if there are more issues.