How to fix Startup Disk Creator which ends in an unhandled exception?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
2
down vote

favorite












I am starting the ubuntu start up disk creator (usb-creator-gtk) on Ubuntu 17.10 (4.13.0-37-generic) and getting this dialog:



enter image description here



I already reinstalled it by:



sudo apt remove usb-creator-gtk
sudo apt autoremove
sudo apt install usb-creator-gtk


And I checked its installation path:



whereis usb-creator-gtk
usb-creator-gtk: /usr/bin/usb-creator-gtk /usr/share/man/man8/usb-creator-gtk.8.gz


And I tried to start it directly with:



/usr/bin/usb-creator-gtk


And i did a hexdump which showes there is no 0xd9 at position two. There is an 0x21:



hd -n 32 /usr/bin/usb-creator-gtk
00000000 23 21 2f 75 73 72 2f 62 69 6e 2f 70 79 74 68 6f |#!/usr/bin/pytho|
00000010 6e 33 0a 0a 23 20 43 6f 70 79 72 69 67 68 74 20 |n3..# Copyright |


But still the same issue.



How to fix Startup Disk Creator which ends in an exception?










share|improve this question



























    up vote
    2
    down vote

    favorite












    I am starting the ubuntu start up disk creator (usb-creator-gtk) on Ubuntu 17.10 (4.13.0-37-generic) and getting this dialog:



    enter image description here



    I already reinstalled it by:



    sudo apt remove usb-creator-gtk
    sudo apt autoremove
    sudo apt install usb-creator-gtk


    And I checked its installation path:



    whereis usb-creator-gtk
    usb-creator-gtk: /usr/bin/usb-creator-gtk /usr/share/man/man8/usb-creator-gtk.8.gz


    And I tried to start it directly with:



    /usr/bin/usb-creator-gtk


    And i did a hexdump which showes there is no 0xd9 at position two. There is an 0x21:



    hd -n 32 /usr/bin/usb-creator-gtk
    00000000 23 21 2f 75 73 72 2f 62 69 6e 2f 70 79 74 68 6f |#!/usr/bin/pytho|
    00000010 6e 33 0a 0a 23 20 43 6f 70 79 72 69 67 68 74 20 |n3..# Copyright |


    But still the same issue.



    How to fix Startup Disk Creator which ends in an exception?










    share|improve this question

























      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      I am starting the ubuntu start up disk creator (usb-creator-gtk) on Ubuntu 17.10 (4.13.0-37-generic) and getting this dialog:



      enter image description here



      I already reinstalled it by:



      sudo apt remove usb-creator-gtk
      sudo apt autoremove
      sudo apt install usb-creator-gtk


      And I checked its installation path:



      whereis usb-creator-gtk
      usb-creator-gtk: /usr/bin/usb-creator-gtk /usr/share/man/man8/usb-creator-gtk.8.gz


      And I tried to start it directly with:



      /usr/bin/usb-creator-gtk


      And i did a hexdump which showes there is no 0xd9 at position two. There is an 0x21:



      hd -n 32 /usr/bin/usb-creator-gtk
      00000000 23 21 2f 75 73 72 2f 62 69 6e 2f 70 79 74 68 6f |#!/usr/bin/pytho|
      00000010 6e 33 0a 0a 23 20 43 6f 70 79 72 69 67 68 74 20 |n3..# Copyright |


      But still the same issue.



      How to fix Startup Disk Creator which ends in an exception?










      share|improve this question















      I am starting the ubuntu start up disk creator (usb-creator-gtk) on Ubuntu 17.10 (4.13.0-37-generic) and getting this dialog:



      enter image description here



      I already reinstalled it by:



      sudo apt remove usb-creator-gtk
      sudo apt autoremove
      sudo apt install usb-creator-gtk


      And I checked its installation path:



      whereis usb-creator-gtk
      usb-creator-gtk: /usr/bin/usb-creator-gtk /usr/share/man/man8/usb-creator-gtk.8.gz


      And I tried to start it directly with:



      /usr/bin/usb-creator-gtk


      And i did a hexdump which showes there is no 0xd9 at position two. There is an 0x21:



      hd -n 32 /usr/bin/usb-creator-gtk
      00000000 23 21 2f 75 73 72 2f 62 69 6e 2f 70 79 74 68 6f |#!/usr/bin/pytho|
      00000010 6e 33 0a 0a 23 20 43 6f 70 79 72 69 67 68 74 20 |n3..# Copyright |


      But still the same issue.



      How to fix Startup Disk Creator which ends in an exception?







      python 17.10 python3 startup-disk-creator






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 28 at 11:15









      karel

      50.7k11107127




      50.7k11107127










      asked Mar 28 at 11:09









      eDeviser

      7752626




      7752626




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          Create a bug report



          This looks like a bug that affects Ubuntu 17.10 in your computer. I suggest that you create a bug report at Launchpad.



          Edit: I tested in my 'testing Ubuntu 17.10 amd64 installed system', and it works to install (clone) Lubuntu 17.10.1 amd64 with the Startup Disk Creator. So I cannot report the bug. Of course, we have different hardware, but another difference could be the installation. My system was a fresh installation from the 17.10 iso file, and kept up to date. Was your system upgraded from a previous version of Ubuntu?



          Use another tool



          Until it is fixed, I suggest that you use another tool to create a USB boot drive,



          • Disks alias gnome-disks (which comes with Ubuntu)



          • mkusb which is installed via a PPA



            sudo add-apt-repository universe # only for *live* standard Ubuntu

            sudo add-apt-repository ppa:mkusb/ppa # and press Enter
            sudo apt-get update
            sudo apt-get install mkusb mkusb-nox usb-pack-efi






          share|improve this answer






















          • Yep, I think I started once with Ubuntu 15, walking through all releases. Don't want to setup the system from scratch. Hopefully this 'upgrade-bug' is obsolete with the next update to 18.04.
            – eDeviser
            Mar 28 at 12:24










          • @eDeviser, Yes, let us hope so.
            – sudodus
            Mar 28 at 14:27










          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: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          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%2f1019932%2fhow-to-fix-startup-disk-creator-which-ends-in-an-unhandled-exception%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          2
          down vote



          accepted










          Create a bug report



          This looks like a bug that affects Ubuntu 17.10 in your computer. I suggest that you create a bug report at Launchpad.



          Edit: I tested in my 'testing Ubuntu 17.10 amd64 installed system', and it works to install (clone) Lubuntu 17.10.1 amd64 with the Startup Disk Creator. So I cannot report the bug. Of course, we have different hardware, but another difference could be the installation. My system was a fresh installation from the 17.10 iso file, and kept up to date. Was your system upgraded from a previous version of Ubuntu?



          Use another tool



          Until it is fixed, I suggest that you use another tool to create a USB boot drive,



          • Disks alias gnome-disks (which comes with Ubuntu)



          • mkusb which is installed via a PPA



            sudo add-apt-repository universe # only for *live* standard Ubuntu

            sudo add-apt-repository ppa:mkusb/ppa # and press Enter
            sudo apt-get update
            sudo apt-get install mkusb mkusb-nox usb-pack-efi






          share|improve this answer






















          • Yep, I think I started once with Ubuntu 15, walking through all releases. Don't want to setup the system from scratch. Hopefully this 'upgrade-bug' is obsolete with the next update to 18.04.
            – eDeviser
            Mar 28 at 12:24










          • @eDeviser, Yes, let us hope so.
            – sudodus
            Mar 28 at 14:27














          up vote
          2
          down vote



          accepted










          Create a bug report



          This looks like a bug that affects Ubuntu 17.10 in your computer. I suggest that you create a bug report at Launchpad.



          Edit: I tested in my 'testing Ubuntu 17.10 amd64 installed system', and it works to install (clone) Lubuntu 17.10.1 amd64 with the Startup Disk Creator. So I cannot report the bug. Of course, we have different hardware, but another difference could be the installation. My system was a fresh installation from the 17.10 iso file, and kept up to date. Was your system upgraded from a previous version of Ubuntu?



          Use another tool



          Until it is fixed, I suggest that you use another tool to create a USB boot drive,



          • Disks alias gnome-disks (which comes with Ubuntu)



          • mkusb which is installed via a PPA



            sudo add-apt-repository universe # only for *live* standard Ubuntu

            sudo add-apt-repository ppa:mkusb/ppa # and press Enter
            sudo apt-get update
            sudo apt-get install mkusb mkusb-nox usb-pack-efi






          share|improve this answer






















          • Yep, I think I started once with Ubuntu 15, walking through all releases. Don't want to setup the system from scratch. Hopefully this 'upgrade-bug' is obsolete with the next update to 18.04.
            – eDeviser
            Mar 28 at 12:24










          • @eDeviser, Yes, let us hope so.
            – sudodus
            Mar 28 at 14:27












          up vote
          2
          down vote



          accepted







          up vote
          2
          down vote



          accepted






          Create a bug report



          This looks like a bug that affects Ubuntu 17.10 in your computer. I suggest that you create a bug report at Launchpad.



          Edit: I tested in my 'testing Ubuntu 17.10 amd64 installed system', and it works to install (clone) Lubuntu 17.10.1 amd64 with the Startup Disk Creator. So I cannot report the bug. Of course, we have different hardware, but another difference could be the installation. My system was a fresh installation from the 17.10 iso file, and kept up to date. Was your system upgraded from a previous version of Ubuntu?



          Use another tool



          Until it is fixed, I suggest that you use another tool to create a USB boot drive,



          • Disks alias gnome-disks (which comes with Ubuntu)



          • mkusb which is installed via a PPA



            sudo add-apt-repository universe # only for *live* standard Ubuntu

            sudo add-apt-repository ppa:mkusb/ppa # and press Enter
            sudo apt-get update
            sudo apt-get install mkusb mkusb-nox usb-pack-efi






          share|improve this answer














          Create a bug report



          This looks like a bug that affects Ubuntu 17.10 in your computer. I suggest that you create a bug report at Launchpad.



          Edit: I tested in my 'testing Ubuntu 17.10 amd64 installed system', and it works to install (clone) Lubuntu 17.10.1 amd64 with the Startup Disk Creator. So I cannot report the bug. Of course, we have different hardware, but another difference could be the installation. My system was a fresh installation from the 17.10 iso file, and kept up to date. Was your system upgraded from a previous version of Ubuntu?



          Use another tool



          Until it is fixed, I suggest that you use another tool to create a USB boot drive,



          • Disks alias gnome-disks (which comes with Ubuntu)



          • mkusb which is installed via a PPA



            sudo add-apt-repository universe # only for *live* standard Ubuntu

            sudo add-apt-repository ppa:mkusb/ppa # and press Enter
            sudo apt-get update
            sudo apt-get install mkusb mkusb-nox usb-pack-efi







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Mar 28 at 11:56

























          answered Mar 28 at 11:24









          sudodus

          20.2k32667




          20.2k32667











          • Yep, I think I started once with Ubuntu 15, walking through all releases. Don't want to setup the system from scratch. Hopefully this 'upgrade-bug' is obsolete with the next update to 18.04.
            – eDeviser
            Mar 28 at 12:24










          • @eDeviser, Yes, let us hope so.
            – sudodus
            Mar 28 at 14:27
















          • Yep, I think I started once with Ubuntu 15, walking through all releases. Don't want to setup the system from scratch. Hopefully this 'upgrade-bug' is obsolete with the next update to 18.04.
            – eDeviser
            Mar 28 at 12:24










          • @eDeviser, Yes, let us hope so.
            – sudodus
            Mar 28 at 14:27















          Yep, I think I started once with Ubuntu 15, walking through all releases. Don't want to setup the system from scratch. Hopefully this 'upgrade-bug' is obsolete with the next update to 18.04.
          – eDeviser
          Mar 28 at 12:24




          Yep, I think I started once with Ubuntu 15, walking through all releases. Don't want to setup the system from scratch. Hopefully this 'upgrade-bug' is obsolete with the next update to 18.04.
          – eDeviser
          Mar 28 at 12:24












          @eDeviser, Yes, let us hope so.
          – sudodus
          Mar 28 at 14:27




          @eDeviser, Yes, let us hope so.
          – sudodus
          Mar 28 at 14:27

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1019932%2fhow-to-fix-startup-disk-creator-which-ends-in-an-unhandled-exception%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          Which professions warranted travel in Medieval times?

          How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

          Trouble downloading packages list due to a “Hash sum mismatch” error