gphoto2: Could not claim the USB device












6















Im trying to use My Canon 100D as a webcam on Ubuntu 17.10.



Whether I try to launch:



gphoto2 --capture-movie


I returns error:




An error occurred in the io-library ('Could not claim the USB device'): Could not claim interface 0 (Device or resource busy). Make sure no other program (gvfs-gphoto2-volume-monitor) or kernel module (such as sdc2xx, stv680, spca50x) is using the device and you have read/write access to the device.




Camera is detected by system - I can transfer data from it.



Also lsusb shows this device:




Bus 001 Device 020: ID 04a9:3270 Canon, Inc.




Pretty verbose description, but it is it.



Perhaps I should... Yes, where to start?










share|improve this question























  • Does your camera have any webcam mode or similar? If not then expect it not to work as you want and just as the typical mass storage device which is how the OS will "see" it and nothing else.

    – user692175
    Jan 9 '18 at 12:06











  • There are many cameras supported by gphoto2. This is really cool, as the quality is superior to typical webcam.

    – PeterM
    Jan 9 '18 at 17:43
















6















Im trying to use My Canon 100D as a webcam on Ubuntu 17.10.



Whether I try to launch:



gphoto2 --capture-movie


I returns error:




An error occurred in the io-library ('Could not claim the USB device'): Could not claim interface 0 (Device or resource busy). Make sure no other program (gvfs-gphoto2-volume-monitor) or kernel module (such as sdc2xx, stv680, spca50x) is using the device and you have read/write access to the device.




Camera is detected by system - I can transfer data from it.



Also lsusb shows this device:




Bus 001 Device 020: ID 04a9:3270 Canon, Inc.




Pretty verbose description, but it is it.



Perhaps I should... Yes, where to start?










share|improve this question























  • Does your camera have any webcam mode or similar? If not then expect it not to work as you want and just as the typical mass storage device which is how the OS will "see" it and nothing else.

    – user692175
    Jan 9 '18 at 12:06











  • There are many cameras supported by gphoto2. This is really cool, as the quality is superior to typical webcam.

    – PeterM
    Jan 9 '18 at 17:43














6












6








6








Im trying to use My Canon 100D as a webcam on Ubuntu 17.10.



Whether I try to launch:



gphoto2 --capture-movie


I returns error:




An error occurred in the io-library ('Could not claim the USB device'): Could not claim interface 0 (Device or resource busy). Make sure no other program (gvfs-gphoto2-volume-monitor) or kernel module (such as sdc2xx, stv680, spca50x) is using the device and you have read/write access to the device.




Camera is detected by system - I can transfer data from it.



Also lsusb shows this device:




Bus 001 Device 020: ID 04a9:3270 Canon, Inc.




Pretty verbose description, but it is it.



Perhaps I should... Yes, where to start?










share|improve this question














Im trying to use My Canon 100D as a webcam on Ubuntu 17.10.



Whether I try to launch:



gphoto2 --capture-movie


I returns error:




An error occurred in the io-library ('Could not claim the USB device'): Could not claim interface 0 (Device or resource busy). Make sure no other program (gvfs-gphoto2-volume-monitor) or kernel module (such as sdc2xx, stv680, spca50x) is using the device and you have read/write access to the device.




Camera is detected by system - I can transfer data from it.



Also lsusb shows this device:




Bus 001 Device 020: ID 04a9:3270 Canon, Inc.




Pretty verbose description, but it is it.



Perhaps I should... Yes, where to start?







usb webcam






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 9 '18 at 11:50









PeterMPeterM

244314




244314













  • Does your camera have any webcam mode or similar? If not then expect it not to work as you want and just as the typical mass storage device which is how the OS will "see" it and nothing else.

    – user692175
    Jan 9 '18 at 12:06











  • There are many cameras supported by gphoto2. This is really cool, as the quality is superior to typical webcam.

    – PeterM
    Jan 9 '18 at 17:43



















  • Does your camera have any webcam mode or similar? If not then expect it not to work as you want and just as the typical mass storage device which is how the OS will "see" it and nothing else.

    – user692175
    Jan 9 '18 at 12:06











  • There are many cameras supported by gphoto2. This is really cool, as the quality is superior to typical webcam.

    – PeterM
    Jan 9 '18 at 17:43

















Does your camera have any webcam mode or similar? If not then expect it not to work as you want and just as the typical mass storage device which is how the OS will "see" it and nothing else.

– user692175
Jan 9 '18 at 12:06





