I'm seeing this same problem. I'm trying to use Xephyr to connect to a
host using XDMCP, using this command:
Xephyr :1 -query
It works with Xnest (except for the fact that it looks terrible). If I
run the same command except with "-verbosity 1000" I also see this extra
output:
(II) config/hal:
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/34194498/lspci.txt
--
Xephyr - unrecognised device identifier!
https://bugs.launchpad.net/bugs/453989
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/34194503/dmesg.txt
** Changed in: xorg (Ubuntu)
Status: Incomplete => Confirmed
--
Xephyr - unrecognised device identifier!
https://bugs.launchpad.net/bugs/453989
You received this bug notification because you are a member
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
Xephyr - unrecognised device identifier!
https://bugs.launchpad.net/bugs/453989
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
The issue is occurring in Karmic and has been reported to start sometime
during Januty.
I tried following the suggestions in this thread
http://www.gossamer-threads.com/lists/maemo/developers/50784?do=post_view_threaded#50784
Adding the lines to:
/etc/dbus-1/system.d/xorg-server.conf (inside of t
** Package changed: ubuntu => xorg (Ubuntu)
--
Xephyr - unrecognised device identifier!
https://bugs.launchpad.net/bugs/453989
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
Hi maestro-bwh,
Please attach the output of `lspci -vvnn` and `dmesg`, and attach your
/var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this
issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.
[This is an automated message. Apologies if it
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirm
** Tags added: intrepid
--
Xephyr - unrecognised device identifier!
https://bugs.launchpad.net/bugs/453989
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
[This is an automatic notification.]
Hi Brian,
This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal
still exists
$ Xephyr :1 -ac -query myhostname
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing
from list!
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed
on karmic
** Attachment added: "dmesg"
http://launchpadlibrarian.net/37494000/dmesg
--
Xephyr - unrecognised device identifier!
https://bugs.launchpad.net/bugs/453989
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
updated today
** Attachment added: "lspci"
http://launchpadlibrarian.net/37494027/lspci
--
Xephyr - unrecognised device identifier!
https://bugs.launchpad.net/bugs/453989
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
Sometime in the last two weeks my Xnext (and now that I have tested it,
Xephyr too) have also started failing with:
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
I am not running amule, I have edited /etc/dbus-1/system.d/xorg-
server.conf to add the 'allow' lin
Ups sorry guys I forgot about this...
After some checks I saw that Xephyr goes "offline" after a while(tryin to
understand if it's the blackscreen opt or else)...but I'm still tryin to figure
out why... v.v*
meanwhile i'm switchin' to ssh even for remote desktop(should work finer)
--
Xephyr -
I've this issue too...I've usually used it normally...the other day I
reinstalled the system from scratch...
In the first place I thought this was an Amule issuebut I see You
have the same issue too.
It happens usually to me not the first time I issue the command "Xephyr :1
-screen 1024x768
uh...damn...looks like that amule daemon makes the differences!
If it's running...bang! Xephyr won't load...black screen and
nothing...suggestions?
--
Xephyr - unrecognised device identifier!
https://bugs.launchpad.net/bugs/453989
You received this bug notification because you are a member of Ub
I have this issue too. My command was:
$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb &
[1] 1978
$ unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device id
And dmesg output.
** Attachment added: "dmesg.out"
http://launchpadlibrarian.net/35895755/dmesg.out
--
Xephyr - unrecognised device identifier!
https://bugs.launchpad.net/bugs/453989
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
And the lspci output.
** Attachment added: "lspci.out"
http://launchpadlibrarian.net/35895767/lspci.out
--
Xephyr - unrecognised device identifier!
https://bugs.launchpad.net/bugs/453989
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
20 matches
Mail list logo