Bug 511809 - Xnest does not work
Summary: Xnest does not work
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-15 07:29 UTC by Russell Strong
Modified: 2018-04-11 08:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 13:38:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Russell Strong 2009-07-15 07:29:44 UTC
Description of problem:

[russell@studio ~]$ rpm -qf `which Xnest`
xorg-x11-server-Xnest-1.6.1.901-1.fc11.x86_64
[russell@studio ~]$ Xnest :1
SELinux: Disabled on system, not enabling in X server
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 188 requests (188 known processed) with 0 events remaining.
[russell@studio ~]$

Comment 1 Matěj Cepl 2009-11-05 18:34:45 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Comment 2 Burhan Ali 2009-12-02 17:59:50 UTC
I am also seeing this problem in F12.

Both Xnest and Xephyr suffer from the problem ie. "NewInputDeviceRequest failed" messages on startup.

For completion, here are the versions I have:

[burhan@orion ~]$ rpm -qa xorg-x11-server-Xnest xorg-x11-server-Xephyr
xorg-x11-server-Xephyr-1.7.1-7.fc12.x86_64
xorg-x11-server-Xnest-1.7.1-7.fc12.x86_64

Comment 3 Nathan Crubel 2010-01-18 17:14:57 UTC
I am seeing the same problem in Fedora 12 with the latest updates.  I am also not able to connect to a remote PC using xdmcp on Fedora 12. 

[ncrubel~]$ Xnest :3
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)

Screen shows up, but only stays black.  

[ncrubel@uslt21592 ~]$ Xephyr -br -once -screen 1280x800 -query 10.201.22.48 :1
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)

Comment 4 Matěj Cepl 2010-02-26 12:14:07 UTC
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]

Comment 5 Burhan Ali 2010-02-26 16:22:03 UTC
(In reply to comment #4)
> Could you please reply to the previous question? If you won't reply in one
> month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

Which question?

Comment 6 Matěj Cepl 2010-03-02 22:32:04 UTC
(In reply to comment #1)
> Please, if you experience this problem on the up-to-date system, let us now in
> the comment for this bug, or whether the upgraded system works for you.

Comment 7 Burhan Ali 2010-03-03 09:58:58 UTC
(In reply to comment #6)
> (In reply to comment #1)
> > Please, if you experience this problem on the up-to-date system, let us now in
> > the comment for this bug, or whether the upgraded system works for you.    

Since this question was asked on 2009-11-05, two people have reported that it still exists on up to date systems, so I'm unsure why you think the question in unanswered.

For completion, I still see the symptoms mentioned above. I have the most recent version I could pull in from updates-testing.

[burhan@orion ~]$ rpm -qa xorg-x11-server-Xnest xorg-x11-server-Xephyr
xorg-x11-server-Xnest-1.7.5-1.fc12.x86_64
xorg-x11-server-Xephyr-1.7.5-1.fc12.x86_64


What other information would you like, to help diagnose the problem?

Comment 8 Nathan Crubel 2010-03-03 18:34:24 UTC
I am still having the same problems.  

Thanks

Comment 9 Nathan Crubel 2010-03-23 17:58:02 UTC
xorg-x11-server-Xnest-1.7.6-1.fc12.x86_64
xorg-x11-server-Xephyr-1.7.6-1.fc12.x86_64

Tested with the latest, still getting these errors[nathan@nc7520laptop ~]$ Xnest :3 -name test
SELinux: Disabled on system, not enabling in X server
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 200 requests (200 known processed) with 0 events remaining.

Xephyr :3  -br -once -screen 1280x800 -query localhost
SELinux: Disabled on system, not enabling in X server
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 53 requests (53 known processed) with 0 events remaining.

Comment 10 Bug Zapper 2010-04-27 15:41:23 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 11 Bug Zapper 2010-06-28 13:38:23 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.