How to solve $HOME/.dmrc file permission error?

up vote
0
down vote

favorite

I recently had a problem and here is the solution of it. After following these steps I fixed my problem, but faced another one.

On Login window after I enter my password and press Enter, this message popups:

User's $HOME/.dmrc file is being ignored. This prevents the default session and language from being saved. File should be owned by user and have 644 permissions. User's $HOME directory must be owned by user and not writable by other users.

I haven't noticed any notable problems except of this message, but anyway, how to solve it?

ls -ld "$HOME" "$HOME/.dmrc"
drwxr-xr-x 82 neo neo 4096 Jul 12 12:05 /home/neo
-rw------- 1 neo neo 29 Jul 12 12:05 /home/neo/.dmrc

I have tried this but it had no effect.

edited Jul 12 at 6:43

roaima

39.2k544105

asked Jul 12 at 6:00

neo mendax

39210

@Kusalananda $ ls -ld "$HOME" "$HOME/.dmrc" drwxr-xr-x 82 neo neo 4096 Jul 12 12:05 /home/neo -rw------- 1 neo neo 29 Jul 12 12:05 /home/neo/.dmrc
â€“Â neo mendax
Jul 12 at 6:11

add a commentÂ |Â

up vote
0
down vote

favorite

I recently had a problem and here is the solution of it. After following these steps I fixed my problem, but faced another one.

On Login window after I enter my password and press Enter, this message popups:

User's $HOME/.dmrc file is being ignored. This prevents the default session and language from being saved. File should be owned by user and have 644 permissions. User's $HOME directory must be owned by user and not writable by other users.

I haven't noticed any notable problems except of this message, but anyway, how to solve it?

ls -ld "$HOME" "$HOME/.dmrc"
drwxr-xr-x 82 neo neo 4096 Jul 12 12:05 /home/neo
-rw------- 1 neo neo 29 Jul 12 12:05 /home/neo/.dmrc

I have tried this but it had no effect.

edited Jul 12 at 6:43

roaima

39.2k544105

asked Jul 12 at 6:00

neo mendax

39210

@Kusalananda $ ls -ld "$HOME" "$HOME/.dmrc" drwxr-xr-x 82 neo neo 4096 Jul 12 12:05 /home/neo -rw------- 1 neo neo 29 Jul 12 12:05 /home/neo/.dmrc
â€“Â neo mendax
Jul 12 at 6:11

add a commentÂ |Â

up vote
0
down vote

favorite

I recently had a problem and here is the solution of it. After following these steps I fixed my problem, but faced another one.

On Login window after I enter my password and press Enter, this message popups:

User's $HOME/.dmrc file is being ignored. This prevents the default session and language from being saved. File should be owned by user and have 644 permissions. User's $HOME directory must be owned by user and not writable by other users.

I haven't noticed any notable problems except of this message, but anyway, how to solve it?

ls -ld "$HOME" "$HOME/.dmrc"
drwxr-xr-x 82 neo neo 4096 Jul 12 12:05 /home/neo
-rw------- 1 neo neo 29 Jul 12 12:05 /home/neo/.dmrc

I have tried this but it had no effect.

edited Jul 12 at 6:43

roaima

39.2k544105

asked Jul 12 at 6:00

neo mendax

39210

I recently had a problem and here is the solution of it. After following these steps I fixed my problem, but faced another one.

On Login window after I enter my password and press Enter, this message popups:

User's $HOME/.dmrc file is being ignored. This prevents the default session and language from being saved. File should be owned by user and have 644 permissions. User's $HOME directory must be owned by user and not writable by other users.

I haven't noticed any notable problems except of this message, but anyway, how to solve it?

ls -ld "$HOME" "$HOME/.dmrc"
drwxr-xr-x 82 neo neo 4096 Jul 12 12:05 /home/neo
-rw------- 1 neo neo 29 Jul 12 12:05 /home/neo/.dmrc

I have tried this but it had no effect.

edited Jul 12 at 6:43

roaima

39.2k544105

asked Jul 12 at 6:00

neo mendax

39210

edited Jul 12 at 6:43

roaima

39.2k544105

edited Jul 12 at 6:43

roaima

39.2k544105

edited Jul 12 at 6:43

roaima

39.2k544105

asked Jul 12 at 6:00

neo mendax

39210

asked Jul 12 at 6:00

neo mendax

39210

asked Jul 12 at 6:00

neo mendax

39210

@Kusalananda $ ls -ld "$HOME" "$HOME/.dmrc" drwxr-xr-x 82 neo neo 4096 Jul 12 12:05 /home/neo -rw------- 1 neo neo 29 Jul 12 12:05 /home/neo/.dmrc
â€“Â neo mendax
Jul 12 at 6:11

add a commentÂ |Â

