#force-koreader-landscape not working with type folio
1 messages · Page 1 of 1 (latest)
via reManager, go to Maintenance and run xovi's debug command, copy the result and paste it here, or once it's running, (assuming reManager higher than 1.1.0) submit a support bundle and paste the URL to it here. That command won't terminate, so once it's run for a minute or so, stop it, then run xovi start
this part maybe?
Loading file forceKoreaderLandscape.qmd
[qmldiff]: Failed to load file /home/root/xovi/exthome/qt-resource-rebuilder/forceKoreaderLandscape.qmd: Error while parsing: expected Identifier, got Unknown('?')
that's the guy
Too old qt-resource-rebuilder
which device?
rm2
which version of qt-resource-rebuilder do you have installed?
on reManager it says 17.0.0-r4
that's what I thought, no one should really get v16 via reManager / vellum
@neat vapor Oh yeah, how do you publish the not-yet-released v18?
it's only in the testing repo
@vast pond has been working on that PR
Anything that uses wildcards (?[...]) syntax will break on v17 and earlier
oh I thought v17 supported wildcards?
Isn't forceKoreaderLandscape.qmd the same between 3.24 and 3.25 though? It works for me on 3.24
yeah should be the same qmd content
Oh right - yeah, that should work
haha okay i was looking at the github repo and you guys are the ones who make all of these things i feel a little stupid but am i just waiting for the v18 now?
Try manually forcing v17 onto your tablet from my repo @carmine sonnet
That should make it work
that's not ideal
@carmine sonnet could you do sha256sum ~/xovi/extensions.d/qt-resource-rebuilder.so and share the output?
316d60e8bc0597854172addb4b09ff7363a1148b8128c7e55977877a7e41910b /home/root/xovi/extensions.d/qt-resource-rebuilder.so
which device?
I'm surprised at how forgetful I can be
.
I'm re-bootstrapping my rm2 to test
that is not v17
v17 should be 9a973f73123893f25d17c4d2e053de76583d58312b34e8aaabbecef3a4aee91f right
that's v16
yup
That's not v16 either
@m try hitting "vellum upgrade" in reManager maintenance
I've no idea what qt-resource-rebuilder you're on, but it's none of the officially built ones
it is
[notfrants@archlinux extensions-arm32-testing(4)]$ sha256sum qt-resource-rebuilder.so
316d60e8bc0597854172addb4b09ff7363a1148b8128c7e55977877a7e41910b qt-resource-rebuilder.so
no updates available
is it just lying
hmm can you open the terminal (either via remanager or ssh) and run vellum fix qt-resource-rebuilder
had you installed any of the xovi stuff before reManager?
(or after)
no everything through remanager
wouldn't vellum overwrite that anyways?
should
(1/1) Reinstalling qt-resource-rebuilder (17.0.0-r4)
ERROR: qt-resource-rebuilder-17.0.0-r4: DNS: transient error (try again later)
damn rm dns
toggle airplane mode on, wait a couple seconds, then turn off airplane mode
then re-run that command
I wonder how that happened
okay now the question is how that happened in the first place
could you submit a support bundle, no need to post it here, I'll take a look at the logs on my end 🙂
could you do sha256sum /home/root/xovi/extensions.d/*.so, curious if it's just qrr or all xovi-extensions
oo good call
@carmine sonnet
e6cd2f6b1a00a2bf6a5aef2570a0668ad1a4d915c1945164a5f8cfff7bc94272 /home/root/xovi/extensions.d/appload.so
b4c07a6f1ed100517633dff081f46b9d94bdc4e598dee8a57b81cea1da78ca8b /home/root/xovi/extensions.d/fileman.so
a60ef8ad3f3cd96e0904cc8dd1554ff318a4e0f0fac8bbe7d1a1ad2e47e4f1e0 /home/root/xovi/extensions.d/framebuffer-spy.so
1e1300097b0544c8adcfc29287ff2988e9a6469ee05f62da5a266238bd7d91f7 /home/root/xovi/extensions.d/qt-command-executor.so
9a973f73123893f25d17c4d2e053de76583d58312b34e8aaabbecef3a4aee91f /home/root/xovi/extensions.d/qt-resource-rebuilder.so
f31f0b44fb86591a7fbf735d63a403ff1eb575b779138949b1c2d323228c2dd0 /home/root/xovi/extensions.d/random-suspend-screen.so
cfc1db7ace0addf699d992c07d8d4d79c38e4f14cfc9f211580e0ec577d70f17 /home/root/xovi/extensions.d/webserver-remote.so
0bd54e0d14a2bdeb10ede78d7afcc0f0d7bd9cf0e64e019a494780250c3adb07 /home/root/xovi/extensions.d/xovi-message-broker.so
hold on
BTW: I'm still open for the ideas on how to fix this correctly, LOL. There should be no need for that qmd file, if appload worked correctly.
there's no way reManager installed those
fileman??
Oh yeah - do not run fileman if you're not a developer haha
fileman's never been packaged in vellum
all of those except qrr and appload are v16
are you sure you haven't installed xovi after (or before) remanager?
vellum list -I would be interesting too
yea because the first thing i wanted and knew of was koreader and when installing it xovi is a dependency right? so remanager installed like 5 other things
Yes, but fileman is a tool that remanager couldn't have installed
but you've never run "install-xovi-for-rm"?
It's meant to be used for developers for hooking low-level file access
is this the only way? can i just grep from history?
you can send the history here probably
yeah you could do history | grep xovi
also history | grep extensions might be useful, since the libs were moved from there
ah yeah I forget xovi isn't in the extensions zip name
only thing is scp comicreader.koplugin
that doesnt even have xovi in it
wait but you need to do that on the remarkable, not your computer
i didnt copy the whole command but it was there in the file path
oh haha
45 cd ./home/root/xovi/exthome/appload/koreader
50 cd xovi
58 sha256sum ~/xovi/extensions.d/qt-resource-rebuilder.so
61 sha256sum /home/root/xovi/extensions.d/*.so
63 history | grep xovi
history | grep extensions
58 sha256sum ~/xovi/extensions.d/qt-resource-rebuilder.so
61 sha256sum /home/root/xovi/extensions.d/*.so
64 history | grep extensions
Honestly, I suggest a full reinstall at this point
At least of xovi and friends
QMDs are probably all OK, and so are koreader apps
But the extensions are weird
that's really weird
can you also do find xovi -maxdepth 3?
xovi
xovi/debug
xovi/stock
xovi/extensions.d
xovi/extensions.d/fileman.so
xovi/extensions.d/webserver-remote.so
xovi/extensions.d/xovi-message-broker.so
xovi/extensions.d/random-suspend-screen.so
xovi/extensions.d/qt-command-executor.so
xovi/extensions.d/appload.so.conf
xovi/extensions.d/framebuffer-spy.so
xovi/extensions.d/appload.so
xovi/extensions.d/qt-resource-rebuilder.so
xovi/start
xovi/xovi.so
xovi/stop
xovi/rebuild-hashtable.sh
xovi/exthome
xovi/exthome/appload
xovi/exthome/appload/koreader
xovi/exthome/qt-resource-rebuilder
xovi/exthome/qt-resource-rebuilder/unlockMethodsContent.qmd
xovi/exthome/qt-resource-rebuilder/_ingatellent.qmd
xovi/exthome/qt-resource-rebuilder/hashtab
xovi/exthome/qt-resource-rebuilder/enableAllColors.qmd
xovi/exthome/qt-resource-rebuilder/forceKoreaderLandscape.qmd
xovi/exthome/qt-resource-rebuilder/ingatellent
xovi/rebuild_hashtable
okay i think i was trying to install something else maybe? and gave up on it in the middle becuase i remember something with the rebuild hashtable
Yeah... I don't remember writing these files, like ever
im sorry guys i might have been lying about not installing anything before or after but i honestly dont remember
I've no idea what xovi/stop is and I wrote the damned thing 🤣
it's okay, we're just trying to figure out the mystery
no it was not freemarkable
pretty sure that's it
let me check my search history
readmarkable? my enemy
hmm I don't see it there either (at least in the copy of the source I have)
omg yea i first tried it with readmarkable
but that didnt work
so i used remanager
lol more proof that dude just ripped off freemarkable
Did readmarkable really install fucking everything and the kitchen sink into the extensions?
That's irresponsible LOL
I would blame freemarkable for this
there's plenty of blame for readmarkable
haha is there remarkable drama
so reManager exists because readmarkable exists
I saw them making a closed source tool that stole community-made software without attribution, and I spent 3 weeks writing reManager and a package system for it to use lol
okay genually wtf
like it's mounting / as rw on xovi/start, making the xovi systemd dropin permanent
@carmine sonnet do cat xovi/start | head -n 10
at this point, I'd recommend the following:
rm -r xovi
rm -r .vellum
then re-install via reManager
Recipe for disaster
that will delete everything in xovi, you may not have to go that hard
Warning: This will reset plugins for koreader
oh damn okay thats really sad but cool from your part thank you
yea you might want to make a backup of xovi/exthome
Essentially it's the nuclear approach: Start over. Also, make sure you don't have anything written to root, because if what notfrants says is true then that might actually brick your tablet
ah true crap, what a mess
The safest thing here would probably be to update to the same version you're on, then restarting, then removing xovi and starting anew with reManager only
you might want to do a fresh os install. Easiest steps (probably):
- install rm-version-switcher via reManager
- run it, swap to booting from your backup partition
- once you reboot into the previous version, check for updates, install 3.25.1.1, reboot into it
- then do the deletes I mentioned
How did I not notice this. 🙁
It's amazing how many people do not get why I explicitly made xovi this way
can we do something with freemarkable? it has 80+ starts so that's a lot of users with cursed installs
how easy is it to fuck it up and brick my tablet
Yikes
doing the listed actions?
or in general?
okay right i should be able to follow instructions
those steps are safe
wait do this before, I want to check
#!/bin/bash
mkdir -p /etc/systemd/system/xochitl.service.d
mount -t tmpfs tmpfs /etc/systemd/system/xochitl.service.d
cat > /etc/systemd/system/xochitl.service.d/xovi.conf << 'XOVI_CONF'
[Service]
Environment="QML_DISABLE_DISK_CACHE=1"
Environment="QML_XHR_ALLOW_FILE_WRITE=1"
Environment="QML_XHR_ALLOW_FILE_READ=1"
Environment="LD_PRELOAD=/home/root/xovi/xovi.so"
XOVI_CONF
okay at least remanager saved that
freeMarkable - Jailbreak Toolkit for reMarkable 1+2+rmPP devices
I would argue bricking the tablet is closer to a jail than the stock state
I really don't know why the freemarkable person rewrote all the installers...
lol apparently a couple new people are trying to keep freemarkable alive
silly question but did i have to manually create a backup
of what?
swap to booting from your backup partition means that i will boot into a backup? im assuming i had to make something like that or am i understanding it wrong sorry guys
fallback would be a better word probably
ah no, just the OS, reMarkable runs an A/B os scheme
oh okay im going to try this then
so when you do an OS upgrade, it upgrades the fallback partition, then boots into and that's the new active partition. Then the next upgrade does the other one, so you're always flip-flopping between then as you do upgrades
oo cool thank you
is it a dick move to go plug my own tool in freemarkable's github issues lol
I think I'll refrain but .... https://github.com/wowitsjack/freeMarkable/issues/21
how was there a PR 30 min ago? lol
maybe ping @scaredpelican since it's their project? they have some explanation to do lol
wait hold on they left the server
Was that wowitsjack?
I think they left when they got rid of their rM
Which was like a week after making the project…
#general message
pretty sure yes
Antlers yep
thank you everyone you have been really helpful i have reinstalled the packages and everything works yay
Happy to hear that 🙂
Make sure you disable rM autoupdates
Then check compatibility for your installed packages before you pull the trigger on upgrading the OS. reManager has a Check OS button for that.
oh true thank you for reminding me