Bug 154502 - x11/xdm authorization failure when used with E17 window manager
Summary: x11/xdm authorization failure when used with E17 window manager
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-x11 (Nobody)
URL:
Keywords:
Depends on: 211624
Blocks:
  Show dependency tree / graph
 
Reported: 2011-02-04 08:20 UTC by cc
Modified: 2016-08-30 17:58 UTC (History)
4 users (show)

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description cc 2011-02-04 08:20:11 UTC 
Xdm authorization fails after user login.
The user is unable to start an E17 window manager session, and is returned to the xdm login screen.

Fix: 

Please view /usr/local/lib/X11/xdm/xdm-config.  The default authorization settings were:
DisplayManager*authorize: true

Need to add the missing option:
DisplayManager*authName: MIT-MAGIC-COOKIE-1

otherwise xdm authorization will fail.

Thanks.
How-To-Repeat: Install i386 8.1-RELEASE.
Install enlightenment e17.
Use the method detailed in the Handbook about starting a window manager (Xfce) using xdm.
Comment 1 Remko Lodder freebsd_committer freebsd_triage 2011-02-04 19:13:12 UTC 
Responsible Changed
From-To: freebsd-i386->freebsd-doc

This might involve updating the documentation
Comment 2 Niclas Zeising 2011-10-12 13:47:24 UTC 
This rather seems like it is a documentation issue in xdm, which is not 
part of the base system. This pr should most likely be reclassified or 
just closed, if it is not an issue any longer.
Regards!
-- 
Niclas Zeising
Comment 3 Anton Shterenlikht 2011-10-12 14:02:27 UTC 
I've had similar behaviour when some ports were missing,
perhaps x11/xrdb. The OP needs to examine
/var/log/xdm.log first. This might be no error at all.

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
Comment 4 Glen Barber freebsd_committer freebsd_triage 2011-10-12 14:03:29 UTC 
Responsible Changed
From-To: freebsd-doc->freebsd-ports-bugs

Ports PR (if it's still a problem).
Comment 5 Mark Linimon freebsd_committer freebsd_triage 2011-11-20 23:33:31 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->freebsd-x11

Fix synopsis and assign.
Comment 6 Jilles Tjoelker freebsd_committer freebsd_triage 2013-06-12 21:46:57 UTC 
In FreeBSD PR 154502, you wrote:
> Xdm authorization fails after user login.
> The user is unable to start an E17 window manager session, and is
> returned to the xdm login screen.

> Fix: Need to add the missing option:
> DisplayManager*authName: MIT-MAGIC-COOKIE-1

I take it that the error message
  XDM authorization key matches an existing client!
appears in .xsession-errors.

I recently encountered this issue when trying to log in using xdm and
xfce4-session. Adding the quoted line to xdm-config fixed the problem
for me.

The cause is that the implementation of XDM-AUTHORIZATION-1 is broken if
applications execve or unload/reload libX11/libxcb between connections
to the X server. More information can be found in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486606

Since it is unclear whether XDM-AUTHORIZATION-1 will be fixed and if so,
where, I think it is best to disable it in xdm. It looks like adding
--disable-xdm-auth to xdm's configure flags will do this but I have not
tested it. I think the security impact is minimal; gdm does not use
XDM-AUTHORIZATION-1 either.

-- 
Jilles Tjoelker
Comment 7 Carlo Strub freebsd_committer freebsd_triage 2014-09-14 10:32:14 UTC 
Is this PR still relevant?
Comment 8 Jilles Tjoelker freebsd_committer freebsd_triage 2014-10-27 22:20:31 UTC 
The problem in xdm was discussed today on the freebsd-stable mailing list: https://lists.freebsd.org/pipermail/freebsd-stable/2014-October/080775.html

I would still like to see xdm compiled without XDM-AUTHORIZATION-1.
Comment 9 Johannes Lundberg 2014-12-04 02:07:45 UTC 
I have the same problem when I try to run pwcview. It fails to init SDL.

FreeBSD 11 current in VMWare
xdm
lxde
Comment 10 Kurt Jaeger freebsd_committer freebsd_triage 2016-08-30 17:58:41 UTC 
See PR#211624 for the fix.