No login possible after sudo in Mint

George, can you copy and paste INTO your terminal from here?

Code:
ls ~/.gnome2

and 

ls ~/.gnome2/keyrings
 
You're cooking with gas now. :)

If you do it correctly, the output should be exactly the same as your last post. If it's different, you're doing something wrong. Let's see.
 
OK, if what you've posted is correct, there's no keyrings directory in ~/.gnome2

I think that's a bit odd, but try this please:

ls ~/.local/share/keyrings

What are the contents?
 
I can not cut and paste your directed lines to Terminal . OK, maybe this is the strange part coming up???

Sone a beetch. The first time I typed " ls /home/my-name/.gnome2:" I got:
ls: cannot access /home/my-name/.gnome2: No such file or directory"

Then I typed " ls /home/my-name/.gnome2/keyrings" the return was:
"ls: cannot access /home/my-name/.gnome2/keyrings: No such file or directory"

Oh sheeite, the SECOND time I entered (in Terminal) : "ls /home/my-name/.gnome2" the return was "accels" gedit"



Wait for it.
Then I typed (with NO "ls") "/home/my-name/.gnome2" The return:
"bash: /home/my-name/.gnome2: is a directory !!! The NO "ls" made a HUGE difference.

So I tried without the "ls" "/home/my-name/.gnome2/keyrings" the return was:
"bash /home/my-name/.gnome2/keyrings: No such file or directory"

I theenk something wrong?


Ho K,
typed ls /home/my-name/.local/share/keyrings Return:
login.keyring user.keystore

Thank you for your help, ThunderRd!
 
Last edited:
Nope, forwards. Think of the cd command as the same cd command you used to use in windows/DOS. Notice how the directory you cd'd into has become part of the prompt now? We are going to cd into your user directory now. Let's see what its name is.

Now:
Code:
ls

What directories are listed there? Find your user directory, and cd into it as we did before:

Code:
cd myusername

Now, tell me what the prompt looks like. Mine looks like this:

thunderrd@Q6600:~$

The ~$ means I am in my own user directory.
 
filesystem.jpg I'm showing you this because it's important that you have a concept of the directory structure. It will help us. I promise to show you why at the appropriate time. Don't think it's going backwards, just think of it as a slower, more deliberate way into the same goal. We were using shorthand before, and this is the longhand way, so you will visualize the path a bit easier like this.

If you type 'ls /'

You will see all the directories pictured here in yellow. We want to navigate to /home, so you type 'cd /home'

In /home, you see all the user accounts by issuing the command 'ls'. For example, /home/thunderrd or /home/gizmo, or /home/brucespringsteen.

When Bruce looks at his home directory, it looks like ~ at the prompt.

Likewise, /home/cloasters appears as ~ to you, because ~ is shorthand for /home/name-of-the-user-now-logged-on
 
So, to recap:

