Bug 6053

Summary:	I updated vbox linux addition to 4.1.16, I no access anymore to mouse and keyboard
Product:	Mageia	Reporter:	Yann COLLETTE <ycollette.nospam>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	stormi-mageia
Version:	2	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	virtualbox	CVE:
Status comment:

Description Yann COLLETTE 2012-05-23 14:27:53 CEST

I have removed virtualbox 4.1.12 from mageia 2 64 bits.
My host is windows XC 64.
I installed virtualbox linux additions 4.1.16 in mageia 2 64 bits (the guest).
Now, I reboot the virtual machine.
After Xwindows starts, I have no access anymore to keyboard and mouse.
I can loggin into kde.

I have reinstalled mageia 3 times to check several combinations:
- remove vbox addition 4.1.12 and install vbox additions 4.1.16
- install vbox additions 4.1.16 without removing vbox additions 4.1.12

The result is always the same.

Yann COLLETTE 2012-05-23 14:28:06 CEST

Hardware: i586 => x86_64

Comment 1 Manuel Hiebel 2012-05-24 19:42:17 CEST

I don't see the need to removing our rpm (guest addition) for the oracle one, since it should work with virtualbox 4.1.16

Comment 2 Yann COLLETTE 2012-05-25 09:40:24 CEST

Yes, I know, that's the solution I used.
But there is a problem when I upgrade the guest additions to 4.1.16.

Comment 3 Manuel Hiebel 2012-05-25 10:43:51 CEST

well you can search in the dmesg, .xsession-errors or in the xorg.log if there is some errors (with ssh), but I'm not sure we can do something

Comment 4 Yann COLLETTE 2012-05-25 10:48:45 CEST

I will try to update the guest additions in a fedora distrib, to see if the problem occurs on this distrib too.

Comment 5 Samuel Verschelde 2013-09-05 14:34:12 CEST

Hi,

did you find out if there's a specific problem about Mageia's virtualbox in Mageia 2 or if it was another type of problem?

Keywords: (none) => NEEDINFO
CC: (none) => stormi

Comment 6 Yann COLLETTE 2013-09-06 09:10:32 CEST

I haven't seen the problem since I upgraded virtualbox on my host windows machine.
So, maybe this bug was virtualbox related.
I close the bug.

Status: NEW => RESOLVED
Resolution: (none) => FIXED