Cannot install virtualbox on 18.04 [closed]

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








up vote
1
down vote

favorite
1












I had Virtualbox installed fine on 18.04 but after an upgrade (sudo apt upgrade) this morning it doesn't seem to work:



Loading new virtualbox-5.2.10 DKMS files...
Building for 4.15.0-15-generic
Building initial module for 4.15.0-15-generic
Done.
At main.c:281:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:81
kmodsign: /var/lib/dkms/virtualbox/5.2.10/4.15.0-15-generic/x86_64/module/virtualbox.ko: No such file or directory
dpkg: error processing package virtualbox-dkms (--configure):
 installed virtualbox-dkms package post-installation script subprocess returned error exit status 1


Is this a temporary problem with the repos or something wrong my end?



EDIT: bug report




virtualbox




share|improve this question














closed as off-topic by Arronical, karel, fkraiem, pomsky, heynnema Apr 23 at 19:37


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – Arronical, karel, fkraiem, pomsky, heynnema
If this question can be reworded to fit the rules in the help center, please edit the question.








  • 1




    virtualbox has been working with 18.04 for weeks now. It was until the upgrade from 5.2.10-dfsg-1 to 5.2.10-dfsg-2 came out that this problem started for me.
    – General Redneck
    Apr 23 at 13:27














up vote
1
down vote

favorite
1












I had Virtualbox installed fine on 18.04 but after an upgrade (sudo apt upgrade) this morning it doesn't seem to work:



Loading new virtualbox-5.2.10 DKMS files...
Building for 4.15.0-15-generic
Building initial module for 4.15.0-15-generic
Done.
At main.c:281:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:81
kmodsign: /var/lib/dkms/virtualbox/5.2.10/4.15.0-15-generic/x86_64/module/virtualbox.ko: No such file or directory
dpkg: error processing package virtualbox-dkms (--configure):
 installed virtualbox-dkms package post-installation script subprocess returned error exit status 1


Is this a temporary problem with the repos or something wrong my end?



EDIT: bug report




virtualbox




share|improve this question














closed as off-topic by Arronical, karel, fkraiem, pomsky, heynnema Apr 23 at 19:37


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – Arronical, karel, fkraiem, pomsky, heynnema
If this question can be reworded to fit the rules in the help center, please edit the question.








  • 1




    virtualbox has been working with 18.04 for weeks now. It was until the upgrade from 5.2.10-dfsg-1 to 5.2.10-dfsg-2 came out that this problem started for me.
    – General Redneck
    Apr 23 at 13:27












up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





I had Virtualbox installed fine on 18.04 but after an upgrade (sudo apt upgrade) this morning it doesn't seem to work:



Loading new virtualbox-5.2.10 DKMS files...
Building for 4.15.0-15-generic
Building initial module for 4.15.0-15-generic
Done.
At main.c:281:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:81
kmodsign: /var/lib/dkms/virtualbox/5.2.10/4.15.0-15-generic/x86_64/module/virtualbox.ko: No such file or directory
dpkg: error processing package virtualbox-dkms (--configure):
 installed virtualbox-dkms package post-installation script subprocess returned error exit status 1


Is this a temporary problem with the repos or something wrong my end?



EDIT: bug report




virtualbox




share|improve this question














I had Virtualbox installed fine on 18.04 but after an upgrade (sudo apt upgrade) this morning it doesn't seem to work:



Loading new virtualbox-5.2.10 DKMS files...
Building for 4.15.0-15-generic
Building initial module for 4.15.0-15-generic
Done.
At main.c:281:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:81
kmodsign: /var/lib/dkms/virtualbox/5.2.10/4.15.0-15-generic/x86_64/module/virtualbox.ko: No such file or directory
dpkg: error processing package virtualbox-dkms (--configure):
 installed virtualbox-dkms package post-installation script subprocess returned error exit status 1


Is this a temporary problem with the repos or something wrong my end?



EDIT: bug report





virtualbox





share|improve this question













share|improve this question




share|improve this question








edited Apr 23 at 11:05

























asked Apr 23 at 10:40









artfulrobot

3,894114174




3,894114174




closed as off-topic by Arronical, karel, fkraiem, pomsky, heynnema Apr 23 at 19:37


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – Arronical, karel, fkraiem, pomsky, heynnema
If this question can be reworded to fit the rules in the help center, please edit the question.




closed as off-topic by Arronical, karel, fkraiem, pomsky, heynnema Apr 23 at 19:37


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – Arronical, karel, fkraiem, pomsky, heynnema
If this question can be reworded to fit the rules in the help center, please edit the question.







  • 1




    virtualbox has been working with 18.04 for weeks now. It was until the upgrade from 5.2.10-dfsg-1 to 5.2.10-dfsg-2 came out that this problem started for me.
    – General Redneck
    Apr 23 at 13:27












  • 1




    virtualbox has been working with 18.04 for weeks now. It was until the upgrade from 5.2.10-dfsg-1 to 5.2.10-dfsg-2 came out that this problem started for me.
    – General Redneck
    Apr 23 at 13:27







1




1




virtualbox has been working with 18.04 for weeks now. It was until the upgrade from 5.2.10-dfsg-1 to 5.2.10-dfsg-2 came out that this problem started for me.
– General Redneck
Apr 23 at 13:27




