Xnest: (EE) config/hal: NewInputDeviceRequest failed (2)

onkelfusspilz

If I run Xnest with for example

zixnub · Posted: Wed Aug 26, 2009 9:37 pm Post subject:

My Xnest gives the same output about the input device and hal but starts up just fine. Something else must be off (I'm also on ~amd64), does

onkelfusspilz · Posted: Wed Aug 26, 2009 9:58 pm Post subject:

Hi zixnub,

ok I see "-ac" stands for disable access control. But it had not changed the behaviour of Xnest. It is hard to discribe, but Xnest connects to the display and I can watch the logonscreen of kdm from the remote machine for a tenth of a second, then the complete Xnest window comes down and reinitialises again.
The "-ac" was worth a try, thank you for the hint.

Oh and I should mention: If I use "X" isntead of "Xnest" all works perfectly fine. I use the same machine to connect to without any problems, I just want Xnest to use the remote connection without switching to the dedicated TTY.

Any additional ideas what I can try?

Thank you in advance!

fbcyborg · Advocate Joined: 16 Oct 2005 Posts: 3056 Location: ROMA

Hi!
I use Xnest or X to use graphical environments for virtualized machines.
It doesn't matter if I use XEN, User Mode Linux or VirtualBox; the result is the same: crashes and crashes.
My typical situation is a vitual operating system (i.e. Linux) started and fully working in a shell, without any X server, but with kde installed.

These are the steps I do:
"h#" stands for the host system shell
"g#" stands for the guest system shell
1) h# Xnest -ac :1
2) g# export DISPLAY="host_ip:1"
3) g# startkde

Once I start, for example, Konsole or Konqueror, Xnest suddenly crashes, reporting these messages:
Before crash:

i92guboj · Posted: Thu Sep 03, 2009 11:59 am Post subject:

Xnest is a lost cause. It never worked fine.

I suggest Xephyr. You need to compile xorg with USE=kdrive to get it.

fbcyborg · Advocate Joined: 16 Oct 2005 Posts: 3056 Location: ROMA

onkelfusspilz · Posted: Thu Sep 03, 2009 12:14 pm Post subject:

Hi fbcyborg,

your first problem seems to match my experience. Since I have KDM running as login-manager on the remote-box, this could cause the same error as when you start konsole or konqueror. It still seems to me that the error really relies on the errors caused by some kind of input-device-query "(EE) config/hal: NewInputDeviceRequest failed", but I have still no solution for this yet.

The second one

onkelfusspilz · Posted: Thu Sep 03, 2009 12:17 pm Post subject:

Hi i92guboj,

that sounds like over-simplifying it a little to me. Xnest worked for ages without any flaws until this problem emerged on the recent X upgrade.

I haven't tried Xephyr yet, I'll give it a shot.

Thank you,

Andreas

fbcyborg · Advocate Joined: 16 Oct 2005 Posts: 3056 Location: ROMA

Hi!
I don't need kdm in this circumstance, because, when I start kde, I'm already logged in, through the bash terminal.
I really don't understand this kind of error "(EE) config/hal: NewInputDeviceRequest failed".

onkelfusspilz · Posted: Thu Sep 03, 2009 12:42 pm Post subject:

Hi i92guboj,

I just recompiled xorg-server with use-flag +kdrive and tried Xephyr and it worked perfectly well! Just one thing: I needed to add the parameter "-kb" which disables the x-keyboard-extension. If I don't disable it, my keyboard-layout is screewed up completely within Xephyr.

Thank you very much!

Andreas

fbcyborg · Advocate Joined: 16 Oct 2005 Posts: 3056 Location: ROMA

Hello,

Is there a way to exit from the full screen mode of Xephyr???
Sometime I do Xephyr -fullscreen but I'm not able to switch to another X session or to close it.
_________________
[HOWTO] Come criptare la /home usando cryptsetup e luks
[HOWTO] Abilitare il supporto al dom0 XEN su kernel 3.X
Help answer the unanswered