meld takes ages to open and fails with org.gtk.vfs.UDisks2VolumeMonitor:: Timeout was reached...





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















git mergetool opening meld takes ages to open and finally fails with:



invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor:: Timeout was reached (g-io-error-quark, 24)


It was working fine not long ago and no system updates were installed. No other tools seem to have this problem.



What could be causing this issue?










share|improve this question





























    0















    git mergetool opening meld takes ages to open and finally fails with:



    invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor:: Timeout was reached (g-io-error-quark, 24)


    It was working fine not long ago and no system updates were installed. No other tools seem to have this problem.



    What could be causing this issue?










    share|improve this question

























      0












      0








      0








      git mergetool opening meld takes ages to open and finally fails with:



      invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor:: Timeout was reached (g-io-error-quark, 24)


      It was working fine not long ago and no system updates were installed. No other tools seem to have this problem.



      What could be causing this issue?










      share|improve this question














      git mergetool opening meld takes ages to open and finally fails with:



      invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor:: Timeout was reached (g-io-error-quark, 24)


      It was working fine not long ago and no system updates were installed. No other tools seem to have this problem.



      What could be causing this issue?







      linux ubuntu git sshfs meld






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 2 at 4:12









      jozxyqkjozxyqk

      1,18041941




      1,18041941






















          1 Answer
          1






          active

          oldest

          votes


















          0














          The reason was a failed sshfs attempt elsewhere on the system and seemingly completely unrelated to the git repository. The sshfs command had hung while connecting. Even after killing it, accessing the mount point produced the error Transport endpoint is not connected.



          The solution was to ctrl-c the sshfs command and unbind the failed mount point with fusermount -u /path/to/mount.






          share|improve this answer
























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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: 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%2fsuperuser.com%2fquestions%2f1410651%2fmeld-takes-ages-to-open-and-fails-with-org-gtk-vfs-udisks2volumemonitor-timeou%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            The reason was a failed sshfs attempt elsewhere on the system and seemingly completely unrelated to the git repository. The sshfs command had hung while connecting. Even after killing it, accessing the mount point produced the error Transport endpoint is not connected.



            The solution was to ctrl-c the sshfs command and unbind the failed mount point with fusermount -u /path/to/mount.






            share|improve this answer




























              0














              The reason was a failed sshfs attempt elsewhere on the system and seemingly completely unrelated to the git repository. The sshfs command had hung while connecting. Even after killing it, accessing the mount point produced the error Transport endpoint is not connected.



              The solution was to ctrl-c the sshfs command and unbind the failed mount point with fusermount -u /path/to/mount.






              share|improve this answer


























                0












                0








                0







                The reason was a failed sshfs attempt elsewhere on the system and seemingly completely unrelated to the git repository. The sshfs command had hung while connecting. Even after killing it, accessing the mount point produced the error Transport endpoint is not connected.



                The solution was to ctrl-c the sshfs command and unbind the failed mount point with fusermount -u /path/to/mount.






                share|improve this answer













                The reason was a failed sshfs attempt elsewhere on the system and seemingly completely unrelated to the git repository. The sshfs command had hung while connecting. Even after killing it, accessing the mount point produced the error Transport endpoint is not connected.



                The solution was to ctrl-c the sshfs command and unbind the failed mount point with fusermount -u /path/to/mount.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 2 at 4:12









                jozxyqkjozxyqk

                1,18041941




                1,18041941






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


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




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1410651%2fmeld-takes-ages-to-open-and-fails-with-org-gtk-vfs-udisks2volumemonitor-timeou%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

                    Probability when a professor distributes a quiz and homework assignment to a class of n students.

                    Aardman Animations

                    Are they similar matrix