Does your camera have any webcam mode or similar? If not then expect it not to work as you want and just as the typical mass storage device which is how the OS will "see" it and nothing else.

– user692175
Jan 9 '18 at 12:06













There are many cameras supported by gphoto2. This is really cool, as the quality is superior to typical webcam.

– PeterM
Jan 9 '18 at 17:43





There are many cameras supported by gphoto2. This is really cool, as the quality is superior to typical webcam.

– PeterM
Jan 9 '18 at 17:43










2 Answers
2






active

oldest

votes


















6














It turned out that that in fact there was gvfs-gphoto2-volume-monitor process in the background.



Run ps aux | grep gphoto, which might have output like:



peter    25802  2.1  0.1 302504  8736 ?        Ssl  13:10   0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
peter 25814 2.2 0.1 441508 11176 ? Sl 13:10 0:00 /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.3 /org/gtk/gvfs/exec_spaw/21
peter 25835 0.0 0.0 22676 1096 pts/0 S+ 13:10 0:00 grep --color=auto gphoto


First colums is PID (process id), kill them:



kill -9 25802
kill -9 25814


Now gphoto2 can now connect to camera.






share|improve this answer
























  • What to do if the "gvfs-gphoto2-volume-monitor" process keeps starting again? DO we have to manually always kill the process?

    – Zythyr
    Aug 21 '18 at 17:49











  • That's a good question. I don't know how to remove it from startup. Feel free to ask another question, or improve this answer if You figure out this.

    – PeterM
    Aug 21 '18 at 20:40



















0














PeterM's answer works in principle. To make it simpler and quicker I propose the following procedure:



First find all processes which are related to gphoto2



pgrep -fla gphoto2
1236 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
1345 /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.4 /org/gtk/gvfs/exec_spaw/1


if they are the ones shown above you can safely kill these



pkill -f gphoto2


and happily take pictures



gphoto2 --capture-image-and-download --filename pic0001.jpg





