-
Notifications
You must be signed in to change notification settings - Fork 205
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
New install of eDEX-UI provides many errors #1654
Comments
The second error only happens after typing letters. |
@Botspot @ryanfortner Please check out this link: GitSquared/edex-ui#313 (comment) |
I think that advice there is outdated, as since then the eDEX-UI developer was able to get ARM builds running. |
Strange. The two recent commits that triggered an update for you were not intended to make any functional changes to eDEX-UI's behavior. eDEX-UI runs fine for me on armhf, and I don't recall there being further problems on arm64 after @GitSquared solved them all last year. |
For some reason though, it does not run for me. :( |
@GitSquared It's so nice of you to help! The exact model would be the Raspberry Pi 400 Rev. 1.0
|
Haha! Happy April 1st to you too. Maybe you could list more info:
I unfortunately do not have Pi hardware to test on (and eDEX is archived/unmaintained now) so I'm not sure how much of a help I can be here, but I'll try a few things. |
Glxgears info command:
chromium:
|
I've built a new version with basically all the upgrades to I am not sure how likely it is to work for you but looking at the Chromium debug output above I think there's some chance that it might. Here's the download link (gDrive, 100mb or so). I can send you the patch from the current archived git tree of eDEX if you want to attempt a compile directly on your Pi, which might have more chances of working... 🤞 |
What I am more concerned about, is getting a hardware checker on the install of Pi-Apps and building from the git tree of eDEX if it's on a 400. Could you send me the patch? |
Here's the diff from the latest master. Compile instructions
|
@Sussy-OS you should look at your install you do NOT have GPU hardware acceleration working. LLVMpipe is a multithreaded cpu software renderer from mesa. @GitSquared I would not look into this more until Sussy-OS fixes their install I suggest testing out piOS on a fresh SD card to verify that it is working there. the output for |
I will do a fresh install, but how will I fix it on my current install? I have a lot of important things on here |
that depends on what is causing the issue. it could be multiple things... maybe you are missing the libraspberrypi packages? or another possibility is you have installed a version of mesa not from the raspberrypi repos that doesn't include the raspberrypi drivers I have also found this posted on a forum from this year https://forum.endeavouros.com/t/rpi-4-eos-is-using-software-renderer-llvmpipe/24579/5:
if this is true and you have |
you should replace
with this
don't make a new line |
Okay, will do. Thanks again! :) |
@theofficialgman Errors persist. :( |
Same ones. (Sorry for close) |
In Chromium, try going to the |
We already got the output from glxinfo and know the llvmpipe cpu renderer is active. By guess is the libraspberrypi packages are uninstalled, but sussy-os hasn't checked |
@theofficialgman @Botspot I just installed eDEX, and running from terminal gives me this:
So I ran without seccomp-filter, but it just hung (unless it was just taking a super long time to load):
^ I killed it after a few minutes This is my
I'm on armhf. |
Which packages to check? |
@Sussy-OS |
You might need to enable the KMS driver in config.txt. A quick google search or the raspberry pi docs should help. |
1 similar comment
You might need to enable the KMS driver in config.txt. A quick google search or the raspberry pi docs should help. |
they already tried both kms and fkms |
Yeah, I did, so idk whats the matter. Btw, im a he. |
@Crilum sorry for the very late answer, I missed this ping somehow. I provided the instructions earlier, see here. |
@GitSquared Sorry, this is probably a silly question, but how do you apply the patch? |
@Crilum there are no dumb questions! You can paste the patch to a file in your git clone directory (e.g |
I like that answer! Once, I asked a question, and somebody called me dumb (when I was younger.) and it made me realize: the reason to ask questions is to get answers. Answers to questions so that you know more. |
@GitSquared So I did all the steps, but on final build it throws. Maybe something to do with using
|
Ok, the fix for that is to add "variables": {
"openssl_fips" : "0"
}, to the top of source: https://stackoverflow.com/questions/69882740/how-to-rebuild-epoll-package-in-electron |
So, with the new build, I still have the errors @Sussy-OS was having:
Here's the AppImage: https://drive.protonmail.com/urls/YJ5B1VZ8V0#HVK2xL2rWIf9 |
Damned. The MESA errors in the log could point to a root cause... Now that you have edex with the latest version of chromium embedded, could be a good idea to debug with chromium and its helpful |
See #1654 (comment) |
For some reason, |
What was the result of this issue? |
@Botspot It never really got resolved, eDEX-UI still throws on my system (and GPU acceleration does work), even after building myself with the newer electron version. I wonder if this also has something to do with the electron bug electron/electron#31091.. |
@GitSquared I am actually running RPiOS arm64 right now so I can test your AppImage, and see if it works. |
so you got video_decode GPU accelerated in Chromium but edex crashes? Fwiw the patch made it work on my arm64 apple silicon laptop. |
I started eDEX (your appimage) about 20 mins ago, and it's just hung (it never loaded the UI):
Is the problem that |
no that looks unrelated, likely a mismatch between the precompiled version and your cpu architecture. I'm afraid I can't provide you much more than the patch and compilation instructions I've previously sent. I'll let you guys figure out what this means in the context of this repository if it still can't run for the majority of users. |
@Botspot For me, it still does not work, even after a reinstall (that is why I was asking about the new setup yesterday) and I wonder if my Pi is the problem.. |
This may be solved now that electron 18.2.4 has been released. |
@Crilum I have seen this error before. its a build script error (at least with newer electron) this is a script specific to tabby, but it builds the natives, something that I guess the compilation instructions from gitsquared didn't do https://github.com/Eugeny/tabby/blob/master/scripts/build-native.js either that or you skipped a step. again though... do we (pi-apps) really want to do maintenance and upkeep on eDEX-UI when GitSquared does not want to do it anymore and nobody has forked? |
@theofficialgman I was just using @GitSquared's AppImage, I didn't build the arm64 one. |
so you got video_decode GPU accelerated in Chromium but edex crashes?
Fwiw the patch made it work on my arm64 apple silicon laptop.
On May 18, 2022, GitHub ***@***.***> wrote:
@GitSquared <https://github.com/GitSquared> I am actually running
RPiOS arm64 right now so I can test your AppImage, and see if it
works.
—
Reply to this email directly, view it on GitHub
<#1654 (comment)-
1129628072>, or unsubscribe
<https://github.com/notifications/unsubscribe-
auth/AF24SIIGXSHRDCWTOQALWCTVKSF5DANCNFSM5SF2POJQ>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I don't think I ever got |
Oh wow GitHub posted my comment yesterday even though I answered the email months ago. Sorry for the noise! |
Oh haha 😂 |
Confirmations
What happened?
eDEX-UI provides enough bugs for it to not work
Description
Baicically, eDEX-UI never worked for me before, so with the new update, it is finally working.. with a lot of errors. Here are two errors I have recorded below.
edit: the following error happens after clicking on any of the 'empties'
![2022-03-31-115141_1920x1080_scrot](https://user-images.githubusercontent.com/98842253/161097505-6218457c-e230-44e2-9bec-f7f7f75606da.png)
What is your operating system?
Raspberry Pi OS aarch64
(Optional) Error log? Terminal output? Debug messages?
No response
The text was updated successfully, but these errors were encountered: