Upgrade to 18.04 LTS from 16.04 LTS broke VMware Workstation 12.5.9












0















After upgrading Ubuntu from 16.04 LTS to 18.04 LTS, VMware Workstation 12.5.9 will not start. I uninstalled VMware then reinstalled it. Still get this message:



/usr/lib/vmware/bin/vmware-modconfig: Relink /lib/x86_64-linux-gnu/libbsd.so.0 with /lib/x86_64-linux-gnu/librt.so.1 for IFUNC symbol clock_gettime










share|improve this question





























    0















    After upgrading Ubuntu from 16.04 LTS to 18.04 LTS, VMware Workstation 12.5.9 will not start. I uninstalled VMware then reinstalled it. Still get this message:



    /usr/lib/vmware/bin/vmware-modconfig: Relink /lib/x86_64-linux-gnu/libbsd.so.0 with /lib/x86_64-linux-gnu/librt.so.1 for IFUNC symbol clock_gettime










    share|improve this question



























      0












      0








      0








      After upgrading Ubuntu from 16.04 LTS to 18.04 LTS, VMware Workstation 12.5.9 will not start. I uninstalled VMware then reinstalled it. Still get this message:



      /usr/lib/vmware/bin/vmware-modconfig: Relink /lib/x86_64-linux-gnu/libbsd.so.0 with /lib/x86_64-linux-gnu/librt.so.1 for IFUNC symbol clock_gettime










      share|improve this question
















      After upgrading Ubuntu from 16.04 LTS to 18.04 LTS, VMware Workstation 12.5.9 will not start. I uninstalled VMware then reinstalled it. Still get this message:



      /usr/lib/vmware/bin/vmware-modconfig: Relink /lib/x86_64-linux-gnu/libbsd.so.0 with /lib/x86_64-linux-gnu/librt.so.1 for IFUNC symbol clock_gettime







      18.04 upgrade vmware-workstation






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 18 at 20:50









      mature

      2,2024933




      2,2024933










      asked Mar 18 at 20:26









      stevejstevej

      1




      1






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Please open a terminal end execute the command



          sudo vmware-modconfig --console --install-all


          TL;DR



          When the kernel is updated, VMWare must be relinked against changed modules. The program listed above accomplishes this function, and older version of VMWare can be reconfigured with sudo /usr/bin/vmware-config.pl.



          Source of information: VMware Knowledge Base






          share|improve this answer
























          • vmware-modconfig gives the message "Failed to get gcc information". /usr/bin/vmware-config.pl does not exist.

            – stevej
            Mar 19 at 15:04











          • The "failed to get gcc information" is concerning - tdo ou have build-essential intsalled? I would be tempted to sudo apt install --reinstall build-essential

            – Charles Green
            Mar 19 at 15:10











          • I reinstalled build-essential and tried again. Get the same "Failed to get gcc information" message. I've since upgraded to vmware workstation 15.0.3. This has fixed the problem.

            – stevej
            Mar 19 at 19:41












          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%2f1126739%2fupgrade-to-18-04-lts-from-16-04-lts-broke-vmware-workstation-12-5-9%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














          Please open a terminal end execute the command



          sudo vmware-modconfig --console --install-all


          TL;DR



          When the kernel is updated, VMWare must be relinked against changed modules. The program listed above accomplishes this function, and older version of VMWare can be reconfigured with sudo /usr/bin/vmware-config.pl.



          Source of information: VMware Knowledge Base






          share|improve this answer
























          • vmware-modconfig gives the message "Failed to get gcc information". /usr/bin/vmware-config.pl does not exist.

            – stevej
            Mar 19 at 15:04











          • The "failed to get gcc information" is concerning - tdo ou have build-essential intsalled? I would be tempted to sudo apt install --reinstall build-essential

            – Charles Green
            Mar 19 at 15:10











          • I reinstalled build-essential and tried again. Get the same "Failed to get gcc information" message. I've since upgraded to vmware workstation 15.0.3. This has fixed the problem.

            – stevej
            Mar 19 at 19:41
















          0














          Please open a terminal end execute the command



          sudo vmware-modconfig --console --install-all


          TL;DR



          When the kernel is updated, VMWare must be relinked against changed modules. The program listed above accomplishes this function, and older version of VMWare can be reconfigured with sudo /usr/bin/vmware-config.pl.



          Source of information: VMware Knowledge Base






          share|improve this answer
























          • vmware-modconfig gives the message "Failed to get gcc information". /usr/bin/vmware-config.pl does not exist.

            – stevej
            Mar 19 at 15:04











          • The "failed to get gcc information" is concerning - tdo ou have build-essential intsalled? I would be tempted to sudo apt install --reinstall build-essential

            – Charles Green
            Mar 19 at 15:10











          • I reinstalled build-essential and tried again. Get the same "Failed to get gcc information" message. I've since upgraded to vmware workstation 15.0.3. This has fixed the problem.

            – stevej
            Mar 19 at 19:41














          0












          0








          0







          Please open a terminal end execute the command



          sudo vmware-modconfig --console --install-all


          TL;DR



          When the kernel is updated, VMWare must be relinked against changed modules. The program listed above accomplishes this function, and older version of VMWare can be reconfigured with sudo /usr/bin/vmware-config.pl.



          Source of information: VMware Knowledge Base






          share|improve this answer













          Please open a terminal end execute the command



          sudo vmware-modconfig --console --install-all


          TL;DR



          When the kernel is updated, VMWare must be relinked against changed modules. The program listed above accomplishes this function, and older version of VMWare can be reconfigured with sudo /usr/bin/vmware-config.pl.



          Source of information: VMware Knowledge Base







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 18 at 22:49









          Charles GreenCharles Green

          14.1k73859




          14.1k73859













          • vmware-modconfig gives the message "Failed to get gcc information". /usr/bin/vmware-config.pl does not exist.

            – stevej
            Mar 19 at 15:04











          • The "failed to get gcc information" is concerning - tdo ou have build-essential intsalled? I would be tempted to sudo apt install --reinstall build-essential

            – Charles Green
            Mar 19 at 15:10











          • I reinstalled build-essential and tried again. Get the same "Failed to get gcc information" message. I've since upgraded to vmware workstation 15.0.3. This has fixed the problem.

            – stevej
            Mar 19 at 19:41



















          • vmware-modconfig gives the message "Failed to get gcc information". /usr/bin/vmware-config.pl does not exist.

            – stevej
            Mar 19 at 15:04











          • The "failed to get gcc information" is concerning - tdo ou have build-essential intsalled? I would be tempted to sudo apt install --reinstall build-essential

            – Charles Green
            Mar 19 at 15:10











          • I reinstalled build-essential and tried again. Get the same "Failed to get gcc information" message. I've since upgraded to vmware workstation 15.0.3. This has fixed the problem.

            – stevej
            Mar 19 at 19:41

















          vmware-modconfig gives the message "Failed to get gcc information". /usr/bin/vmware-config.pl does not exist.

          – stevej
          Mar 19 at 15:04





          vmware-modconfig gives the message "Failed to get gcc information". /usr/bin/vmware-config.pl does not exist.

          – stevej
          Mar 19 at 15:04













          The "failed to get gcc information" is concerning - tdo ou have build-essential intsalled? I would be tempted to sudo apt install --reinstall build-essential

          – Charles Green
          Mar 19 at 15:10





          The "failed to get gcc information" is concerning - tdo ou have build-essential intsalled? I would be tempted to sudo apt install --reinstall build-essential

          – Charles Green
          Mar 19 at 15:10













          I reinstalled build-essential and tried again. Get the same "Failed to get gcc information" message. I've since upgraded to vmware workstation 15.0.3. This has fixed the problem.

          – stevej
          Mar 19 at 19:41





          I reinstalled build-essential and tried again. Get the same "Failed to get gcc information" message. I've since upgraded to vmware workstation 15.0.3. This has fixed the problem.

          – stevej
          Mar 19 at 19:41


















          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%2f1126739%2fupgrade-to-18-04-lts-from-16-04-lts-broke-vmware-workstation-12-5-9%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

          Category:香港粉麵

          List *all* the tuples!

          Channel [V]