virtualbox has been working with 18.04 for weeks now. It was until the upgrade from 5.2.10-dfsg-1 to 5.2.10-dfsg-2 came out that this problem started for me.
– General Redneck
Apr 23 at 13:27










1 Answer
1






active

oldest

votes

















up vote
3
down vote



accepted










Ok the answer for now is actually to uninstall the ubuntu apt version of Virtualbox and go with the package over on Virtualbox's site. https://www.virtualbox.org/wiki/Linux_Downloads You will clearly see the one marked Bionic. Doing some digging and dfsg-2 is coming from http://us.archive.ubuntu.com/ubuntu bionic/multiverse. You might try also seeing if the following the Debian based Linux distributions instructions produces a stabler build. I haven't done that yet.






share|improve this answer



























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    3
    down vote



    accepted










    Ok the answer for now is actually to uninstall the ubuntu apt version of Virtualbox and go with the package over on Virtualbox's site. https://www.virtualbox.org/wiki/Linux_Downloads You will clearly see the one marked Bionic. Doing some digging and dfsg-2 is coming from http://us.archive.ubuntu.com/ubuntu bionic/multiverse. You might try also seeing if the following the Debian based Linux distributions instructions produces a stabler build. I haven't done that yet.






    share|improve this answer
























      up vote
      3
      down vote



      accepted










      Ok the answer for now is actually to uninstall the ubuntu apt version of Virtualbox and go with the package over on Virtualbox's site. https://www.virtualbox.org/wiki/Linux_Downloads You will clearly see the one marked Bionic. Doing some digging and dfsg-2 is coming from http://us.archive.ubuntu.com/ubuntu bionic/multiverse. You might try also seeing if the following the Debian based Linux distributions instructions produces a stabler build. I haven't done that yet.






      share|improve this answer






















        up vote
        3
        down vote



        accepted







        up vote
        3
        down vote



        accepted






        Ok the answer for now is actually to uninstall the ubuntu apt version of Virtualbox and go with the package over on Virtualbox's site. https://www.virtualbox.org/wiki/Linux_Downloads You will clearly see the one marked Bionic. Doing some digging and dfsg-2 is coming from http://us.archive.ubuntu.com/ubuntu bionic/multiverse. You might try also seeing if the following the Debian based Linux distributions instructions produces a stabler build. I haven't done that yet.






        share|improve this answer












        Ok the answer for now is actually to uninstall the ubuntu apt version of Virtualbox and go with the package over on Virtualbox's site. https://www.virtualbox.org/wiki/Linux_Downloads You will clearly see the one marked Bionic. Doing some digging and dfsg-2 is coming from http://us.archive.ubuntu.com/ubuntu bionic/multiverse. You might try also seeing if the following the Debian based Linux distributions instructions produces a stabler build. I haven't done that yet.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 23 at 13:44









        General Redneck

        1463




        1463












            -

            Popular posts from this blog

            pylint3 and pip3 broken

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have tried sudo apt remove --purge on various packages. I get the same when I reinstall. I have also tried reinstall using aptitude. This does not work. My current workaround is to run pylint3 as root, which works, but is bad practice. pip3 $ pip3 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 33, in vendored __import__(vendored_name, globals(), locals(), level=0) ImportError: No module named 'pip._vendor.pkg_resources' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/pip3", line 9, in <module> from pip import main File "/usr/lib/python3/dist-packages/pip/__init__.py", line 13, in <module> from pip.exceptions import InstallationError, CommandError, PipError File "/usr/lib/python3/dist-packages/pip/exceptions.py", line 6, ...
            Read more

            Missing snmpget and snmpwalk

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried to install it with: apt-get install net-snmp-utils but I have error message: Unable to locate package. I have also check what from SNMP is preinstalled and there is: libsnmp-base libsnmp30:amd64 snmp-mibs-downloader snmpd snmptrapd snmptrapfmt How can I install snmpget and snmpwalk ? snmp zabbix share | improve this question edited Jan 29 at 10:10 Yaron 8,552 7 18 38 asked Jan 29 at 9:51 Alfista 1 apt install snmp perhaps ? If named differently - apt cache snmp – fugitive Jan 29 at 10:00 add a comment  |  up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried...
            Read more

            How to enroll fingerprints to Ubuntu 17.10 with VFS491

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I decided to switch from Windows to Ubuntu 17.10, I meet it like 8 years ago and I didn't decided to switch until now (haha). Well, my actual device is an HP Probook 4540s with a Validity fingerprint sensor (VFS491). The fingerprint sensor worked fine on Windows but I can't get it to work in Ubuntu. The device is recognized as 138a:003d but is not detected as a fingerprint scanner by some apps like Fingerprint GUI. I want to use the fingerprint scanner to log in into my user account in Ubuntu but it doesn't supports fingerprints without special software and the drivers of the fingerprint scanner are available for Windows but not for any Linux distribution. I found something on GitHub (https://github.com/eekpie/libfprint) about the integration of the VFS491 in libfprint and I think it can help but I don't know what to do with it, so that's why I need the help of the community to do it since I am...
            Read more