-
Notifications
You must be signed in to change notification settings - Fork 14
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
Text is blank on iOS Safari/chrome #2
Comments
What version are you using? Buster (Umbrel) or Bullseye (Citadel)? |
Citadel |
Could be related to this: tsl0922/ttyd#798 What iOS version are you using? |
Yeah the issue looks similar, I’m on 15.2 |
It's been over a year since I could try building it from master, though I don't really like that approach. What do you think, @AaronDewes ? |
That would mean reverting some changes for bullseye in |
Hey @AaronDewes, I've made a new build with the last ttyd (on master). Could you try it on Citadel and confirm that the issue is fixed? If so, I will create a new tag and close the issue. |
I've published the new version to Citadel, but can't test it myself, @refazi it'd be great if you could try with the update apps button and waiting a few minutes. |
I updated twice, the version in the App Store shows as 1.1.1, still have the same issue. |
Can you try to SSH in and run |
@AaronDewes is the SHA256 in app.yaml the correct one though? I am trying to run that container on my Umbrel and can't. This one, I mean runcitadel/apps@edf35a0 |
Thanks, that was the problem. Looks like I had another sha256 copied and pasted that by accident |
The app doesn’t seem to start, the docker log on syslog says “manifest unknown” |
I think this is getting a bit confusing now, with so many versions flying around. I've created version 0.1.3 of lightning-shell and submitted a pull request to @runcitadel. Ideally we will be using tagged versions, not builds from master. |
I still see an issue, the COI toner in version 0.1.3 doesn’t come up, I see the following error on the container log: |
Hmm, that is strange, that error should show up when you try to run a container built for the wrong architecture - like running the amd64 container on the Pi. But the SHA in https://github.com/runcitadel/apps/blob/main/apps/lightning-shell/app.yml matches the SHA of the ARM64 build on https://github.com/ibz/lightning-shell/pkgs/container/lightning-shell/13252298?tag=v0.1.3-bullseye-slim . Is there any other place where you are storing the image reference/SHA, @AaronDewes ? Or can it be that he did not update to the last yml? Or ... are you running Citadel on something else than Raspberry Pi @refazi ? Other than that, I don't understand how this would happen. |
Yeah it’s running on x86, can you build it for that arch as well? |
Yeah, v0.1.3 was built for x86 as well, but I wrongly added the SHA256 of the ARCH build (thinking Citadel is only used on Raspberry Pi, silly me). I think @AaronDewes fixed it by now. |
I fixed it, but even after my PR to add a missing dependency, it's still broken. I'll debug it further |
Btw I just installed the umbrel version via the umbrel 0.4.11 release and I have the same issue |
Yes, Umbrel has the old version. I submitted to them before the fix. :) |
@AaronDewes I just had a look at your app.yaml, it seems like you are using a build from master, that may be broken (master is sometimes broken). You should be using v0.1.3, which works fine on my Umbrel. |
Ha! I found something... I think it's only the Bullseye image that is broken ( I'll investigate further and come up with a fix, but before that, to summarize...
As a temporary fix:
|
Sure, I'll try to go back to buster. |
@AaronDewes I think the issue was this after all 4c53e09#diff-5be359434de5b83c3988bbf1494c1dab5bb8110cf7141650fec0e06e02d4b1dcR102 Should be fixed now in master. I'll make a tag soon also. |
BTW, v0.1.4 is released. I just submitted it to Umbrel. Could we add that to Citadel as well? |
Updated to citadel 0.5.20 and 0.1.4 seems to be there. |
@refazi Thanks for double checking! Too bad... OK, we'll leave this issue open then for now. |
When using mobile browser like safari or chrome in iOS, the text is blank - looks like the characters are colored the same as the background.
The text was updated successfully, but these errors were encountered: