-
Notifications
You must be signed in to change notification settings - Fork 208
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
pi-apps won't launch #2525
Comments
Hello there 👋 Please respond as soon as possible if a Pi-Apps maintainer requests more information from you. Stale issues will be closed after a lengthy period of time with no response. |
Are you running this command in the console, or with ssh or something? |
After installation I first tried to run from the Desktop using the launch icon. When the GUI didn't come up, I started from the shell to see if any errors would appear, with the results posted above. So while I agree the error points at display/screen there seems to be also unrelated shell parsing errors. I did try to set $DISPLAY=:0.0 manually to but it didn't help. |
Yeah you would get similar display-related errors from trying to run any GUI program in the shell. |
that's what i did, i started pi-apps in a terminal within the desktop environment. i thought that's what you meant by shell. i don't have any problems starting any other GUI application that way (i tried e.g. a webbrowser to check), only pi-apps. |
Please test on a fresh piOS image and report back (image dated December 11th 2023) https://www.raspberrypi.com/software/operating-systems/ |
since the last pi-apps update it works. i didn't investigate further what changed. i didn't change anything in my system (no packages removed, added or updated) |
Let us know if the problem happens again. |
Confirmations
What happened?
after running pi-apps various errors appear and gui does not launch
Description
various error messages at startup
What are your system specs (run the following command in your terminal)?
(Recommended) Error log? Terminal output? Debug messages?
The text was updated successfully, but these errors were encountered: