First, thank you.
Using your instructions I was able to locate the Firefox profile and copy the contents into a text file, which I saved to my external hard drive. You aren't kidding; it's hard to read. But it's a lot better than nothing! I'm so grateful both for your instructions and for my having kept the computer running in the hopes that data was in there somewhere. FYI, I didn't see "USERID" (is that a placemat for my name or something?) But I explored for a while and when I saw the .mozilla folder I followed the rest of your path and there was the sessionstore.js file! Nice. I thought I had done this before and found nothing, but possibly that was before I selected "show hidden files". So, mission accomplished on perhaps my top priority.
Now moving on to your next instruction, I first misread the $ for an S, and got the response...
S: command not found
Wow, that's a subtle difference between those two characters! I have to look close to tell them apart. I should have known, because even being a newbie I've seen the "dollar sign" precede many commands. However I also seem to recall reading somewhere that you don't have to type that symbol. (Is that true?) At any rate, I also tried the 'pidof' command without typing anything else and that also appeared to be invalid. Now I'm going back to my broken computer to use the proper syntax. I want to try those related to Firefox first because if I can get my browser back I can copy and paste the info you seek, rather than switch back and forth between two computers and hope I remember and copy correctly.
OK, several questions about what just happened. First, does it matter whether I launch the terminal by right-clicking the desktop or by using the menu? In the latter case the terminal opens with...
and from the desktop it opens with...
Next, I tried the line...
$ pidof firefox (from both locations) and got...
$: command not found
This would seem to answer my question; I probably didn't need to type that $
, right? Is that because it was already displayed when I opened terminal?
Next I typed just...
and the cursor moved down to the next line, blinked for a few moments, then stopped blinking, stayed as a solid black rectangle, and no information was displayed.
I wasn't sure if I was supposed to enter your second line here, the "kill" line, so I waited for maybe half a minute but after nothing happened I entered that line and (as I recall) got the same result... the cursor just moved down another line.
Next, after closing and reopening the terminal (from the menu) I entered...
sudo inxi -F
sudo: inxi: command not found
Am I doing something wrong? I'm intrigued by the idea that some process is running, preventing Firefox from launching; that sounds plausible to me. And I'm glad to hear this behavior isn't typical for Firefox on Linux (and live doesn't make it any more susceptible to crashes?).
Also, I was so relieved after reading, "I see you're running "live" mode so far" to read "That's a good idea."
My gut was ready for another punch because it seems I'm often being told I can't do whatever it is I'm trying to do, or that something's not
a good idea.
Any further help is appreciated. If you can give me some alternate commands -- and especially if we can first get my Firefox running again so I can go online from the broken computer rather than this awkward two-computer juggling thing I'm doing -- I'll be happy to report what I find.