Issue 936: grmldailysid101125: No keyboard, no mouse using X in virtualbox - GRML issue tracker

Title	grmldailysid101125: No keyboard, no mouse using X in virtualbox
Priority	bug	Status	resolved
Superseder		Nosy List	ch, grml.fksi, mru
Assigned To		Topics

Created on 2010-11-26.19:16:40 by grml.fksi, last changed 2011-05-09.20:13:30 by mika.

Files
File name	Uploaded	Type	Edit	Remove
with-xorg-Xorg.0.log	grml.fksi, 2010-11-26.19:16:36	text/plain
without-xorg-Xorg.0.log	grml.fksi, 2010-11-26.19:16:39	text/plain

Messages
msg3767 (view)	Author: mika	Date: 2011-05-09.20:13:30
This issues was just set to "fixed-in-git", closing therefore as the issue should be fixed.
msg3521 (view)	Author: mru	Date: 2010-11-26.20:27:44
Just debugged with OP and ch the issue. Seems that the copied xorg.conf.vbox file (which was done in grml-autoconfig) caused the issue. I removed the functions in grml-autoconfig. Qemu is nowadays handled by grml-x itself and virtualbox/vmware should not need a special configuration
msg3520 (view)	Author: grml.fksi	Date: 2010-11-26.19:16:39
Hi, checking out grmldailysid101125 as a virtualbox guest I noticed neither mouse nor keyboard were functional after starting X (using the menu at the end of the grml startup). Attached are two Xorg.0.log files. The first one (with-xorg-Xorg.0.log) was written during regular startup, i.e. using the prepared xorg.conf{,.virtualbox} (md5sum ec735899424f1c5d5b1637329bdfb9bb). Especially, (EE) Failed to load module "kbd" (module does not exist, 0) looks rather odd. The second one (without-xorg-Xorg.0.log) was created during another boot with xorg.conf intentionally removed. Same unusability of X, though. Regards, Christoph

History
Date	User	Action	Args
2011-05-09 20:13:30	mika	set	status: fixed-in-git -> resolved nosy: mru, ch, grml.fksi messages: + msg3767
2010-11-26 20:27:44	mru	set	priority: bug status: unread -> fixed-in-git messages: + msg3521 nosy: + ch, mru
2010-11-26 19:16:40	grml.fksi	create