I was a bit surprised to hear about it but I have so much to learn anyway that I couldn't let the fact I hadn't heard of it be too big a factor in my thinking.
I make extensive use of the tools used by Synaptic for basic research on packages in Debian. I use them on the cli because they are easier and more convenient to use there. You can open a number of queries in tabs in the cli so you can compare the depends and descriptions of different packages whereas you can only see one at a time in the gui.
These are all apt-cache tools like apt-cache policy (installed or not and what versions are available), apt-cache show (the description and depends and what repo it is in and so forth) and apt-cache search.
Using those it is also easy to open several tabs of a web search on a web browser and copy/paste package names or the home pages for different applications that are listed in any of those tools.
Pretty good way to get my aging brain confused and bewildered.
One reason I have so many installs is that I can dedicate different installs to be used for particular types of application installs. Appears that I am trending, once again, toward security related packages.
What OS is installed on that laptop?
Shouldn't be too hard to get past that Admin password. It is a really good security tool but can be bypassed by people that know how. Should be in the bios and be able to be simply disabled so that you could keep a record of that password and enable it again if you want.
It is a bit worrying that the system was that screwed up. Would be a bit easier to understand in a desktop than a laptop, at least for me.
Did the laptop shut down due to power failure (dead battery or something) or have any power related problems right before this behavior started?
It is pretty weird that bios settings simply changed on their own. Swap disappearing is equally strange as is the lack of grub being not installed in the things "protective" mbr.
When installing did you use the MSDos partition table or GPT?
GPT is really better in a lot of ways. It is also what modern (Uefi) bios is happiest with and it works fine with 'legacy boot' (fake mbr).
My desktop is uefi and the internal drives are out of the old Dell (bios) box so they are still MSDos partition tabled. With the problems that I have currently with one of the drives being defunct I am working from an external drive mainly. It is a GPT setup but still booting with the fake mbr (bad idea to mix the 2 boot systems on the same box - causes problems - I read the warnings and did it anyway for a VERY brief time). But I find that if I boot to the internals, usually do so for a short time daily, it is best to boot recovery mode when going from one partition table system to another.
When I can get a couple new drives every thing will be converted to GPT and uefi boot.
Got a couple changelog messages about openbox-menu that I don't comprehend.
Here is the stuff as I saved it - so the newest is at the top. These are the only OB ones I have. Been collecting the things for 2 years now.
openbox (3.6.1-6) unstable; urgency=medium
After many bug reports configuration with openbox-menu has been replaced
by simple python script to generate dynamic menu.
openbox (3.6.1-5) unstable; urgency=medium
Start with this release menu is replaced by openbox-menu. If you still
using old style menu please replace configuration file with your own.
The oldest one, from Aug, seems pretty straight forward but I have always used openbox-menu so I ignored it.
The new one I have not seen any results from because it came in a chroot environment run from testing and doing a Sid install. I didn't pop over there as it is on my internals and I try to stay off there except to log into one install and keep all up to date, and get out until I get at least one new drive. But I may have to go to my Sid install there instead of the testing one just to try and figure this out.
To put it simply;
What the hell are they talking about?
Any information will be greatly appreciated. That message simply baffles me.
"- After many bug reports configuration with openbox-menu has been replaced
by simple python script to generate dynamic menu."
All the words seem to be understandable but the entire sentence seems like gibberish.
This was an upgrade for openbox-menu.
Not sure why openbox-menu is even installed on here. Don't remember doing that. Have never complained to them myself but the damned thing doesn't work well. I don't use it.
May have to rethink that or at least give it a whack to see what it does.
I spent 3 hours last night working with this kept getting invlaid options. from terminal help I went to:
where it (if I understand what it said) to use -h instead of -r this got me to path which I entered like this:
/home/pictures/childhood/locked/ and /home/pictures/childhood/
and I get from both no such directory found. I must be doing some thing wrong on the path. I will now go look up paths and try to learn something.
Go to your file manager and right click on the name of the directory in which the photos exist and use the 'copy' option. Then go to your terminal and use the 'paste' option to put that in where the path needs to be. Will give you the complete path that way every time.
I am not real good at typing and have some long paths that need entered. Discovered this works quite a time ago and it makes my life easier.
Use the -R option for chown in that case.
Here is what I have at the moment:
sudo chown -h whoami: /home/michael/pictures/childhood/locked/
I ge no such file or directory.
so Itried this:
sudo chown -h /home/michael/pictures/childhood/locke/
and I got this
missing olperation after /home/michael/pictures/childhood/locked/
sudo chown -h $(whoami): /home/michael/pictures/childhood/locked/
Why does this have "locked" in the file name in the first place?
What is the output of
# stat /home/michael/pictures/childhood/locked/
That needs run as root at the # prompt or with sudo at the $ prompt.
when I use -r I get invaled option
-R is uppercase