search

dupontgu / retro-ipod-spotify-client

The software that powers the sPot: a 4th generation "Click Wheel" iPod with a full Spotify client.
Apache License 2.0
892 stars 90 forks source link

Unable to open display #33

Open nassafellow opened 3 years ago

nassafellow commented 3 years ago

16186091114226054285710309907953 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

trystendsmyth commented 3 years ago

@nassafellow this just pops up because of the edits to .bash_profile The console doesn't have a display set, so it outputs this in response to the xset commands, but it's not an issue. The issue here is that xserver won't start.

I assume you have your pi set to autologin to the console? Did you edit xinitrc per the instructions?

nassafellow commented 3 years ago

16186132135743970276966403491320

Yes it logs into auto console straight away.

I didn't get to put in the long authorisation website in anywhere though. It wasn't clear where I had to put it. I've filled in all the details for it though.

nassafellow commented 3 years ago

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.

trystendsmyth commented 3 years ago

@nassafellow what does your log file say? Did you install everything? (openbox, lightdm, x11-xserver-utils, etc...)

nassafellow commented 3 years ago

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?

trystendsmyth commented 3 years ago

In your first screenshot, it specifies a log at /var/log/Xorg.0.log. Might be worth taking a look in there and seeing if it has any useful information.

nassafellow commented 3 years ago

IMG_20210417_002656

nassafellow commented 3 years ago

Wait, just seen there's more... 16186157714647841832305915771548 16186158038687358189247630313846 16186158358966420887258237558368 16186158643492482056008355922313 16186158877641907410975733800792 16186159116442803970550684861377 16186159301271760163116541731566

nassafellow commented 3 years ago

any suggestions on what I should do?

trystendsmyth commented 3 years ago

I'm not seeing anything that jumps out to me - (also all the screenshots are slightly overwhelming 😄 ) Some places to check (but I wouldn't output everything here unless you see a specific error) are/var/log/lightdm and ~/.xsession-errors. If there's nothing of note either place, I'd recheck that you did all the steps exactly as specified in the README and restart with only your monitor plugged in. If it still fails to run the GUI, I might check with a different display to see if that's an issue. Beyond that, my troubleshooting gets weak and you might want to wait on a Linux guru.

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.

nassafellow commented 3 years ago

Hmm ok I'm retracing my steps. Where did you put the website link please - it doesn't say where to type it in.

nassafellow commented 2 years ago

I'm still so stuck I just keep getting the x set unable to open display, and the program keeps crashing. :(

tomaculum commented 2 years ago

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.