ubuntu mate caja settings need read and write options
I am using ubuntu mate, when I want to access Home directory it shows
The path for the directory containing caja settings need read and write permissions: /home/xxxx/.config/caja
I tried to change permission and restarted it but I get into same problem
ubuntu mate-desktop
asked Jan 13 '17 at 15:57
sandeppsandepp
62
add a comment |
I am using ubuntu mate, when I want to access Home directory it shows
The path for the directory containing caja settings need read and write permissions: /home/xxxx/.config/caja
I tried to change permission and restarted it but I get into same problem
ubuntu mate-desktop
asked Jan 13 '17 at 15:57
sandeppsandepp
62
Can you give a little bit more insight? How do you access the home directory and where appears the error? How were the permissions set for the home folder and how do you change them?...
– marc
Jan 14 '17 at 0:20
I used sudo chmod 777 -R /home/xxxx/.config/caja, it gave results like "changing directory permission: Read only" although I restarted and I was directed to initrafms where I ran "fsck /dev/sda3" and then rebooted it, Right now t is working
– sandepp
Jan 14 '17 at 18:00
Is the partition in read-only mode? You can see that with themountcommand. If yes, then remount it with write permission activatedsudo mount -o remount,rw /dev/sda3 ...
– marc
Jan 14 '17 at 18:43
add a comment |
I am using ubuntu mate, when I want to access Home directory it shows
The path for the directory containing caja settings need read and write permissions: /home/xxxx/.config/caja
I tried to change permission and restarted it but I get into same problem
ubuntu mate-desktop
asked Jan 13 '17 at 15:57
sandeppsandepp
62
I am using ubuntu mate, when I want to access Home directory it shows
The path for the directory containing caja settings need read and write permissions: /home/xxxx/.config/caja
I tried to change permission and restarted it but I get into same problem
ubuntu mate-desktop
ubuntu mate-desktop
asked Jan 13 '17 at 15:57
sandeppsandepp
62
asked Jan 13 '17 at 15:57
sandeppsandepp
62
asked Jan 13 '17 at 15:57
sandeppsandepp
62
asked Jan 13 '17 at 15:57
sandeppsandepp
62
asked Jan 13 '17 at 15:57
sandeppsandepp
62
62
Can you give a little bit more insight? How do you access the home directory and where appears the error? How were the permissions set for the home folder and how do you change them?...
– marc
Jan 14 '17 at 0:20
I used sudo chmod 777 -R /home/xxxx/.config/caja, it gave results like "changing directory permission: Read only" although I restarted and I was directed to initrafms where I ran "fsck /dev/sda3" and then rebooted it, Right now t is working
– sandepp
Jan 14 '17 at 18:00
Is the partition in read-only mode? You can see that with themountcommand. If yes, then remount it with write permission activatedsudo mount -o remount,rw /dev/sda3 ...
– marc
Jan 14 '17 at 18:43
add a comment |
Can you give a little bit more insight? How do you access the home directory and where appears the error? How were the permissions set for the home folder and how do you change them?...
– marc
Jan 14 '17 at 0:20
I used sudo chmod 777 -R /home/xxxx/.config/caja, it gave results like "changing directory permission: Read only" although I restarted and I was directed to initrafms where I ran "fsck /dev/sda3" and then rebooted it, Right now t is working
– sandepp
Jan 14 '17 at 18:00
Is the partition in read-only mode? You can see that with themountcommand. If yes, then remount it with write permission activatedsudo mount -o remount,rw /dev/sda3 ...
– marc
Jan 14 '17 at 18:43
Can you give a little bit more insight? How do you access the home directory and where appears the error? How were the permissions set for the home folder and how do you change them?...
– marc
Jan 14 '17 at 0:20
Can you give a little bit more insight? How do you access the home directory and where appears the error? How were the permissions set for the home folder and how do you change them?...
– marc
Jan 14 '17 at 0:20
I used sudo chmod 777 -R /home/xxxx/.config/caja, it gave results like "changing directory permission: Read only" although I restarted and I was directed to initrafms where I ran "fsck /dev/sda3" and then rebooted it, Right now t is working
– sandepp
Jan 14 '17 at 18:00
I used sudo chmod 777 -R /home/xxxx/.config/caja, it gave results like "changing directory permission: Read only" although I restarted and I was directed to initrafms where I ran "fsck /dev/sda3" and then rebooted it, Right now t is working
– sandepp
Jan 14 '17 at 18:00
Is the partition in read-only mode? You can see that with the
mount command. If yes, then remount it with write permission activated sudo mount -o remount,rw /dev/sda3 ...– marc
Jan 14 '17 at 18:43
Is the partition in read-only mode? You can see that with the
mount command. If yes, then remount it with write permission activated sudo mount -o remount,rw /dev/sda3 ...– marc
Jan 14 '17 at 18:43
add a comment |
2 Answers
2
active
oldest
votes
People that came here from Google or Duckduckgo (like me) need the answer on this one. In my case I made a Starter on my Desktop to start Caja filemanager directly from the Desktop. But when I made it executable and click it to run, I get the same message as topic starter above.
For that, I found out a solution, so here it is:
Open a terminal and type:
(change username to your username)
cd /home/username/
cd .config
chmod -a -R 777 caja
rm -r caja
Done!
Next time the machine starts or Caja filemanager is used, the map caja wil be back in the right mode on /home/username/.config. So don't worry for that.
Greetz,
Arno.
answered Nov 30 '18 at 10:39
ArnoArno
1
add a comment |
I encountered this problem after hibernating with the "pm-suspend-hybrid" command in Ubuntu 16.04. Trying to open caja resulted in the same error message you describe. After a reboot and an execution of the fsck command, the problem was fixed in my case, no permission changes required (changing permissions to "777" as per Arno's answer is ill-advised from a security standpoint since "7" permission for "other" means read, write and execute permissions for everyone.)
As to WHY this is happening to prevent recurrences, in this Linux Mint discussion on the topic https://forums.linuxmint.com/viewtopic.php?f=90&t=165741?f=90&t=165741, user "Wharfrat" pins the blame on bypassing ordinary logins with an encrypted drive, which is what happens when I resume from hibernation and wind up directly at my desktop without logging in.
answered 10 hours ago
wurtzkurdlewurtzkurdle
12
New contributor
wurtzkurdle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f337175%2fubuntu-mate-caja-settings-need-read-and-write-options%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
People that came here from Google or Duckduckgo (like me) need the answer on this one. In my case I made a Starter on my Desktop to start Caja filemanager directly from the Desktop. But when I made it executable and click it to run, I get the same message as topic starter above.
For that, I found out a solution, so here it is:
Open a terminal and type:
(change username to your username)
cd /home/username/
cd .config
chmod -a -R 777 caja
rm -r caja
Done!
Next time the machine starts or Caja filemanager is used, the map caja wil be back in the right mode on /home/username/.config. So don't worry for that.
Greetz,
Arno.
answered Nov 30 '18 at 10:39
ArnoArno
1
add a comment |
People that came here from Google or Duckduckgo (like me) need the answer on this one. In my case I made a Starter on my Desktop to start Caja filemanager directly from the Desktop. But when I made it executable and click it to run, I get the same message as topic starter above.
For that, I found out a solution, so here it is:
Open a terminal and type:
(change username to your username)
cd /home/username/
cd .config
chmod -a -R 777 caja
rm -r caja
Done!
Next time the machine starts or Caja filemanager is used, the map caja wil be back in the right mode on /home/username/.config. So don't worry for that.
Greetz,
Arno.
answered Nov 30 '18 at 10:39
ArnoArno
1
add a comment |
People that came here from Google or Duckduckgo (like me) need the answer on this one. In my case I made a Starter on my Desktop to start Caja filemanager directly from the Desktop. But when I made it executable and click it to run, I get the same message as topic starter above.
For that, I found out a solution, so here it is:
Open a terminal and type:
(change username to your username)
cd /home/username/
cd .config
chmod -a -R 777 caja
rm -r caja
Done!
Next time the machine starts or Caja filemanager is used, the map caja wil be back in the right mode on /home/username/.config. So don't worry for that.
Greetz,
Arno.
answered Nov 30 '18 at 10:39
ArnoArno
1
People that came here from Google or Duckduckgo (like me) need the answer on this one. In my case I made a Starter on my Desktop to start Caja filemanager directly from the Desktop. But when I made it executable and click it to run, I get the same message as topic starter above.
For that, I found out a solution, so here it is:
Open a terminal and type:
(change username to your username)
cd /home/username/
cd .config
chmod -a -R 777 caja
rm -r caja
Done!
Next time the machine starts or Caja filemanager is used, the map caja wil be back in the right mode on /home/username/.config. So don't worry for that.
Greetz,
Arno.
answered Nov 30 '18 at 10:39
ArnoArno
1
answered Nov 30 '18 at 10:39
ArnoArno
1
answered Nov 30 '18 at 10:39
ArnoArno
1
answered Nov 30 '18 at 10:39
ArnoArno
1
1
add a comment |
add a comment |
I encountered this problem after hibernating with the "pm-suspend-hybrid" command in Ubuntu 16.04. Trying to open caja resulted in the same error message you describe. After a reboot and an execution of the fsck command, the problem was fixed in my case, no permission changes required (changing permissions to "777" as per Arno's answer is ill-advised from a security standpoint since "7" permission for "other" means read, write and execute permissions for everyone.)
As to WHY this is happening to prevent recurrences, in this Linux Mint discussion on the topic https://forums.linuxmint.com/viewtopic.php?f=90&t=165741?f=90&t=165741, user "Wharfrat" pins the blame on bypassing ordinary logins with an encrypted drive, which is what happens when I resume from hibernation and wind up directly at my desktop without logging in.
answered 10 hours ago
wurtzkurdlewurtzkurdle
12
New contributor
wurtzkurdle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I encountered this problem after hibernating with the "pm-suspend-hybrid" command in Ubuntu 16.04. Trying to open caja resulted in the same error message you describe. After a reboot and an execution of the fsck command, the problem was fixed in my case, no permission changes required (changing permissions to "777" as per Arno's answer is ill-advised from a security standpoint since "7" permission for "other" means read, write and execute permissions for everyone.)
As to WHY this is happening to prevent recurrences, in this Linux Mint discussion on the topic https://forums.linuxmint.com/viewtopic.php?f=90&t=165741?f=90&t=165741, user "Wharfrat" pins the blame on bypassing ordinary logins with an encrypted drive, which is what happens when I resume from hibernation and wind up directly at my desktop without logging in.
answered 10 hours ago
wurtzkurdlewurtzkurdle
12
New contributor
wurtzkurdle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I encountered this problem after hibernating with the "pm-suspend-hybrid" command in Ubuntu 16.04. Trying to open caja resulted in the same error message you describe. After a reboot and an execution of the fsck command, the problem was fixed in my case, no permission changes required (changing permissions to "777" as per Arno's answer is ill-advised from a security standpoint since "7" permission for "other" means read, write and execute permissions for everyone.)
As to WHY this is happening to prevent recurrences, in this Linux Mint discussion on the topic https://forums.linuxmint.com/viewtopic.php?f=90&t=165741?f=90&t=165741, user "Wharfrat" pins the blame on bypassing ordinary logins with an encrypted drive, which is what happens when I resume from hibernation and wind up directly at my desktop without logging in.
answered 10 hours ago
wurtzkurdlewurtzkurdle
12
New contributor
wurtzkurdle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I encountered this problem after hibernating with the "pm-suspend-hybrid" command in Ubuntu 16.04. Trying to open caja resulted in the same error message you describe. After a reboot and an execution of the fsck command, the problem was fixed in my case, no permission changes required (changing permissions to "777" as per Arno's answer is ill-advised from a security standpoint since "7" permission for "other" means read, write and execute permissions for everyone.)
As to WHY this is happening to prevent recurrences, in this Linux Mint discussion on the topic https://forums.linuxmint.com/viewtopic.php?f=90&t=165741?f=90&t=165741, user "Wharfrat" pins the blame on bypassing ordinary logins with an encrypted drive, which is what happens when I resume from hibernation and wind up directly at my desktop without logging in.
answered 10 hours ago
wurtzkurdlewurtzkurdle
12
New contributor
wurtzkurdle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 10 hours ago
wurtzkurdlewurtzkurdle
12
New contributor
wurtzkurdle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 10 hours ago
wurtzkurdlewurtzkurdle
12
answered 10 hours ago
wurtzkurdlewurtzkurdle
12
12
New contributor
wurtzkurdle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
wurtzkurdle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
wurtzkurdle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f337175%2fubuntu-mate-caja-settings-need-read-and-write-options%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you give a little bit more insight? How do you access the home directory and where appears the error? How were the permissions set for the home folder and how do you change them?...
– marc
Jan 14 '17 at 0:20
I used sudo chmod 777 -R /home/xxxx/.config/caja, it gave results like "changing directory permission: Read only" although I restarted and I was directed to initrafms where I ran "fsck /dev/sda3" and then rebooted it, Right now t is working
– sandepp
Jan 14 '17 at 18:00
Is the partition in read-only mode? You can see that with the
mountcommand. If yes, then remount it with write permission activatedsudo mount -o remount,rw /dev/sda3 ...– marc
Jan 14 '17 at 18:43