How do I get rid of this flatpak dconf-WARNING?
Multi tool use
up vote
1
down vote
favorite
I installed flatpak and one application. I have now removed both flatpak and that application, and I'm getting this message for AFAICS whenever I start a GUI application (for example, meld or pluma):
dconf-WARNING **: 18:37:20.153: Unable to open /home/user/.local/share/flatpak/exports/share/dconf/profile/user: Permission denied
I'm using a fresh install of Ubuntu Mate 18.04 and I don't remember seeing this before.
dconf flatpak
asked Jun 23 at 16:48
Joschua
1651113
add a comment |
up vote
1
down vote
favorite
I installed flatpak and one application. I have now removed both flatpak and that application, and I'm getting this message for AFAICS whenever I start a GUI application (for example, meld or pluma):
dconf-WARNING **: 18:37:20.153: Unable to open /home/user/.local/share/flatpak/exports/share/dconf/profile/user: Permission denied
I'm using a fresh install of Ubuntu Mate 18.04 and I don't remember seeing this before.
dconf flatpak
asked Jun 23 at 16:48
Joschua
1651113
2
dconf-warnings are there for the maintainer of dconf so please report this as a bug. For the mean time I would suggest to do als -l ~/.local/share/flatpak/exports/share/dconf/profile/userand document the result and then do asudo chown $USER:$USER ~/.local/share/flatpak/exports/share/dconf/profile/userand see if that fixes it.
– Rinzwind
Jun 23 at 16:53
1
Thanks! Apparently~/.local/share/flatpakwas owned byroot. (Maybe as a result ofsudo flatpak install.. Is that wrong?) I simply deleted the folder (withsudo) and the issue is gone.
– Joschua
Jun 23 at 17:54
I'm not sure how I should deal with this askubuntu question now.. Deleting it seems wrong, as other people might stumble upon the same problem.
– Joschua
Jun 23 at 17:54
oh that's easy: you make an answer and accept it when you can
– Rinzwind
Jun 23 at 20:23
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I installed flatpak and one application. I have now removed both flatpak and that application, and I'm getting this message for AFAICS whenever I start a GUI application (for example, meld or pluma):
dconf-WARNING **: 18:37:20.153: Unable to open /home/user/.local/share/flatpak/exports/share/dconf/profile/user: Permission denied
I'm using a fresh install of Ubuntu Mate 18.04 and I don't remember seeing this before.
dconf flatpak
asked Jun 23 at 16:48
Joschua
1651113
I installed flatpak and one application. I have now removed both flatpak and that application, and I'm getting this message for AFAICS whenever I start a GUI application (for example, meld or pluma):
dconf-WARNING **: 18:37:20.153: Unable to open /home/user/.local/share/flatpak/exports/share/dconf/profile/user: Permission denied
I'm using a fresh install of Ubuntu Mate 18.04 and I don't remember seeing this before.
dconf flatpak
dconf flatpak
asked Jun 23 at 16:48
Joschua
1651113
asked Jun 23 at 16:48
Joschua
1651113
asked Jun 23 at 16:48
Joschua
1651113
asked Jun 23 at 16:48
Joschua
1651113
asked Jun 23 at 16:48
Joschua
1651113
1651113
2
dconf-warnings are there for the maintainer of dconf so please report this as a bug. For the mean time I would suggest to do als -l ~/.local/share/flatpak/exports/share/dconf/profile/userand document the result and then do asudo chown $USER:$USER ~/.local/share/flatpak/exports/share/dconf/profile/userand see if that fixes it.
– Rinzwind
Jun 23 at 16:53
1
Thanks! Apparently~/.local/share/flatpakwas owned byroot. (Maybe as a result ofsudo flatpak install.. Is that wrong?) I simply deleted the folder (withsudo) and the issue is gone.
– Joschua
Jun 23 at 17:54
I'm not sure how I should deal with this askubuntu question now.. Deleting it seems wrong, as other people might stumble upon the same problem.
– Joschua
Jun 23 at 17:54
oh that's easy: you make an answer and accept it when you can
– Rinzwind
Jun 23 at 20:23
add a comment |
2
dconf-warnings are there for the maintainer of dconf so please report this as a bug. For the mean time I would suggest to do als -l ~/.local/share/flatpak/exports/share/dconf/profile/userand document the result and then do asudo chown $USER:$USER ~/.local/share/flatpak/exports/share/dconf/profile/userand see if that fixes it.
– Rinzwind
Jun 23 at 16:53
1
Thanks! Apparently~/.local/share/flatpakwas owned byroot. (Maybe as a result ofsudo flatpak install.. Is that wrong?) I simply deleted the folder (withsudo) and the issue is gone.
– Joschua
Jun 23 at 17:54
I'm not sure how I should deal with this askubuntu question now.. Deleting it seems wrong, as other people might stumble upon the same problem.
– Joschua
Jun 23 at 17:54
oh that's easy: you make an answer and accept it when you can
– Rinzwind
Jun 23 at 20:23
2
2
dconf-warnings are there for the maintainer of dconf so please report this as a bug. For the mean time I would suggest to do a
ls -l ~/.local/share/flatpak/exports/share/dconf/profile/user and document the result and then do a sudo chown $USER:$USER ~/.local/share/flatpak/exports/share/dconf/profile/user and see if that fixes it.– Rinzwind
Jun 23 at 16:53
dconf-warnings are there for the maintainer of dconf so please report this as a bug. For the mean time I would suggest to do a
ls -l ~/.local/share/flatpak/exports/share/dconf/profile/user and document the result and then do a sudo chown $USER:$USER ~/.local/share/flatpak/exports/share/dconf/profile/user and see if that fixes it.– Rinzwind
Jun 23 at 16:53
1
1
Thanks! Apparently
~/.local/share/flatpak was owned by root. (Maybe as a result of sudo flatpak install.. Is that wrong?) I simply deleted the folder (with sudo) and the issue is gone.– Joschua
Jun 23 at 17:54
Thanks! Apparently
~/.local/share/flatpak was owned by root. (Maybe as a result of sudo flatpak install.. Is that wrong?) I simply deleted the folder (with sudo) and the issue is gone.– Joschua
Jun 23 at 17:54
I'm not sure how I should deal with this askubuntu question now.. Deleting it seems wrong, as other people might stumble upon the same problem.
– Joschua
Jun 23 at 17:54
I'm not sure how I should deal with this askubuntu question now.. Deleting it seems wrong, as other people might stumble upon the same problem.
– Joschua
Jun 23 at 17:54
oh that's easy: you make an answer and accept it when you can
– Rinzwind
Jun 23 at 20:23
oh that's easy: you make an answer and accept it when you can
– Rinzwind
Jun 23 at 20:23
add a comment |
3 Answers
3
active
oldest
votes
up vote
1
down vote
accepted
For me the issue was solved by deleting the whole flatpak directory (sudo rm -rf ~/.local/share/flatpak/), but may not want to do that if you're currently using any flatpak apps or want to keep their config files.
In that case it's probably better to try to use something like this (as sugested by @Rinzwind): sudo chown $USER:$USER ~/.local/share/flatpak/exports/share/dconf/profile/user
answered Jun 23 at 20:59
Joschua
1651113
add a comment |
up vote
0
down vote
I had the problem when launching Firefox by clicking a link inside a Thunderbird's message. The Firefox profile was locked, and in the terminal where Thunderbird was launched, I got the message «dconf-WARNING **: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission denied».
In deed, I later found there was no "/dconf/profile/user" present in the file system.
Solved the issue by reinstalling flatpak packages from repository.
Thunderbird links worked again without locking the Firefox profile.
answered Oct 21 at 6:58
Rocdufer
412
add a comment |
up vote
0
down vote
Do not let Firefox write in that file!
, the question is why FF want to access Flatpak container settings ?
-save : ~/.local/share/flatpak/exports/share/dconf/profile/user
-chown : ( let FF to write in )
-diff : than upload the diff result
--- after this you can put back the original file in place.
answered Nov 20 at 6:56
IMP
1
New contributor
IMP 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 |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
For me the issue was solved by deleting the whole flatpak directory (sudo rm -rf ~/.local/share/flatpak/), but may not want to do that if you're currently using any flatpak apps or want to keep their config files.
In that case it's probably better to try to use something like this (as sugested by @Rinzwind): sudo chown $USER:$USER ~/.local/share/flatpak/exports/share/dconf/profile/user
answered Jun 23 at 20:59
Joschua
1651113
add a comment |
up vote
1
down vote
accepted
For me the issue was solved by deleting the whole flatpak directory (sudo rm -rf ~/.local/share/flatpak/), but may not want to do that if you're currently using any flatpak apps or want to keep their config files.
In that case it's probably better to try to use something like this (as sugested by @Rinzwind): sudo chown $USER:$USER ~/.local/share/flatpak/exports/share/dconf/profile/user
answered Jun 23 at 20:59
Joschua
1651113
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
For me the issue was solved by deleting the whole flatpak directory (sudo rm -rf ~/.local/share/flatpak/), but may not want to do that if you're currently using any flatpak apps or want to keep their config files.
In that case it's probably better to try to use something like this (as sugested by @Rinzwind): sudo chown $USER:$USER ~/.local/share/flatpak/exports/share/dconf/profile/user
answered Jun 23 at 20:59
Joschua
1651113
For me the issue was solved by deleting the whole flatpak directory (sudo rm -rf ~/.local/share/flatpak/), but may not want to do that if you're currently using any flatpak apps or want to keep their config files.
In that case it's probably better to try to use something like this (as sugested by @Rinzwind): sudo chown $USER:$USER ~/.local/share/flatpak/exports/share/dconf/profile/user
answered Jun 23 at 20:59
Joschua
1651113
answered Jun 23 at 20:59
Joschua
1651113
answered Jun 23 at 20:59
Joschua
1651113
answered Jun 23 at 20:59
Joschua
1651113
1651113
add a comment |
add a comment |
up vote
0
down vote
I had the problem when launching Firefox by clicking a link inside a Thunderbird's message. The Firefox profile was locked, and in the terminal where Thunderbird was launched, I got the message «dconf-WARNING **: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission denied».
In deed, I later found there was no "/dconf/profile/user" present in the file system.
Solved the issue by reinstalling flatpak packages from repository.
Thunderbird links worked again without locking the Firefox profile.
answered Oct 21 at 6:58
Rocdufer
412
add a comment |
up vote
0
down vote
I had the problem when launching Firefox by clicking a link inside a Thunderbird's message. The Firefox profile was locked, and in the terminal where Thunderbird was launched, I got the message «dconf-WARNING **: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission denied».
In deed, I later found there was no "/dconf/profile/user" present in the file system.
Solved the issue by reinstalling flatpak packages from repository.
Thunderbird links worked again without locking the Firefox profile.
answered Oct 21 at 6:58
Rocdufer
412
add a comment |
up vote
0
down vote
up vote
0
down vote
I had the problem when launching Firefox by clicking a link inside a Thunderbird's message. The Firefox profile was locked, and in the terminal where Thunderbird was launched, I got the message «dconf-WARNING **: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission denied».
In deed, I later found there was no "/dconf/profile/user" present in the file system.
Solved the issue by reinstalling flatpak packages from repository.
Thunderbird links worked again without locking the Firefox profile.
answered Oct 21 at 6:58
Rocdufer
412
I had the problem when launching Firefox by clicking a link inside a Thunderbird's message. The Firefox profile was locked, and in the terminal where Thunderbird was launched, I got the message «dconf-WARNING **: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission denied».
In deed, I later found there was no "/dconf/profile/user" present in the file system.
Solved the issue by reinstalling flatpak packages from repository.
Thunderbird links worked again without locking the Firefox profile.
answered Oct 21 at 6:58
Rocdufer
412
edited Oct 21 at 7:09
answered Oct 21 at 6:58
Rocdufer
412
answered Oct 21 at 6:58
Rocdufer
412
answered Oct 21 at 6:58
Rocdufer
412
412
add a comment |
add a comment |
up vote
0
down vote
Do not let Firefox write in that file!
, the question is why FF want to access Flatpak container settings ?
-save : ~/.local/share/flatpak/exports/share/dconf/profile/user
-chown : ( let FF to write in )
-diff : than upload the diff result
--- after this you can put back the original file in place.
answered Nov 20 at 6:56
IMP
1
New contributor
IMP 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 |
up vote
0
down vote
Do not let Firefox write in that file!
, the question is why FF want to access Flatpak container settings ?
-save : ~/.local/share/flatpak/exports/share/dconf/profile/user
-chown : ( let FF to write in )
-diff : than upload the diff result
--- after this you can put back the original file in place.
answered Nov 20 at 6:56
IMP
1
New contributor
IMP 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 |
up vote
0
down vote
up vote
0
down vote
Do not let Firefox write in that file!
, the question is why FF want to access Flatpak container settings ?
-save : ~/.local/share/flatpak/exports/share/dconf/profile/user
-chown : ( let FF to write in )
-diff : than upload the diff result
--- after this you can put back the original file in place.
answered Nov 20 at 6:56
IMP
1
New contributor
IMP is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Do not let Firefox write in that file!
, the question is why FF want to access Flatpak container settings ?
-save : ~/.local/share/flatpak/exports/share/dconf/profile/user
-chown : ( let FF to write in )
-diff : than upload the diff result
--- after this you can put back the original file in place.
answered Nov 20 at 6:56
IMP
1
New contributor
IMP is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 20 at 6:56
IMP
1
New contributor
IMP is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 20 at 6:56
IMP
1
answered Nov 20 at 6:56
IMP
1
1
New contributor
IMP is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
IMP is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
IMP 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 |
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%2faskubuntu.com%2fquestions%2f1049115%2fhow-do-i-get-rid-of-this-flatpak-dconf-warning%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
aqVJg9TMD92jis 1n,Jb0OrgSXr0YcH07rSPXDxvD4tylsH5vxyKJ n68e,oQu
2
dconf-warnings are there for the maintainer of dconf so please report this as a bug. For the mean time I would suggest to do a
ls -l ~/.local/share/flatpak/exports/share/dconf/profile/userand document the result and then do asudo chown $USER:$USER ~/.local/share/flatpak/exports/share/dconf/profile/userand see if that fixes it.– Rinzwind
Jun 23 at 16:53
1
Thanks! Apparently
~/.local/share/flatpakwas owned byroot. (Maybe as a result ofsudo flatpak install.. Is that wrong?) I simply deleted the folder (withsudo) and the issue is gone.– Joschua
Jun 23 at 17:54
I'm not sure how I should deal with this askubuntu question now.. Deleting it seems wrong, as other people might stumble upon the same problem.
– Joschua
Jun 23 at 17:54
oh that's easy: you make an answer and accept it when you can
– Rinzwind
Jun 23 at 20:23