@Kusalananda $ ls -ld "$HOME" "$HOME/.dmrc" drwxr-xr-x 82 neo neo 4096 Jul 12 12:05 /home/neo -rw------- 1 neo neo 29 Jul 12 12:05 /home/neo/.dmrc
â€“Â neo mendax
Jul 12 at 6:11

@Kusalananda

$ ls -ld "$HOME" "$HOME/.dmrc" drwxr-xr-x 82 neo neo 4096 Jul 12 12:05 /home/neo -rw------- 1 neo neo 29 Jul 12 12:05 /home/neo/.dmrc

â€“Â neo mendax
Jul 12 at 6:11

@Kusalananda

$ ls -ld "$HOME" "$HOME/.dmrc" drwxr-xr-x 82 neo neo 4096 Jul 12 12:05 /home/neo -rw------- 1 neo neo 29 Jul 12 12:05 /home/neo/.dmrc

â€“Â neo mendax
Jul 12 at 6:11

add a commentÂ |Â

2 Answers
2

active

oldest

votes

up vote
1
down vote

accepted

Looking at your permissions and ownerships of $HOME and of $HOME/.dmrc, the only thing you need to do to satisfy the required ownership/permission settings is

chmod 644 "$HOME/.dmrc"

You already own your home directory and it's not writable by other users. The only thing not "correct" is that permissions on the .dmrc file are too tight.

edited Jul 12 at 6:49

answered Jul 12 at 6:39

Kusalananda

101k13199312

add a commentÂ |Â

up vote
-1
down vote

Googling around I found this post. It stands for:

...

Solution Summary: No Frills Depending on the problem, all of these
steps may not be necessary. Running all of them will correct any of
the issues addressed by the error message. They can be run in terminal
in the current session or from the root prompt in recovery mode. If
running from the root prompt, sudo is not required. These commands
will not work from the LiveCD desktop without modification .
sudo chown username /home/username/.dmrc chmod 644 /home/username/.dmrc sudo chown username /home/username # if you get a ".gvfs" error message, see Section 3, Note 3 chmod 755 /home/username

Log out of your current session and back in.
Rebooting is not necessary but will accomplish the same thing.

For the last command, other acceptable permissions include 750 or 700.

edited Jul 12 at 7:51

answered Jul 12 at 6:36

neo mendax

39210

Not strictly accurate as quoted here. Those asterisks around username could affect other users' files and directories, and the lack of semicolons between commands will mean the sequence as written here will fail to run usefully at all. (Note that the original document is accurate.)
â€“Â roaima
Jul 12 at 7:47

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f454827%2fhow-to-solve-home-dmrc-file-permission-error%23new-answer', 'question_page');

);

Post as a guest

Name

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

up vote
1
down vote

accepted

Looking at your permissions and ownerships of $HOME and of $HOME/.dmrc, the only thing you need to do to satisfy the required ownership/permission settings is

chmod 644 "$HOME/.dmrc"

You already own your home directory and it's not writable by other users. The only thing not "correct" is that permissions on the .dmrc file are too tight.

edited Jul 12 at 6:49

answered Jul 12 at 6:39

Kusalananda

101k13199312

add a commentÂ |Â

up vote
1
down vote

accepted

Looking at your permissions and ownerships of $HOME and of $HOME/.dmrc, the only thing you need to do to satisfy the required ownership/permission settings is

chmod 644 "$HOME/.dmrc"

You already own your home directory and it's not writable by other users. The only thing not "correct" is that permissions on the .dmrc file are too tight.

edited Jul 12 at 6:49

answered Jul 12 at 6:39

Kusalananda

101k13199312

add a commentÂ |Â

up vote
1
down vote

accepted

Looking at your permissions and ownerships of $HOME and of $HOME/.dmrc, the only thing you need to do to satisfy the required ownership/permission settings is

chmod 644 "$HOME/.dmrc"

You already own your home directory and it's not writable by other users. The only thing not "correct" is that permissions on the .dmrc file are too tight.

edited Jul 12 at 6:49

answered Jul 12 at 6:39

Kusalananda

101k13199312

Looking at your permissions and ownerships of $HOME and of $HOME/.dmrc, the only thing you need to do to satisfy the required ownership/permission settings is

chmod 644 "$HOME/.dmrc"

You already own your home directory and it's not writable by other users. The only thing not "correct" is that permissions on the .dmrc file are too tight.

edited Jul 12 at 6:49

answered Jul 12 at 6:39

Kusalananda

101k13199312

edited Jul 12 at 6:49

answered Jul 12 at 6:39

Kusalananda

101k13199312

answered Jul 12 at 6:39

Kusalananda

101k13199312

answered Jul 12 at 6:39

Kusalananda

101k13199312

add a commentÂ |Â

up vote
-1
down vote

Googling around I found this post. It stands for:

...

