How do I get rid of this flatpak dconf-WARNING?











up vote
1
down vote

favorite
1












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.










share|improve this question


















  • 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








  • 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












  • 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















up vote
1
down vote

favorite
1












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.










share|improve this question


















  • 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








  • 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












  • 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













up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





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.










share|improve this question













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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










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 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




    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












  • oh that's easy: you make an answer and accept it when you can
    – Rinzwind
    Jun 23 at 20:23














  • 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








  • 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












  • 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










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






share|improve this answer




























    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.






    share|improve this answer






























      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.






      share|improve this answer








      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.


















        Your Answer








        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "89"
        };
        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: true,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: 10,
        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
        });


        }
        });














         

        draft saved


        draft discarded


















        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

























        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






        share|improve this answer

























          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






          share|improve this answer























            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






            share|improve this answer












            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







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jun 23 at 20:59









            Joschua

            1651113




            1651113
























                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.






                share|improve this answer



























                  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.






                  share|improve this answer

























                    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.






                    share|improve this answer














                    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.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Oct 21 at 7:09

























                    answered Oct 21 at 6:58









                    Rocdufer

                    412




                    412






















                        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.






                        share|improve this answer








                        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.






















                          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.






                          share|improve this answer








                          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.




















                            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.






                            share|improve this answer








                            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.







                            share|improve this answer








                            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.









                            share|improve this answer



                            share|improve this answer






                            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




                            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.






























                                 

                                draft saved


                                draft discarded



















































                                 


                                draft saved


                                draft discarded














                                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





















































                                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







                                Popular posts from this blog

                                flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                                Mangá

                                 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