Bug 1151472

Summary: XDMCP trouble
Product: [Fedora] Fedora Reporter: Louter <serg>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 20CC: normand, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 22:51:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
gdm config by HOST none

Description Louter 2014-10-10 14:04:37 UTC
Created attachment 945620 [details]
gdm config by HOST

Description of problem:

X -query HOST
not work from remote machine
X -ac -query HOST
work, but slow. HOST generate 2-MiB/s traffic (wifi full speed) and reaction very slow. Not display cursor.

Xephyr -query HOST
not work
Xephyr -ac -screen WIDTHxHEIGHT -query HOST
work as `X -ac -query HOST` but screen resolution not applyed. Start with HOST resoulution settings.

Xephyr -ac -fillscreen -query HOST
eq `X -ac -query HOST`

Try xdm...
XDM response quick, Login and Password entries momental. Then start GDM, and work as `X -ac -query HOST` (slow, big traffic when mouse move, pictire change, no cursor)

Version-Release number of selected component (if applicable):
GDM 3.10.0.1
X11 1.12 and X11 1.14

How reproducible:
see above

Steps to Reproduce:
1. configure gdm by HOST
2. restart HOST machine, and we see that the UDP port 177 is open.
3. try connect from remote machine

Actual results:
Don't work or generate traffic

Expected results:
--

Additional info:
I try from HOST to HOST by Xephyr:
Xephyr :1 
Xephyr :1 -ac
Xephyr :1 -ac -query localhost
All black screen. Then start xdm
Xephyr :1 -query localhost
Logon and Ooops!

Comment 1 Fedora End Of Life 2015-05-29 13:03:47 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 2 Fedora End Of Life 2015-06-29 22:51:25 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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