Nathaniel van Diepen
Nathaniel van Diepen
We would want a solution that works for both installs in Toltec, as well as users who install manually.
It would probably make sense to just try to pull down the address definition for the specific OS version, instead of the full list each time. This would also need...
Fixed the issue, but not with rm2fb right? You are no longer blocked, but no longer using rm2fb.
@Jayy001 @X-Ryl669 are either of you using Oxide?
> I'm not, no - the list of packages I'm using are in my first comment (no ddvk hacks either) Well, it does have tarnish in the list, which is...
For those of you not in the discord:  It seems a lockfile was added that doesn't play nice with rm2fb yet. Some development will need to be done to...
It should probably be easy enough to add some extra handling on the client side to catch attempts to open/lock `/tmp/epframebuffer.lock` and just noop the calls to get it working.
> No, it doesn't work either. You might have rm2fb to run with the updated offsets, but it'll fail later on. > > Try with tarnish and oxide for example....
> Indeed, that was it. I've removed the "chroot" in the `flags` key of `/opt/usr/share/applications/xochitl.oxide` then re-enabled tarnish (`systemctl enable tarnish` then `systemctl start tarnish`) and it works correctly! Interesting,...
> Would someone be able to verify this on 3.1 as well? If the oxide chroot is the issue, we can close this and open a new issue on Oxide...