-
Notifications
You must be signed in to change notification settings - Fork 97
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
Unable to open display #33
Comments
@nassafellow this just pops up because of the edits to I assume you have your pi set to autologin to the console? |
Worth noting that the file above had to be created by me because it wasn't there before. Please tell me I'm close to finishing the software bit. |
@nassafellow what does your log file say? Did you install everything? (openbox, lightdm, x11-xserver-utils, etc...) |
how do I find the logfile please, forgive me but I'm new to all of this and still learning. I did install everything - had to use a few workarounds that people found in the issues section to get where I am e.g. the -r requirements - only really faced trouble at the xnitrc part but as you can see it is all there. Is a cache missing or something? |
In your first screenshot, it specifies a log at |
any suggestions on what I should do? |
I'm not seeing anything that jumps out to me - (also all the screenshots are slightly overwhelming 😄 ) If you don't want to wait, my last ditch effort would be to re-flash the SD card and try going through the setup steps from scratch. I restarted my pi after step 9 just to make sure everything loaded well before adding the spotifypod specific stuff. |
Hmm ok I'm retracing my steps. Where did you put the website link please - it doesn't say where to type it in. |
I'm still so stuck I just keep getting the x set unable to open display, and the program keeps crashing. :( |
Did you connect a display to your raspberry pi? Does this show anything? If I ssh into my raspberry, I get the same error (if I remember correctly). In my case the auto login session on the display has the display variable set automatically. But if I create another session via ssh, it doesn’t have this display variable and therefore this issue appears. There is a better and more detailed explanation for this issue but I imagine that is enough information for now. If something happens on your display and you enabled auto login, I don’t think this is something to worry about. |
Please help, I don't know what to do... :(
Please break everything down since I am new to all of this and am struggling with both software and hardware
The text was updated successfully, but these errors were encountered: