Your message dated Mon, 19 Oct 2015 11:58:29 +0000 (UTC) with message-id <[email protected]> and subject line Re: Bug#801050: virtualbox can't start [solved] [SUCCESS] has caused the Debian Bug report #801050, regarding virtualbox can't start to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 801050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801050 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: virtualbox Version: 5.0.4-dfsg-4 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? in spite of updating twice, following message: The virtual machine 'Deppi-505' has terminated unexpectedly during startup with exit code 1 (0x1). * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? virtualbox still has newer version in archive which sannot be installedby aptitude * What outcome did you expect instead? A working Versiun of virtualbox *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable-updates'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 4.2.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages virtualbox depends on: ii adduser 3.113+nmu3 ii libc6 2.19-22 ii libcurl3-gnutls 7.44.0-2 ii libgcc1 1:5.2.1-17 ii libgsoap7 2.8.22-1 ii libpng12-0 1.2.50-2+b2 ii libpython2.7 2.7.10-4 ii libsdl1.2debian 1.2.15-11 ii libssl1.0.0 1.0.2d-1 ii libstdc++6 5.2.1-17 ii libvncserver1 0.9.10+dfsg-3 ii libvpx2 1.4.0-4 ii libx11-6 2:1.6.3-1 ii libxcursor1 1:1.1.14-1+b1 ii libxext6 2:1.3.3-1 ii libxml2 2.9.2+zdfsg1-4 ii libxmu6 2:1.1.2-1 ii libxt6 1:1.1.4-1+b1 ii python 2.7.9-1 ii python2.7 2.7.10-4 pn python:any <none> ii virtualbox-dkms 5.0.4-dfsg-4 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages virtualbox recommends: ii libgl1-mesa-glx [libgl1] 10.6.8-1 ii libqt4-opengl 4:4.8.7+dfsg-3 ii libqtcore4 4:4.8.7+dfsg-3 ii libqtgui4 4:4.8.7+dfsg-3 ii virtualbox-qt 5.0.4-dfsg-4 Versions of packages virtualbox suggests: ii vde2 2.3.2+r586-2 ii virtualbox-guest-additions-iso 5.0.4-1 -- Configuration Files: /etc/default/virtualbox changed: LOAD_VBOXDRV_MODULE=1 SHUTDOWN_USERS="yx" SHUTDOWN=poweroff -- no debconf information NS_ERROR_FAILURE (0x80004005) Komponente: MachineWrap Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
--- End Message ---
--- Begin Message ---Hi, I don't know what exactly happened, but I'm happy it is fixed now :) cheers, G. Il Sabato 17 Ottobre 2015 16:18, Clemens Haupt <[email protected]> ha scritto: On Thu, Oct 15, 2015 at 05:33:24PM +0000, Gianfranco Costamagna wrote: > >Now: all vboxdrv.ko are gone By dkms. > how? Don't know how, but it was the first step to success. > >And /dev/vboxdrv isn't built > yes sure, it isn't "built", but created after the modprobe command. > install virtualbox-dkms, modprobe it, and you will see it. No. I "purged" all and everything with the name virtualbox. Rebooted. I purged everything with the letters "dkms". Rebooted. I installes kernels headers. Rebooted. I installed dkms, +acpi-calls, dont know why, just for fun, and blcr-dkms- dkms status: acpi-call, 1.1.0, 4.2.0-1-686-pae, i686: installed blcr, 0.8.5: added so, modules could be added, true? The virtualbox without dkms, but with source. That couldn't work and so it didn't. Then virtualbox-dkms. dkms status: acpi-call, 1.1.0, 4.2.0-1-686-pae, i686: installed blcr, 0.8.5: added virtualbox, 5.0.6, 4.2.0-1-686-pae, i686: installed SUCCESS! virtualbox-qt did start, only two machine were damaged by trying to start before. > if not please provide logs. 91667 0 crw------- 1 root root 10, 57 Okt 17 14:02 vboxdrv 91669 0 crw------- 1 root root 10, 56 Okt 17 14:02 vboxdrvu 91675 0 crw------- 1 root root 10, 55 Okt 17 14:02 vboxnetctl 81208 0 drwxr-x--- 3 root vboxusers 60 Okt 17 13:28 vboxusb looks much better now > thanks Thank YOU! Result: Cleaning seems to be most necessary. -- Warum mit PGP verschlüsseln? http://www.pc-fluesterer.info/wordpress/ Verschlüsseln ist einfach. Und hilft ihrem Internetprovider gegen Staatsspitzel. Noch viel sicherer Schutz gegen Schnüfflerbagage: https://geti2p.net/de/ Damit können sogar selbst Windowsnutzer bei mail, surfen und chatten Privatsphäre haben. Die Demokratie muß jeder einzelne selbst schützen.
--- End Message ---
