Bug#798979: [Pkg-virtualbox-devel] Bug#798979: Bug#798979: virtualbox: DSA-3359-1 causes VBoxClient to send error message "The VirtualBox kernel service is not running" and to break off.

2015-09-17 Thread Gianfranco Costamagna
Hi Dirk, can you please try the guest additions from here?
http://debomatic-amd64.debian.net/distribution#stable/virtualbox-guest-additions-iso/4.3.30-1+deb8u1/contents

thanks,

G.





Il Giovedì 17 Settembre 2015 10:24, Dirk Olsen  ha 
scritto:


Am 16.09.2015 um 17:56 schrieb Gianfranco Costamagna:

> Hi, following up with an upstream discussion,
>
> can you please remove virtualbox-guest-dkms virtualbox-guest-utils and 
> virtualbox-guest-x11?
>
> [...]


Hi Gianfranco,

removing makes not difference:

my VM (Windows-7) still breaks down.

Beyond that up to now "VBoxGuestAdditions.iso"
(including "virtualbox-guest-utils") is necessary
for using shared folders, as described in the user
manual of VirtualBox.

Greetings

Dirk Olsen



Bug#798979: [Pkg-virtualbox-devel] Bug#798979: Bug#798979: virtualbox: DSA-3359-1 causes VBoxClient to send error message "The VirtualBox kernel service is not running" and to break off.

2015-09-17 Thread Dirk Olsen


Am 16.09.2015 um 17:56 schrieb Gianfranco Costamagna:


Hi, following up with an upstream discussion,

can you please remove virtualbox-guest-dkms virtualbox-guest-utils and 
virtualbox-guest-x11?

[...]



Hi Gianfranco,

removing makes not difference:

my VM (Windows-7) still breaks down.

Beyond that up to now "VBoxGuestAdditions.iso"
(including "virtualbox-guest-utils") is necessary
for using shared folders, as described in the user
manual of VirtualBox.

Greetings

Dirk Olsen



Bug#798979: [Pkg-virtualbox-devel] Bug#798979: Bug#798979: virtualbox: DSA-3359-1 causes VBoxClient to send error message "The VirtualBox kernel service is not running" and to break off.

2015-09-17 Thread Dirk Olsen


Am 17.09.2015 um 12:59 schrieb Gianfranco Costamagna:


Hi Dirk, can you please try the guest additions from here?
http://debomatic-amd64.debian.net/distribution#stable/virtualbox-guest-additions-iso/4.3.30-1+deb8u1/contents


Hi Gianfranco,

I tried, but without success:
Windows-7 still breaks down while "booting".

Here the last lines in /var/log/dpkg.log:

2015-09-17 23:48:48 startup archives install
2015-09-17 23:48:56 upgrade virtualbox-guest-additions-iso:all 4.3.18-3 
4.3.30-1+deb8u1
2015-09-17 23:48:56 status half-configured 
virtualbox-guest-additions-iso:all 4.3.18-3
2015-09-17 23:48:56 status unpacked virtualbox-guest-additions-iso:all 
4.3.18-3
2015-09-17 23:48:56 status half-installed 
virtualbox-guest-additions-iso:all 4.3.18-3
2015-09-17 23:48:59 status half-installed 
virtualbox-guest-additions-iso:all 4.3.18-3
2015-09-17 23:48:59 status unpacked virtualbox-guest-additions-iso:all 
4.3.30-1+deb8u1
2015-09-17 23:48:59 status unpacked virtualbox-guest-additions-iso:all 
4.3.30-1+deb8u1
2015-09-17 23:48:59 configure virtualbox-guest-additions-iso:all 
4.3.30-1+deb8u1 4.3.30-1+deb8u1
2015-09-17 23:48:59 status unpacked virtualbox-guest-additions-iso:all 
4.3.30-1+deb8u1
2015-09-17 23:48:59 status half-configured 
virtualbox-guest-additions-iso:all 4.3.30-1+deb8u1
2015-09-17 23:48:59 status installed virtualbox-guest-additions-iso:all 
4.3.30-1+deb8u1


Sincerely, D.O.



Bug#798979: [Pkg-virtualbox-devel] Bug#798979: Bug#798979: virtualbox: DSA-3359-1 causes VBoxClient to send error message "The VirtualBox kernel service is not running" and to break off.

2015-09-17 Thread Dirk Olsen


Hi Gianfranco,

when "kdm" is starting my grafical account I still receive the error 
message "The VirtualBox kernel service is not running. Exiting."


As Ritesh Raj Sarraf mentioned, DSA-3359-1 was not executed completely, 
and after its failure it sent the following message:


"[]
Job for virtualbox.service failed. See 'systemctl status 
virtualbox.service' and 'journalctl -xn' for details.

invoke-rc.d: initscript virtualbox, action "restart" failed.
virtualbox-qt (4.3.30-dfsg-1+deb8u1) wird eingerichtet ...
virtualbox-guest-utils (4.3.30-dfsg-1+deb8u1) wird eingerichtet ...
virtualbox-guest-x11 (4.3.30-dfsg-1+deb8u1) wird eingerichtet ...
Neue Version der Konfigurationsdatei 
/etc/X11/Xsession.d/98vboxadd-xclient wird installiert ...
update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults

[]"

How to repair this situation, i.e. how can I reach that all start and 
stop actions are again supported, especially the VirtualBox kernel service?


Sincerely, D.O.



Bug#798979: [Pkg-virtualbox-devel] Bug#798979: Bug#798979: virtualbox: DSA-3359-1 causes VBoxClient to send error message "The VirtualBox kernel service is not running" and to break off.

