-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
does not work with 2.6.1.71 #23
Comments
I think I'm seeing the same. On macbook:
On reMarkable:
|
It appears the problem is, as mentioned that the ".content' does not exist!". I turned off the automatic restart, printed, then copied a content file into place from another PDF uploaded by the standard software. I also altered the .metadata file to give it a name which wasn't "printed", then manually restarted and I got a working PDF I could read again.
So it looks like a solution may be for remarkable_printer to create a .content file. This is the file I copied into place (which was very obviously incorrect):
It looks like xochitl scanned the PDF and corrected it:
|
It seems you only need a single entry in that .content file for things to work:
I copied this into place and manually restarted xochitl and things worked fine.
|
Thanks! You can make a PR or I can just commit the change if you want. |
Just testing now and it looks like it's working ... PR shortly. |
I tried the fix but the problem persists. Now it says Printed in the remarkable, and it's the same if I try to print on browser or print test page.
If i put the dummy.content in 4e5cf0c7-c27e-4841-a853-347ff59bc1eb.content and reboot it works but the name is "Printed" again. |
What exact fix did you try?
Are you sure the patch applied? The above seems to suggest it wasn't applied. That .content file is what the patch created.
I didn't manage to get the filename to be anything other than "Printed" either. I wasn't able to work out how that worked looking at the PDF files and the code reading them. But otherwise, it did at least work and print the document. |
Yes I have the patch applied. I also deleted the
|
Same here. I'm using a rm1 with ddvk patch. |
I think maybe I see the reason the fix isn't working for you. The release.zip does not appear to have been updated since the code was merged, so you're still using the same code from prior to the fix.
You can also see: https://github.com/Evidlo/remarkable_printer/releases/tag/6 " @Evidlo Evidlo released this 14 days ago · 4 commits to master since this release " @dansbandit - when you say you have the patch applied, did you build the latest source yourself and transfer it over manually? |
In the meantime, until @Evidlo makes a release, you can try this temporary release out:
you should still expect to see the filename "printed", but the file should not be blank. |
I think the name of the file being "Printed" is a separate issue for which we may need a different fix. I've created a separate issue for it. |
My bad! I will keep this in mind next time! |
Reinstalled after the 2.6.1.71 update.
What gets printed is one white page.
The text was updated successfully, but these errors were encountered: