Bug 9998 - Can't connect on Xdmcp server with Xephyr
Summary: Can't connect on Xdmcp server with Xephyr
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-06 10:36 CEST by Philippe Grangeray
Modified: 2013-05-08 19:30 CEST (History)
0 users

See Also:
Source RPM: x11-server-xephyr-1.13.4-2.mga3
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Philippe Grangeray 2013-05-06 10:36:48 CEST 
Description of problem:

An attemp to connect with Xephyr open a window with the background shown but not with the login greeter:

Xephyr :1 -query localhost -once

The same command with X works well; :

X :1 -query localhost -once


Version-Release number of selected component (if applicable):

x11-server-xephyr-1.13.4-2.mga3

How reproducible:

Always.

Steps to Reproduce:
1.Xephyr :1 -query localhost -once
2.the following log is generated in /var/log/kdm.log

Comment, length 12:
Mageia Theme
/usr/share/mga/backgrounds/default.jpg is a 1920x1440 JPEG image, color space YCbCr, 3 comps., Huffman coding
  Zooming image by 33%...done
  Clipping image...(Adding border)...done
  Building XImage...done
X Error of failed request:  BadAccess (attempt to access private resource denied)
  Major opcode of failed request:  130 (MIT-SHM)
  Minor opcode of failed request:  1 (X_ShmAttach)
  Serial number of failed request:  431
  Current serial number in output stream:  432



Reproducible: 

Steps to Reproduce:
Philippe Grangeray 2013-05-06 10:39:50 CEST

Summary: Can't connect on Xmdp server with Xephyr => Can't connect on Xdmcp server with Xephyr

Philippe Grangeray 2013-05-06 10:44:15 CEST

Version: 3 => Cauldron

Comment 1 Philippe Grangeray 2013-05-06 15:00:51 CEST 
it works when login as root
Comment 2 Philippe Grangeray 2013-05-08 19:30:51 CEST 
it's not a bug, just defect of config.
Xdmcp needs DNS lookup to respond.
So, if your LAN don't have DNS server, like mine, you have to define client IPs in /etc/hosts.

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.