I didn’t go out of my way to try anything specific, no. I was prompted for an update, hit yes to restart and then, to my knowledge, I didn’t look at the thing for over a week and came back to it like this.
EDIT: As an aside, in the full installer, is 2015.06-01 the latest or is it RC1/2 or 3?
I don’t see anything immediately wrong with your logs
It would be wonderful if you could run the following commands:
sudo journalctl | paste-log
dmesg | paste-log
It’s 4am here, so I must sleep, but I will check this tomorrow, and I kindly request, you do not reinstall yet so we can help future users should we discover an issue with your system
Sam
The 2015.06-01
If it will ultimately help, I will wait on reinstalling. Here is the output from those two things – both failed.
“osmc@osmc:~$ sudo journalctl | paste-log
mktemp: failed to create file via template ‘/tmp/tmp.XXXXXXXXXX’: Read-only file system
-bash: $tmp: ambiguous redirect
http://paste.osmc.io/ohewiwukeh
osmc@osmc:~$ dmesg | paste-log
mktemp: failed to create file via template ‘/tmp/tmp.XXXXXXXXXX’: Read-only file system
-bash: $tmp: ambiguous redirect
http://paste.osmc.io/yifuvopude”
Somehow your filesystem has got corrupted which has left it in read only mode. Try one of these to fix it. Either
a) Hold down shift during boot to go to the recovery console, when the fsck is finished (it might ask you some questions) type exit
or
b) From ssh run
sudo fsck /
Then reboot when finished.
Note: If you were running RC2 or earlier with particular SD cards (including the Samsung EVO) on a Pi 2 there could be significant file system corruption that might require a reinstall. (Let us know the model of your SD card in case this is your issue) This problem was fixed in RC3 and later.
So, I can’t be sure if I was running RC2 or earlier when all this happened. I was checking for and installing updates pretty frequently, however. I was not able to get it to go to the recovery console by holding shift, so I did it via SSH. It asked me several things to fix and I said yes to all of them. It then said it was rebooting, but my screen just kept flashing the frown face. I removed power, plugged it back in and got that again. I then tried the shift+ctrl to update after it fixed all those things, and got past the “Searching for packages thing …” but then it crashed saying there was an unknown error trying to install updates and I’m back to the frown face.
At this point, I believe something has gone catastrophically wrong. Is there anything else ya’ll can get from this, like logs and what not?
I think I’d say go ahead and rebuild your system. I’ll offer thanks from the dev team here for your assistance in providing relevant info so that we can attempt to prevent future occurances of the issue. Hopefully we’ve also provided you a bit of insight into digging into the system beyond the GUI since the spirit of the Raspberry Pi is based in education 
Thanks again and enjoy!
Yeah, it’s at least given me a basic understanding how to get into that stuff. Also I know how to SSH into my seedbox now, so that’s neat.
Anyway, one last thing is that the SD card I used was a Kingston 4GB N0043-012/A00LF, according to the card.
EDIT: Didn’t want to bump this up with another post, but I’ve reinstalled on the same card and everything seems to be working quite well, so we at least know there was nothing faulty about the card, just in case anyone comes back to this topic.