arctic pilot
I've been beating my head against a wall for 3 days. The official toolchain is sourced and I was able to comple rm-appload but when I try to compile qtfb I get this error:
Project ERROR: Unknown module(s) in QT: qml quickcontrols2
make: *** No targets specified and no makefile found. Stop.
trim current
@steep cedar
arctic pilot
Well I got past that by installing a qt package. Figures as soon as I ask I figure it out....
trim current
Installing a qt package?
If installing a system package affects things, you aren't using the toolchain
arctic pilot
well everything seemed to work but nothing happens when i click KOReader
trim current
It's probably erroring out
It's probably erroring because it's being built for your system architecture instead of using the toolchain
arctic pilot
Well, I don't know any other way to check. $CC returned the toolchain and it showed in source. blah. guess im just in over my head.
I'll start over tomorrow I suppose. Any tips to make sure it is compiling from the toolchain?
trim current
Without digging in more to how it's build is configured, no idea
merry orchid
You probably want to share more about your setup. You write "The official toolchain is sourced", but did you use a linux machine and install it yourself, did you use Eeems' docker image? Did you use wsl? Which command did you run to source the toolchain, and did it give any feedback? (Because it sounds like your make script did not use the toolchain).
Also try to run file qtfb.so when you've built it, it will tell you if it is built for the right architecture.
Finally: When you make changes to your system and use xovi, you should always run it with xovi/debug first, to make sure things are working as expected (the output should also give some hints at what is working and what is not).
arctic pilot
Thank you. Let me give more details: I'm working on WSL and I downloaded this toolchain: remarkable-production-image-5.0.58-ferrari-public-x86_64-toolchain.sh
I'm installing it again now and then will use . path to use it
. /home/sean/dev/sdk/environment-setup-cortexa53-crypto-remarkable-linux
echo $CC
aarch64-remarkable-linux-gcc -mcpu=cortex-a53+crc+crypto -mbranch-protection=standard --sysroot=/home/sean/dev/sdk/sysroots/cortexa53-crypto-remarkable-linux
is that a good indicator that it is correctly sourced?
gilded sonnet
I thought you were supposed to use the source command
trim current
I thought you were supposed to use the source command
. /path/to/file and source /path/to/file are the same thing
trim current
echo $CC
aarch64-remarkable-linux-gcc -mcpu=cortex-a53+crc+crypto -mbranch-prote...
Or does appear to be sourced in that session.
arctic pilot
I was able to compile rm-appload and it appeared to use the toolchain. I will try to compile qtfb again shortly and report back. Thank you for all your help.
arctic pilot
So it compiled both qtfb and the shim with no errors.
17:38:24.215 default Failed to start process: "Child process set up failed: execve: Exec format error"
thats what i get from debug when trying to run KOReader
17:38:24.208 default [AppLoad]: Starting external binary "./reader.lua"
17:38:24.215 default Failed to start process: "Child process set up failed: execve: Exec format error"
winter sorrel
Hi. @arctic pilot refer to this: https://github.com/koreader/koreader/issues/13814
still skiff
Sounds like you might not be using the aarch64 version. Exec format error usually indicates the binary you are running is for a different architecture.
Looks like you are close though!
arctic pilot
07/16/25-22:02:52 INFO Starting reMarkable Ferrari
ERROR: ld.so: object '~/shims/qtfb-shim.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '~/shims/qtfb-shim.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
07/16/25-22:02:52 INFO Oxide running?: false
./luajit: ./ffi/framebuffer_linux.lua:55: cannot open framebuffer
stack traceback:
[C]: in function 'assert'
./ffi/framebuffer_linux.lua:55: in function 'init'
./ffi/framebuffer_mxcfb.lua:830: in function 'init'
./ffi/framebuffer.lua:140: in function 'new'
frontend/device/remarkable/device.lua:186: in function 'init'
frontend/device.lua:54: in main chunk
[C]: in function 'require'
./reader.lua:151: in main chunk
[C]: at 0x00405150
22:02:52.209 default [AppLoad]: Process for "./reader.lua" finished with exit code 1 and status QProcess::NormalExit
even further but now it seems like it is not opening the shim file?
trim current
Is this the nightly build of KOReader for the rMPP?
arctic pilot
It's the only one I could find with arch in the name.
I don't think it is the nightly build
trim current
I don't think it is the nightly build
rMPP support is not yet released for KOReader, which is also what is says in the install instructions:
KOReader support for the reMarkable Paper Pro has not yet been released, but early nightly builds are available.
https://github.com/koreader/koreader/wiki/Installation-on-reMarkable#manual-installation-on-remarkable-paper-pro
arctic pilot
I read that and I'm searching for the right place to download the nightly build. Thanks for the assistance.
I think I finally found it
trim current
https://build.koreader.rocks/download/nightly/v2025.04-161-g70039c9f0_2025-07-15/ Here is today's nightly builds
arctic pilot
Thank you so much.
ERROR: ld.so: object 'home/root/shims/qtfb-shim.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
trim current
As I don't know what specific call is triggering that, I don't know if that's a real error or just a warning
is it still erroring about being unable to open the framebuffer?
arctic pilot
launching...
| |/ / _ | _ \ ___ __ _ | | ___ _ __
| ' / | | | |_) / _ / _ |/ _ |/ _ \ '|
| . \ || | _ < __/ (| | (| | __/ |
||__/|_| __|_,|_,|___|_|
It's a scroll... It's a codex... It's KOReader!
[] Current time: 07/17/25-01:44:58
has monolibtic? no (libs/libkoreader-monolibtic.so: cannot open shared object file: No such file or directory)
lib_search_path: libs/?
lib_basic_format: lib%s.so
lib_version_format: lib%s.so.%s
[] Version: v2025.04-161-g70039c9f0_2025-07-15
ffi.load: rt.so.1 (RTLD_GLOBAL)
ffi.findlib: utf8proc [3]
ffi.load: libs/libutf8proc.so.3
ffi.findlib: blitbuffer
ffi.load: libs/libblitbuffer.so
ffi.findlib: archive [13]
ffi.load: libs/libarchive.so.13
07/17/25-01:44:58 INFO Starting reMarkable Ferrari
ERROR: ld.so: object 'home/root/shims/qtfb-shim.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'home/root/shims/qtfb-shim.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
07/17/25-01:44:58 INFO Oxide running?: false
./luajit: ./ffi/framebuffer_linux.lua:55: cannot open framebuffer
stack traceback:
[C]: in function 'assert'
./ffi/framebuffer_linux.lua:55: in function 'init'
./ffi/framebuffer_mxcfb.lua:830: in function 'init'
./ffi/framebuffer.lua:140: in function 'new'
frontend/device/remarkable/device.lua:186: in function 'init'
frontend/device.lua:54: in main chunk
[C]: in function 'require'
./reader.lua:151: in main chunk
[C]: at 0x00405150
01:44:58.549 default [AppLoad]: Process for "./reader.lua" finished with exit code 1 and status QProcess::NormalExit
^Cshutdown: waiting for updates to complete...
shutdown: waiting for display to finish...
shutdown: shutting down...
trim current
What does file /home/root/shims/qtfb-shim.so return?
arctic pilot
I am.
trim current
What OS version?
trim current
It does seem that they no longer ship the file executable, I'm trying to figure out which release stopped shipping it
As for if 3.20 works for what you are trying to do, I don't know
I'm not sure when they stopped shipping the file executable on the rMPP, sometime before 3.14.1.10 is all I can say
On your computer where you built qtfb-shim.so, can you run file against the so file and post the content?
arctic pilot
Sure
sean@Marvin236:~/dev/RMPP/rmpp-qtfb-shim$ file ~/dev/RMPP/rmpp-qtfb-shim/qtfb-shim.so
/home/sean/dev/RMPP/rmpp-qtfb-shim/qtfb-shim.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=334ca8f177a8ea19b4346d7de456d33d797fea3c, not stripped
trim current
For readability, next time you post console output, put three ` characters and then a newline, and then after the text three of them on their own line again
It makes things look like this
oh cool, will do
trim current
sean@Marvin236:~/dev/RMPP/rmpp-qtfb-shim$ file ~/dev/RMPP/rmpp-qtfb-shim/qtfb-sh...
Hmm, I don't see the interpreter listed, so I don't know if that's the error ornot.
Oh wait
x86-64, version
arctic pilot
x86-64...
trim current
That would be why
trim current
That shouldn't matter here
arctic pilot
its so wierd because if i do echo $CXX is returns the toolchain
sean@Marvin236:~/dev/RMPP/rmpp-qtfb-shim$ echo $CXX
aarch64-remarkable-linux-g++ -mcpu=cortex-a53+crc+crypto -mbranch-protection=standard --sysroot=/home/sean/dev/sdk_final/sysroots/cortexa53-crypto-remarkable-linux
What steps are you taking to compile the shim?
trim current
And you first ran that without the toolchain sourced?
arctic pilot
Not intentionally
trim current
I'm assuming it creates a build folder to execute on, if I remember how cmake works
Can you remove the build folder and do it again and then check
arctic pilot
hmm now it's looking at an old toolchain that I removed.
trim current
That would only be possible if you had that one sourced before you removed it
is this a fresh console session?
arctic pilot
Trying a new session just to be sure
It worked that time
I had to restart my machine
trim current
Next time you can just restart WSL itself
arctic pilot
i thought opening a new tab was a new session.
trim current
Run wsl --shutdown from an admin console/powershell and it'll stop
trim current
i thought opening a new tab was a new session.
It would be
But then again, I don't know what it's a new tab in, so maybe that will have some sort of environment carryover
arctic pilot
Same error. Guess I'll try again tomorrow.
ld.so: object 'home/root/shims/qtfb-shim.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file)
The error would be it failing to load the framebuffer
Your output may just be a warning from an executable that is being run that doesn't need access to the shim
arctic pilot
07/17/25-02:28:55 INFO Starting reMarkable Ferrari
ERROR: ld.so: object 'home/root/shims/qtfb-shim.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'home/root/shims/qtfb-shim.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
07/17/25-02:28:55 INFO Oxide running?: false
./luajit: ./ffi/framebuffer_linux.lua:55: cannot open framebuffer
stack traceback:
[C]: in function 'assert'
./ffi/framebuffer_linux.lua:55: in function 'init'
./ffi/framebuffer_mxcfb.lua:830: in function 'init'
./ffi/framebuffer.lua:140: in function 'new'
frontend/device/remarkable/device.lua:186: in function 'init'
frontend/device.lua:54: in main chunk
[C]: in function 'require'
./reader.lua:151: in main chunk
[C]: at 0x00405150
02:28:55.666 default [AppLoad]: Process for "./reader.lua" finished with exit code 1 and status QProcess::NormalExit
02:29:15.170 rm.upgrades Failed to start /usr/sbin/remarkable-setgoodroot
My guess the second failed to load is when it's trying to run luajit, and that's the one that needs it
arctic pilot
i found someone with the same issue who found a shim on discord that worked for them to resolve the error.
dude...for real
just figured it out
i feel so dumb
i was missing the leading '/' in the path
arctic pilot
I just want to say one last thing in this thread and that is to thank you all of you for your patience. Talking through it was super helpful.
simple basalt
I just want to say one last thing in this thread and that is to thank you all of...
Been following this -- does this mean you got KOReader to work on the RPP?
arctic pilot
Been following this -- does this mean you got KOReader to work on the RPP?
Yes I was able to.
simple basalt
Awesome! I gave up temporarily and put rm-hacks and zotero2remarkable_bridge on mine, but I'll give KOReader another shot sometime soon 🙂
arctic pilot
Let me know if I can help. I learned alot of lessons!
simple basalt
Let me know if I can help. I learned alot of lessons!
Likewise, thank you!
ionic spruce
Let me know if I can help. I learned alot of lessons!
what other extensions did you have out of curiosity?
arctic pilot
what other extensions did you have out of curiosity?
I only installed the extensions needed. There are a lot of extensions in the xovi extensions folder but I didn't want to introduce other issues.
ionic spruce
I only installed the extensions needed. There are a lot of extensions in the xov...
which ones did you use specifically?
ripe lake
hey all, what's up. i've been taking a beating from qtfb on 3.19+. has anyone managed to get it working? yes i want to compile it to run koreader
i'm getting some "Couldn't resolve the hashed identifier" errors on xovi/debug. i've tracked the error down to the hashed components that qtfb is trying to modify on its root-fb.qmd file:
AFFECT [[2328484894988065446]]
IMPORT net.asivery.Framebuffer 1.0
the 2328484894988065446 hash doesn't seem to exist anymore. appload's newest version has changed this hash to another in a recent commit (see screenshot). i have tried replacing the wrong hash in qtfb's root-fb.qmd file but to no avail ahahahah
there's more information on this here https://github.com/asivery/rm-xovi-extensions/issues/21
merry orchid
hey all, what's up. i've been taking a beating from qtfb on 3.19+. has anyone ma...
Perhaps you should start your own support thread, as this one is dealing with other issues...
Your first post in the #21 issue
thread '<unnamed>' panicked at src/util/common_util.rs:76:60:
called `Result::unwrap()` on an `Err` value: Couldn't resolve the hashed identifier 2328484894988065446 required by Framebuffer Root in Navigator
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[QTFB]: In main management thread.
[QTFB]: Creating socket...
fatal runtime error: failed to initiate panic, error 512643904, aborting
[QTFB]: Awaiting incoming connections to/tmp/qtfb.sock
xovi/debug: line 3: 1168 Aborted (core dumped) QML_DISABLE_DISK_CACHE=1 QML_XHR_ALLOW_FILE_READ=1 QML_XHR_ALLOW_FILE_WRITE=1 LD_PRELOAD=/home/root/xovi/xovi.so xochitl```
Suggests that you don't have either qt-resource-rebuilder or the hashtab working. (it's usually one of the first outputs: hashtab loaded (or something).
Do you indeed have a hashtab file?i do have the hashtab file, but i've seen a few errors on the xovi/rebuild_hashtable script:
[qmldiff]: Hashing: /qt-project.org/imports/QtQuick/Controls/Universal/ComboBox.qml
[qmldiff]: Failed to build hashtab from file /qt-project.org/imports/QtQuick/Controls/Universal/ComboBox.qml.
[qmldiff]: Hashing: /qt-project.org/imports/QtQuick/Controls/Universal/CheckBox.qml
...
[qmldiff]: Hashing: /qt-project.org/imports/QtQuick/Controls/Universal/VerticalHeaderView.qml
[qmldiff]: Failed to build hashtab from file /qt-project.org/imports/QtQuick/Controls/Universal/VerticalHeaderView.qml.
[qmldiff]: Hashing: /qt-project.org/imports/QtQuick/Controls/Universal/Dialog.qml
...
[qmldiff]: Hashing: /qt-project.org/imports/QtQuick/Controls/Universal/HorizontalHeaderView.qml
[qmldiff]: Failed to build hashtab from file /qt-project.org/imports/QtQuick/Controls/Universal/HorizontalHeaderView.qml.
[qmldiff]: Hashing: /qt-project.org/imports/QtQuick/Controls/Universal/MenuBar.qml
...
20:49:40.305 rm.network.notifications Connected to notifications server (onStateChanged /home/runner/work/xochitl/xochitl/src/notifications/src/notifications.cpp:206)
20:49:40.377 xofm.libs.toolbar No tools to move to the foldout menu (moveNextToolToFoldout /home/runner/work/xochitl/xochitl/src/xofm/libs/toolbar/src/toolbarprovider.cpp:276)
20:50:09.412 rm.upgrades Failed to start /usr/sbin/remarkable-setgoodroot
[qmldiff]: Processing rules.
[qmldiff]: Hashtab saved to /home/root/xovi/exthome/qt-resource-rebuilder/hashtab
I saw that, but I don't see that you have verified, that you indeed have a working hashtab? ll ~/xovi/exthome/qt-resource-rebuilder output?
merry orchid
Great. Then I suggest, that you temporarily remove qtfb.so and appload.so, so you only have xovi and qt-resource-rebuilder. Then running xovi/debug you should see that the hashtab is loaded.
ripe lake
yup, can confirm that removing qtfb.so, shim, and appload makes xovi run as expected
even with rm-hacks-qmd
i'll try with a qtfb.so file that was sent to me
i have a meeting rn but i'll be back with updates
steep cedar
@ripe lake I am using qtfb on 3.20 fine. It's built from the latest code on github
ripe lake
<@153367952463364096> I am using qtfb on 3.20 fine. It's built from the latest c...
when you rebuild your hashtable do you get those failures i mentioned?
i'm thinking there may be something borked on my rmpp
steep cedar
when you rebuild your hashtable do you get those failures i mentioned?
Oh wait, OK, I see
Your tablet is fine. Are you on the latest version of qt-resource-rebuilder?
ripe lake
i think so, i'm using a locally compiled qt-resource-rebuilder (with the remarkable toolchain)
let me clean everything and rebuild the extensions
steep cedar
Ok - from the latest commit on GH?
Be sure to update the subrepository
git pull; git submodules update --remote
ripe lake
yup
steep cedar
Qmldiff's ABI rarely changes. You might simply be running a weird "mixup" version of the latest C code and outdated rust
Plus I don't see the line "Set system version to..." in your logs
That'd indicate an outdated qmldiff
ripe lake
qmldiff's at commit bb19e820d66bba9a7e45f76ae7d1f1d668dd0647 from Thu Jul 10
steep cedar
That's OK
Run cargo clean in the qmldiff subfolder just to be sure
Yeah... I'll try resolving this mess by merging qtfb into appload
Maybe even today 🙂
steep cedar
Plus my documentation is still garbage 🤣. I'm not a native speaker so docs are a pain and it takes me a long time to write them
steep cedar
i have no clue how you make sense of qml tbh
It's not the worst
ripe lake
Plus my documentation is still garbage 🤣. I'm not a native speaker so docs are ...
maybe i can help w that
steep cedar
I had to figure it out if I wanted to write a parser
ripe lake
i went down ur code's rabbit hole
steep cedar
maybe i can help w that
That'd be super welcome ❤️
ripe lake
i have a few friends who are BEGGING me to get this working so i can write a tutorial
they really want to read manga (.cbz) natively on the rmpp
steep cedar
i went down ur code's rabbit hole
I'm so sorry - I hope you didn't lose much sanity 😅
ripe lake
oh i did
but it's fine
i had a blast
i'll reinstall xovi on the rmpp just to make sure
ripe lake
are there any dirs that i should remove besides the /home/root/xovi one?
steep cedar
Nope
ripe lake
aight
steep cedar
Everything is in that folder
ripe lake
the xovi/stock always tries to remove a xovi.conf file in /etc
rm: can't remove '/etc/systemd/system/xochitl.service.d/xovi.conf': No such file or directory
steep cedar
Yeah. That file is in a folder that's a tmpfs mount
steep cedar
That's on purpose
It xovi breaks everything and the tablet reboots, it defaults to stock
That's a safety measure
ripe lake
ahhhhh
makes a ton of sense
if we do umount -l && mount -o remount,rw / to make it permanent it can bootloop the device is what you're saying
interesting
steep cedar
Yes
Please do not do that
On the pro you will be guaranteed a bootloop
Actually, no, it might still work, but please don't try it 😅
On the rMPP, /home doesn't exist until you enter the password for the first time after a reboot (device encryption)
So /home/root/xovi won't be reachable
ripe lake
ah that's one thing i've noticed - my device isnt encrypted
steep cedar
You have the pro?
steep cedar
That's not possible I think
ripe lake
i mean i get no password prompt like ever
ripe lake
what if rebuild_hashtable doesn't work w/o a password?
steep cedar
It does
That is not the problem. The only way to get that error you reported is if the parser fails
So my parser is not fully compliant
Which sucks 😅
ripe lake
the xovi.so is the version i just built locally, and the xovi.so.old is the one i got from the releases in gh
mine is 33% larger...
steep cedar
Hmm. Maybe the config is different
xovi.so itself matters the least here
If you get any response from qt-res-rebuilder, it's fine
(and you don't get bus errors due to inckrrect alignment of the stack 😉 )
ripe lake
let me rebuild the hashtable
steep cedar
(and you don't get bus errors due to inckrrect alignment of the stack 😉 )
ripe lake
[qmldiff]: Failed to build hashtab from file /qt-project.org/imports/QtQuick/Controls/Universal/ComboBox.qml.
[qmldiff]: Failed to build hashtab from file /qt-project.org/imports/QtQuick/Controls/Universal/VerticalHeaderView.qml.
[qmldiff]: Failed to build hashtab from file /qt-project.org/imports/QtQuick/Controls/Universal/HorizontalHeaderView.qml.
hmm still getting these failures
root@imx8mm-ferrari:~# xovi/debug
[qmldiff]: Set system version to 3.20.0.92
[qmldiff]: Iterating over directory /home/root/xovi/exthome/qt-resource-rebuilder/
[qmldiff]: Hashtab loaded! Cached 11044 entries
[qmldiff]: Configured hashtab rules.
debug: 2025-06-23T10:44:13Z heads/releases/3.20-lillipup 782f1ce
alright debug seems to be ok
steep cedar
```
[qmldiff]: Failed to build hashtab from file /qt-project.org/imports/QtQuick...
This is a high priority bug. I'll try to fix it today
ripe lake
do you have any idea as to why it might be happening?
steep cedar
Yes
ripe lake
and how can i help
steep cedar
If you want to help, you'd need to delve into the file "src/parser/qml/parser.rs" and you'd need to have access to the qml files of xochitl (which I can't reveal how to retrieve - sorry 😦 )
ripe lake
i already went into that file teehee
but yeah, the qml files i have no clue how to get
i thought it was going to be something like this
ripe lake
bc i saw you changed the apploader qmd to remove this hash
no worries
youare helping though, it's your code we rely on hahaahah
dw
i'd be happy to test it out though
steep cedar
Thanks 🙂
ripe lake
since it's clearly reproducible in my dvice
steep cedar
Probably on mine too. I just missed it
ripe lake
[qmldiff]: Hashing: /qt-project.org/imports/QtQuick/Controls/Universal/impl/CheckIndicator.qml
20:40:48.001 default Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
20:40:48.108 default Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
20:40:48.118 default Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
20:40:49.051 rm.network.notifications Connected to notifications server (onStateChanged /home/runner/work/xochitl/xochitl/src/notifications/src/notifications.cpp:206)
20:40:49.079 xofm.libs.toolbar No tools to move to the foldout menu (moveNextToolToFoldout /home/runner/work/xochitl/xochitl/src/xofm/libs/toolbar/src/toolbarprovider.cpp:276)
20:41:18.411 rm.upgrades Failed to start /usr/sbin/remarkable-setgoodroot
[qmldiff]: Processing rules.
[qmldiff]: Hashtab saved to /home/root/xovi/exthome/qt-resource-rebuilder/hashtab
##############
Found expected output. Killing gui process and restarting systemd service.
shutdown: waiting for updates to complete...
shutdown: waiting for display to finish...
shutdown: shutting down...
Now starting the systemd xochitl service back up...
root@imx8mm-ferrari:~# xovi/debug
thread '<unnamed>' panicked at src/util/common_util.rs:86:60:
called `Result::unwrap()` on an `Err` value: Couldn't resolve the hashed identifier 2328484894988065446 required by Framebuffer Root in Navigator
[QTFB]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
In main management thread.
[QTFB]: Creating socket...
[QTFB]: Awaiting incoming connections to/tmp/qtfb.sock
fatal runtime error: failed to initiate panic, error 27534256, aborting
xovi/debug: line 3: 1636 Aborted (core dumped) QML_DISABLE_DISK_CACHE=1 QML_XHR_ALLOW_FILE_READ=1 QML_XHR_ALLOW_FILE_WRITE=1 LD_PRELOAD=/home/root/xovi/xovi.so xochitl
root@imx8mm-ferrari:~#
yeah, qtfb makes xovi not start
i tried using @gilded sonnet's pre-compiled qtfb.so +shim files to see if there's any difference but no, not at all
i tried adding a password just to see if it magically fiexs things and sure enough it doesn't
steep cedar
I'm not at home
ripe lake
omg sorry to bother u when you're not at home
ripe lake
you're a god
steep cedar
the error persists
The qtfb one?
ripe lake
The qtfb one?
yep. but hashtable is being built corectly it seems
the failures have disappeared
steep cedar
The thing is, I can't see how that particular hash would be missing
ripe lake
that's the main UI hash right?
steep cedar
Yes
ripe lake
i figured... makes no sense
bc appload works
i'll try to get you the entire logs of qmldiff 1 sec
steep cedar
I can confirm that missing hash is in that log
Please delete that file now, though 😅
ripe lake
what the hellllll
steep cedar
Can you check your DMs?
ripe lake
yup!
ripe lake
after a lot of help from the amazing @steep cedar everything works!!!!!!!!!! i'll write a how-to as soon as possible
trim current
Just to remind everyone, please make your own threads instead of using existing ones for support.