Solution Summary: No Frills Depending on the problem, all of these
steps may not be necessary. Running all of them will correct any of
the issues addressed by the error message. They can be run in terminal
in the current session or from the root prompt in recovery mode. If
running from the root prompt, sudo is not required. These commands
will not work from the LiveCD desktop without modification .
sudo chown username /home/username/.dmrc chmod 644 /home/username/.dmrc sudo chown username /home/username # if you get a ".gvfs" error message, see Section 3, Note 3 chmod 755 /home/username

Log out of your current session and back in.
Rebooting is not necessary but will accomplish the same thing.

For the last command, other acceptable permissions include 750 or 700.

edited Jul 12 at 7:51

answered Jul 12 at 6:36

neo mendax

39210

Not strictly accurate as quoted here. Those asterisks around username could affect other users' files and directories, and the lack of semicolons between commands will mean the sequence as written here will fail to run usefully at all. (Note that the original document is accurate.)
â€“Â roaima
Jul 12 at 7:47

add a commentÂ |Â

up vote
-1
down vote

Googling around I found this post. It stands for:

...

Solution Summary: No Frills Depending on the problem, all of these
steps may not be necessary. Running all of them will correct any of
the issues addressed by the error message. They can be run in terminal
in the current session or from the root prompt in recovery mode. If
running from the root prompt, sudo is not required. These commands
will not work from the LiveCD desktop without modification .
sudo chown username /home/username/.dmrc chmod 644 /home/username/.dmrc sudo chown username /home/username # if you get a ".gvfs" error message, see Section 3, Note 3 chmod 755 /home/username

Log out of your current session and back in.
Rebooting is not necessary but will accomplish the same thing.

For the last command, other acceptable permissions include 750 or 700.

edited Jul 12 at 7:51

answered Jul 12 at 6:36

neo mendax

39210

Not strictly accurate as quoted here. Those asterisks around username could affect other users' files and directories, and the lack of semicolons between commands will mean the sequence as written here will fail to run usefully at all. (Note that the original document is accurate.)
â€“Â roaima
Jul 12 at 7:47

add a commentÂ |Â

up vote
-1
down vote

Googling around I found this post. It stands for:

...

Solution Summary: No Frills Depending on the problem, all of these
steps may not be necessary. Running all of them will correct any of
the issues addressed by the error message. They can be run in terminal
in the current session or from the root prompt in recovery mode. If
running from the root prompt, sudo is not required. These commands
will not work from the LiveCD desktop without modification .
sudo chown username /home/username/.dmrc chmod 644 /home/username/.dmrc sudo chown username /home/username # if you get a ".gvfs" error message, see Section 3, Note 3 chmod 755 /home/username

Log out of your current session and back in.
Rebooting is not necessary but will accomplish the same thing.

For the last command, other acceptable permissions include 750 or 700.

edited Jul 12 at 7:51

answered Jul 12 at 6:36

neo mendax

39210

Googling around I found this post. It stands for:

...

Solution Summary: No Frills Depending on the problem, all of these
steps may not be necessary. Running all of them will correct any of
the issues addressed by the error message. They can be run in terminal
in the current session or from the root prompt in recovery mode. If
running from the root prompt, sudo is not required. These commands
will not work from the LiveCD desktop without modification .
sudo chown username /home/username/.dmrc chmod 644 /home/username/.dmrc sudo chown username /home/username # if you get a ".gvfs" error message, see Section 3, Note 3 chmod 755 /home/username

Log out of your current session and back in.
Rebooting is not necessary but will accomplish the same thing.

For the last command, other acceptable permissions include 750 or 700.

edited Jul 12 at 7:51

answered Jul 12 at 6:36

neo mendax

39210

edited Jul 12 at 7:51

answered Jul 12 at 6:36

neo mendax

39210

answered Jul 12 at 6:36

neo mendax

39210

answered Jul 12 at 6:36

neo mendax

39210

Not strictly accurate as quoted here. Those asterisks around username could affect other users' files and directories, and the lack of semicolons between commands will mean the sequence as written here will fail to run usefully at all. (Note that the original document is accurate.)
â€“Â roaima
Jul 12 at 7:47

add a commentÂ |Â

Not strictly accurate as quoted here. Those asterisks around username could affect other users' files and directories, and the lack of semicolons between commands will mean the sequence as written here will fail to run usefully at all. (Note that the original document is accurate.)
â€“Â roaima
Jul 12 at 7:47

Not strictly accurate as quoted here. Those asterisks around username could affect other users' files and directories, and the lack of semicolons between commands will mean the sequence as written here will fail to run usefully at all. (Note that the original document is accurate.)
â€“Â roaima
Jul 12 at 7:47

add a commentÂ |Â

draft saved

draft discarded

draft saved

draft discarded

Post as a guest

Name

搜尋此網誌

mjhjmtu