wget http://hastebin.com/raw/fotacezeha -O ~/.i3/config


I can't get out of this box again. Ok so do that and then do the command in the previous post (which will pastebin the config file so I can have a look at it)

edit: I've made a small change to the file so the url has changed. 

Installed pastebin.

Sorry, it's come back with:

Bad API request, invalid api_dev_key

Fuck it, skip that for now. Just re-wget the edited file.

(There was an errant tab in the first one that shouldn't have broken things but may have)

I did it and it claimed to have overwritten it successfully, but it's still opening an error message with the same errors in line 153 and 160.  I can open the file for editing cut & paste the code in directly?  I really really appreciate your help, but don't sacrifice anything else you should/would rather be doing. Sx

Yeah, try that.

blank the file first:
 

echo "" > ~/.i3/config

Then just open it up in a text editor and paste the text from: http://hastebin.com/raw/fotacezeha

And you're welcome, it's no bother.

 :-{)  (hug)

It boots to a blank screen with a mouse cursor and stays like that.  If I then hit Win+Shift+e I get the 'exit' dialogue and if I click 'yes' to exit I get the error screen with the two errors on lines 153 and 160.

I'll make that pesky cursor disappear while I'm thinking on.

Edit: Unclutter has had a grump about installing on my tiny wee screen (see attached photo).   Not sure whether that means it's installed or not.  I'll press on.

Edit 2: With that unclutter line in the .i3/config file it boots straight to the error message. The cursor is still there anyway.  I reckon unclutter didn't install because of that business about the screen.  I'll take the line out back out of the i3 config for now.

I'll look into getting unclutter working on small screens.

Other than that not working, is it launching the terminal when it starts, now?

Not absolutely sure, because it's an absolutely blank screen bar the cursor, but yeah, I reckon it's probably the terminal.  The screen does blank after (I think) 10 minutes, which suggests it is the i3 console.

It *should* be running the script. And it *shouldn't* be blanking. I'll have a think.

Owt I can do in the mean time?  I managed to extract the contents of the config file (not easy without a gui) and there were no hard breaks that I could see.

Just double check you've installed xfce4-terminal. Oh and run 'xset q' and give me the output.

xfce4-terminal is latest version (it says) and the result of running xset q is attached.

Ok, do this in terminal:
 

xset -dpms;xset s off

And then run:
 

xset q

Again immediately after and give me the output again.

We've got two problems now which sort of overlap.

Firstly the stuff in i3's config clearly isn't being run since if it were then you'd have a fullscreen terminal with your script in it.

Secondly, the screen is still blanking. The command to prevent that is also in i3's config so it may be the same problem.

Doesn't make a lot of sense since i3's config is clearly working because you no longer have the i3 bar.

Is there any chance you could open it up to ssh so I could have a poke around?

Xset regurgitation attached.

SSH is apparently enabled by default under Raspbian, which is a good thing as when I navigate to it through raspi-config I just reach a blank screen  & it's not clear how to enable or disable it.

What details do you need to access it?

I managed to log into the Pi on my network through SSH using PuTTY.  Also attached, the info received from the Pi when I logged in through SSH.

You'll need to forward port 22 to the RPi IP on your router.

Then give drew your internet connection IP and RPi login details.

Thanks Ant.  I don't know whether there are any security implications for my home network, so I'll PM the details to Xen.

Yeah, don't give those out to anyone else, and once he's done close port 22 again on the router. It's a common port to try and access.

Yeah, what Ant said. It'll try to start X when I log in but we'll see if I can get around that.

The SSH output is helpful though as it reveals that i3 is *still* erroring on those innocuous lines. I suspect that if I can fix that then stuff should start working.

Xset clearly isn't doing its job though so I'll have to disable dpms via xorg instead, which is fine (easy to do myself via ssh, much harder to explain how to do since it depends a lot on what's already there).