Open a terminal and type each command followed by 'enter':
Code:
cd /home        [don't forget the slash]

ls                               [show-me-names-of-all-users-in- /home]

cd myusername       [no slash in this one]

cd .gnome2              [or here]

ls -la                          [the list command]

The first command enters the /home directory. The second enters your personal user directory. Then, we enter the .gnome2 directory. At this point, your prompt should look like this:

Code:
thunderrd@Q6600:~/.gnome2$

If it doesn't look like this [on the right of the colon], let me know.

Now, the fun starts. 'ls -la' will list all files and directories in the ~/.gnome2 directory. We are looking for 'keyrings'. If it isn't there, and you are sure, let me know.

You really should learn how to copy/paste and or take screenshots. It will eliminate all doubt as to whether you are typing the commands and reading the output properly, or not. I'm flying a little blind when you report that issuing the same command on different occasions is yielding different output. It's IMPOSSIBLE for that to happen.

Editor's note: it's impossible to happen, EXCEPT to Daniel~. In which case, it's absolutely normal. Unfortunately, YOU have not yet achieved the legendary status of the Big Man, so it's IMPOSSIBLE for you.
 
Thank you ThunderRd!

Referencing post # 87 by ThunderRd
Selecting "select all" then "paste" either inside the Terminal window or from its title bar
doesn't let me copy and paste the contents of the Terminal window.
I'm taking special care to follow your directions exactly.

Entering "ls" as directed in post 87 and pressing "Enter" returns:
Desktop Downloads Music Public Videos
Documents firefox Pictures Templates

Entering cd my-name returns:
bash: cd: my-name: No such file or directory

If by chance there is(for now) some tiny little thing I'm supposed to do that you are not specifying in black and white because "everyone knows that" please assume that I don't. Thank you!
 
Thank you a bunch, ThunderRd!

Referencing your post #88
Hey, that's a LOT of posts on my behalf! "Thank you" seems smaller than the thanks I owe you by a lot. Thanks guy!

Re: #88 by Thunder Rd

I downloaded the diagram of Linux File Structure, it's important for future reference. Thanks!

the "ls /" command lists some major files that are the same as your example and some that are Mintish.
 
Thank you very much, Gizmo! I will use your link and hopefully digest and remember the directions in the how-to copy and paste text into...



Referencing ThunderRd #89

All the commands you listed in this post worked exactly as you said they would. Mirabile Dictu!! Thank you!

Because all of the commands worked as they should have I think I should post what the "ls -la" command returned in .gnome2.


total 16
drwx------ 4 my-name my-name 4096 Feb 29 20:37
drwxr xr x 29 my-name my-name 4096 Mar 22 16:00
drwx------ 2 my-name my-name 4096 Feb 29 20:44 accels
drwx-xr-x 2 my-name my-name 4096 Mar 22 17:42 gedit
 
OK, George, I'm confident in that answer now. Next step.

Please close the terminal, open a new one, and follow the instructions in 89 again, but this time go to .local/share/keyrings instead of .gnome2

Then, after you are in
~/.local/share/keyrings [in the prompt], type 'ls -la' again and post the output.

Step by step:
Code:
cd /home
cd myusername
cd .local
cd share
cd keyrings
ls -la

If the information you've given me before is correct, you should see login.keyring and user.keystore in the keyrings directory. If you get that output, I'm confident we can continue.
 
It works as you expected this time, no problems. Just for accuracy, let me write what came after entering ls -la at the
/.local/share/keyrings $ prompt:

total 16
drwx------ 2 my-name my-name 4096 Mar 20 18:32 .
drwxr-xr-x 13 my-name my-name 4096 Mar 22 17:42 ..
-rw------- 1 my-name my-name 2830 Mar 1 18:20 login .keyring
-rw------- 1 my-name my-name 207 Feb 29 21:06 user .keystore

The only difference between what's seen in Terminal and this recounting of it is that Terminal lines up all the lines perfectly.


Thank you very much for your time and efforts on my behalf, ThunderRd!
 
Just a little thing to check, George.

There shouldn't be a space between the filename and the dot. Can you check that?

For example, it SHOULD say login.keyring and user.keystore, with no spaces within the filename.

If that is correct, I want you to go to the next step. We are going to rename the entire ~/.local/share/keyrings directory. Please read this post completely, and choose either option A or B.

Option A:
***Now, m'man, you must be very very careful here. You cannot make any space or syntax mistakes this time, or it won't work. This is why I really want you to copy and paste the commands I give you. Then I can only blame myself :)***

To do this, you will use the command 'mv', like this. Open a new terminal and type:

Code:
mv ~/.local/share/keyrings ~/.local/share/keyrings-OLD

There should not be any output at all. Just a new filesystem prompt. If there is output, post it here.


Option B:
The other option is to rename it from your file manager. Open nemo, and navigate to /home/youruser/.local/share/, and then look in the right hand pane for 'keyrings'

Then, right click on 'keyrings' and rename it to the above filename, the same way you'd do in a windows file manager.

When you are done renaming the directory:
Code:
cd /home
cd myusername
cd .local
cd share
ls -la

OR

Code:
ls -la ~/.local/share          [no spaces after the tilde]

If you did it correctly, you will see that the 'keyrings' directory is now 'keyrings-OLD'

Report when you're done, and we'll continue.
 
Last edited:
Thank you very much for your patience ThunderRd!

Typing /home/my-name/ .gnome2 (inTerminal) gets me:
Is a directory.

Typing ls /home/my-name/.gnome2/keyrings (in Terminal) gets me:
No such file or directory.

Typing /home/my-name/.local/share/keyrings/login.keyring (in Terminal) gets me:

George!
Why are you typing anything!!??
Typing is the great evil of "Terminal"!
It allows countless almost imperceptible errors to creep in and gobble up your endeavors! besides its so slow and boring!
(at lest when your dyslexic! ":O}
Cut 'N Paste George! Cut and paste!

Works from keyboard and from mouse... underline and right click copy, then paste wherever good code needs replicating.
It's like this Georgie,.. ya mind if I calls ya Georgie for the purpose of this example"?
I was sure ya wouldn't. Good Man!
So anyways like I was saying before ya interrupted me with the name..
thing...
It's like this,...
I'm Tried of having to call ya Georgie, let's just leave names out of this and see how that goes.
it's like this you may be 1000 percent sure you've done everything right, but our seniors have no way of knowing that...and they are the one who most need to know what code is actually being input as apposed to what what code your 1000 percent sure you got right.

These guys will work with pretty much any nonsense we bring them to untangle, but it REALLY helps them to be as sure of your moves as you might be.":O}
 
Back
Top