2015-09-16 Thread Ritesh Raj Sarraf
On Tue, 2015-09-15 at 16:39 +0530, Ritesh Raj Sarraf wrote:
> I think this may be the problem. This snippet is present in both vbox
> and vbox-dkms. So while vbox is upgraded, it triggers it in its
> postinst. But vbox-dkms is still not upgraded. Thus this could lead
> to
> version mismatch and failure.
> 
> This may be similar to #798527.
> 
> 
> So if this root cause is correct, the fix (of adding vbox-dkms
> =BinaryVersion to Pre-Depends: of vbox) should work ???


I got the same issue today while upgrading VBox on my machine.


Unpacking quassel-data (1:0.12.2-1) over (1:0.10.0-2.4) ...
Processing triggers for menu (2.1.47) ...
Processing triggers for man-db (2.7.3-1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for mime-support (3.59) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for systemd (225-1) ...
Setting up virtualbox (5.0.4-dfsg-2) ...
Job for virtualbox.service failed because the control process exited
with error code. See "systemctl status virtualbox.service" and
"journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
Setting up virtualbox-qt (5.0.4-dfsg-2) ...
Setting up virtualbox-dkms (5.0.4-dfsg-2) ...
Loading new virtualbox-5.0.4 DKMS files...
Building only for 4.2.0+
Building initial module for 4.2.0+



rrs@learner:~$ sudo systemctl status -l virtualbox.service 
● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox)
   Active: failed (Result: exit-code) since Wed 2015-09-16 11:54:35
IST; 37s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 9078 ExecStop=/etc/init.d/virtualbox stop (code=exited,
status=0/SUCCESS)
  Process: 9102 ExecStart=/etc/init.d/virtualbox start (code=exited,
status=1/FAILURE)

Sep 16 11:54:35 learner systemd[1]: Starting LSB: VirtualBox Linux
kernel module...
Sep 16 11:54:35 learner virtualbox[9102]: Starting VirtualBox kernel
modulesNo suitable module for running kernel found ... failed!
Sep 16 11:54:35 learner virtualbox[9102]: failed!
Sep 16 11:54:35 learner systemd[1]: virtualbox.service: Control process
exited, code=exited status=1
Sep 16 11:54:35 learner systemd[1]: Failed to start LSB: VirtualBox
Linux kernel module.
Sep 16 11:54:35 learner systemd[1]: virtualbox.service: Unit entered
failed state.
Sep 16 11:54:35 learner systemd[1]: virtualbox.service: Failed with
result 'exit-code'.
2015-09-16 / 11:55:13 ♒♒♒☹  => 3  


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


signature.asc
Description: This is a digitally signed message part


Bug#798979: [Pkg-virtualbox-devel] Bug#798979: Bug#798979: virtualbox: DSA-3359-1 causes VBoxClient to send error message "The VirtualBox kernel service is not running" and to break off.

2015-09-16 Thread Gianfranco Costamagna
Hi, following up with an upstream discussion,

can you please remove virtualbox-guest-dkms virtualbox-guest-utils and 
virtualbox-guest-x11?

thanks,


G.





Il Mercoledì 16 Settembre 2015 8:36, Ritesh Raj Sarraf  ha 
scritto:
On Tue, 2015-09-15 at 16:39 +0530, Ritesh Raj Sarraf wrote:
> I think this may be the problem. This snippet is present in both vbox
> and vbox-dkms. So while vbox is upgraded, it triggers it in its
> postinst. But vbox-dkms is still not upgraded. Thus this could lead
> to
> version mismatch and failure.
> 
> This may be similar to #798527.
> 
> 
> So if this root cause is correct, the fix (of adding vbox-dkms
> =BinaryVersion to Pre-Depends: of vbox) should work ???


I got the same issue today while upgrading VBox on my machine.


Unpacking quassel-data (1:0.12.2-1) over (1:0.10.0-2.4) ...
Processing triggers for menu (2.1.47) ...
Processing triggers for man-db (2.7.3-1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for mime-support (3.59) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for systemd (225-1) ...
Setting up virtualbox (5.0.4-dfsg-2) ...
Job for virtualbox.service failed because the control process exited
with error code. See "systemctl status virtualbox.service" and
"journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
Setting up virtualbox-qt (5.0.4-dfsg-2) ...
Setting up virtualbox-dkms (5.0.4-dfsg-2) ...
Loading new virtualbox-5.0.4 DKMS files...
Building only for 4.2.0+
Building initial module for 4.2.0+



rrs@learner:~$ sudo systemctl status -l virtualbox.service 
● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox)
   Active: failed (Result: exit-code) since Wed 2015-09-16 11:54:35
IST; 37s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 9078 ExecStop=/etc/init.d/virtualbox stop (code=exited,
status=0/SUCCESS)
  Process: 9102 ExecStart=/etc/init.d/virtualbox start (code=exited,
status=1/FAILURE)

Sep 16 11:54:35 learner systemd[1]: Starting LSB: VirtualBox Linux
kernel module...
Sep 16 11:54:35 learner virtualbox[9102]: Starting VirtualBox kernel
modulesNo suitable module for running kernel found ... failed!
Sep 16 11:54:35 learner virtualbox[9102]: failed!
Sep 16 11:54:35 learner systemd[1]: virtualbox.service: Control process
exited, code=exited status=1
Sep 16 11:54:35 learner systemd[1]: Failed to start LSB: VirtualBox
Linux kernel module.
Sep 16 11:54:35 learner systemd[1]: virtualbox.service: Unit entered
failed state.
Sep 16 11:54:35 learner systemd[1]: virtualbox.service: Failed with
result 'exit-code'.
2015-09-16 / 11:55:13 ♒♒♒☹  => 3  



-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System