share|improve this answer























    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',
    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%2faskubuntu.com%2fquestions%2f993876%2fgphoto2-could-not-claim-the-usb-device%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









    6














    It turned out that that in fact there was gvfs-gphoto2-volume-monitor process in the background.



    Run ps aux | grep gphoto, which might have output like:



    peter    25802  2.1  0.1 302504  8736 ?        Ssl  13:10   0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
    peter 25814 2.2 0.1 441508 11176 ? Sl 13:10 0:00 /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.3 /org/gtk/gvfs/exec_spaw/21
    peter 25835 0.0 0.0 22676 1096 pts/0 S+ 13:10 0:00 grep --color=auto gphoto


    First colums is PID (process id), kill them:



    kill -9 25802
    kill -9 25814


    Now gphoto2 can now connect to camera.






    share|improve this answer
























    • What to do if the "gvfs-gphoto2-volume-monitor" process keeps starting again? DO we have to manually always kill the process?

      – Zythyr
      Aug 21 '18 at 17:49











    • That's a good question. I don't know how to remove it from startup. Feel free to ask another question, or improve this answer if You figure out this.

      – PeterM
      Aug 21 '18 at 20:40
















    6














    It turned out that that in fact there was gvfs-gphoto2-volume-monitor process in the background.



    Run ps aux | grep gphoto, which might have output like:



    peter    25802  2.1  0.1 302504  8736 ?        Ssl  13:10   0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
    peter 25814 2.2 0.1 441508 11176 ? Sl 13:10 0:00 /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.3 /org/gtk/gvfs/exec_spaw/21
    peter 25835 0.0 0.0 22676 1096 pts/0 S+ 13:10 0:00 grep --color=auto gphoto


    First colums is PID (process id), kill them:



    kill -9 25802
    kill -9 25814


    Now gphoto2 can now connect to camera.






    share|improve this answer
























    • What to do if the "gvfs-gphoto2-volume-monitor" process keeps starting again? DO we have to manually always kill the process?

      – Zythyr
      Aug 21 '18 at 17:49











    • That's a good question. I don't know how to remove it from startup. Feel free to ask another question, or improve this answer if You figure out this.

      – PeterM
      Aug 21 '18 at 20:40














    6












    6








    6







    It turned out that that in fact there was gvfs-gphoto2-volume-monitor process in the background.



    Run ps aux | grep gphoto, which might have output like:



    peter    25802  2.1  0.1 302504  8736 ?        Ssl  13:10   0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
    peter 25814 2.2 0.1 441508 11176 ? Sl 13:10 0:00 /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.3 /org/gtk/gvfs/exec_spaw/21
    peter 25835 0.0 0.0 22676 1096 pts/0 S+ 13:10 0:00 grep --color=auto gphoto


    First colums is PID (process id), kill them:



    kill -9 25802
    kill -9 25814


    Now gphoto2 can now connect to camera.






    share|improve this answer













    It turned out that that in fact there was gvfs-gphoto2-volume-monitor process in the background.



    Run ps aux | grep gphoto, which might have output like:



    peter    25802  2.1  0.1 302504  8736 ?        Ssl  13:10   0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
    peter 25814 2.2 0.1 441508 11176 ? Sl 13:10 0:00 /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.3 /org/gtk/gvfs/exec_spaw/21
    peter 25835 0.0 0.0 22676 1096 pts/0 S+ 13:10 0:00 grep --color=auto gphoto


    First colums is PID (process id), kill them:



    kill -9 25802
    kill -9 25814


    Now gphoto2 can now connect to camera.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jan 9 '18 at 12:24









    PeterMPeterM

    244314




    244314













    • What to do if the "gvfs-gphoto2-volume-monitor" process keeps starting again? DO we have to manually always kill the process?

      – Zythyr
      Aug 21 '18 at 17:49











    • That's a good question. I don't know how to remove it from startup. Feel free to ask another question, or improve this answer if You figure out this.

      – PeterM
      Aug 21 '18 at 20:40



















    • What to do if the "gvfs-gphoto2-volume-monitor" process keeps starting again? DO we have to manually always kill the process?

      – Zythyr
      Aug 21 '18 at 17:49











    • That's a good question. I don't know how to remove it from startup. Feel free to ask another question, or improve this answer if You figure out this.

      – PeterM
      Aug 21 '18 at 20:40

















    What to do if the "gvfs-gphoto2-volume-monitor" process keeps starting again? DO we have to manually always kill the process?

    – Zythyr
    Aug 21 '18 at 17:49





    What to do if the "gvfs-gphoto2-volume-monitor" process keeps starting again? DO we have to manually always kill the process?

    – Zythyr
    Aug 21 '18 at 17:49













    That's a good question. I don't know how to remove it from startup. Feel free to ask another question, or improve this answer if You figure out this.

    – PeterM
    Aug 21 '18 at 20:40





    That's a good question. I don't know how to remove it from startup. Feel free to ask another question, or improve this answer if You figure out this.

    – PeterM
    Aug 21 '18 at 20:40













    0














    PeterM's answer works in principle. To make it simpler and quicker I propose the following procedure:



    First find all processes which are related to gphoto2



    pgrep -fla gphoto2
    1236 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
    1345 /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.4 /org/gtk/gvfs/exec_spaw/1


    if they are the ones shown above you can safely kill these



    pkill -f gphoto2


    and happily take pictures



    gphoto2 --capture-image-and-download --filename pic0001.jpg





    share|improve this answer




























      0














      PeterM's answer works in principle. To make it simpler and quicker I propose the following procedure:



      First find all processes which are related to gphoto2



      pgrep -fla gphoto2
      1236 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
      1345 /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.4 /org/gtk/gvfs/exec_spaw/1


      if they are the ones shown above you can safely kill these



      pkill -f gphoto2


      and happily take pictures



      gphoto2 --capture-image-and-download --filename pic0001.jpg





      share|improve this answer


























        0












        0








        0







        PeterM's answer works in principle. To make it simpler and quicker I propose the following procedure:



        First find all processes which are related to gphoto2



        pgrep -fla gphoto2
        1236 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
        1345 /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.4 /org/gtk/gvfs/exec_spaw/1


        if they are the ones shown above you can safely kill these



        pkill -f gphoto2


        and happily take pictures



        gphoto2 --capture-image-and-download --filename pic0001.jpg





        share|improve this answer













        PeterM's answer works in principle. To make it simpler and quicker I propose the following procedure:



        First find all processes which are related to gphoto2



        pgrep -fla gphoto2
        1236 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
        1345 /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.4 /org/gtk/gvfs/exec_spaw/1


        if they are the ones shown above you can safely kill these



        pkill -f gphoto2


        and happily take pictures



        gphoto2 --capture-image-and-download --filename pic0001.jpg






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 22 at 6:50









        Wolfgang FahlWolfgang Fahl

        240212




        240212






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f993876%2fgphoto2-could-not-claim-the-usb-device%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á

            Eduardo VII do Reino Unido