1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] GDM Configuration
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20GDM%20Configuration&In-Reply-To=%3C20121030091510.GA30685%40bkor.dhs.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="019611.html">
<LINK REL="Next" HREF="019699.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] GDM Configuration</H1>
<B>Olav Vitters</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20GDM%20Configuration&In-Reply-To=%3C20121030091510.GA30685%40bkor.dhs.org%3E"
TITLE="[Mageia-dev] GDM Configuration">olav at vitters.nl
</A><BR>
<I>Tue Oct 30 10:15:10 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="019611.html">[Mageia-dev] GDM Configuration
</A></li>
<LI>Next message: <A HREF="019699.html">[Mageia-dev] GDM Configuration
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19646">[ date ]</a>
<a href="thread.html#19646">[ thread ]</a>
<a href="subject.html#19646">[ subject ]</a>
<a href="author.html#19646">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Mon, Oct 29, 2012 at 01:43:26PM -0400, Frank Griffin wrote:
><i> I was looking around to figure out how to enable XDMCP support in
</I>><i> GDM, and noticed something strange.
</I>><i>
</I>><i> In the GNOME site GDM3 documentation, they give several options for
</I>><i> GDM configuration none of which seem to exist in cauldron.
</I>
I'm guessing the documentation is outdated.
><i> An example is given of using gconf-edit to access apps/gdm, but no
</I>><i> such key exists. Mention is made of using a "gdm3setup" executable
</I>><i> that we don't seem to have.
</I>
GDM has been migrated to gsettings (in practice: dconf).
><i> Mention is made of "gdm" directories in various locations under
</I>><i> /usr/share and /etc which we don't seem to have, and of enabling
</I>><i> XDMCP by setting "Enable=true" in a file called daemon.conf, but the
</I>><i> only daemon.conf we have is in /etc/pulse.
</I>><i>
</I>><i> I did find /usr/share/X11/dm.d/20gdm.conf and
</I>><i> /etc/dbus-1/system.d/gdm.conf, but neither of these seem to have
</I>><i> anything to do with XDMCP.
</I>><i>
</I>><i> I did find a barebones /etc/X11/gdm/custom.conf which had an empty
</I>><i> [Xdmcp] section, but adding Enable=true here had no effect on
</I>><i> getting the GDM main dropdown to show a Remote Login option. It
</I>><i> did, however, get the GDM server to export the host as eligible for
</I>><i> XDMCP, and accept a logon. However, the GDM screen it puts up has
</I>><i> no option to close the connection, or anything else indicating that
</I>><i> it is a remote login.
</I>><i>
</I>><i> What do we do in MGA to enable GDM as an XDMCP client, or configure
</I>><i> it in general ?
</I>
No clue at all. Suggest asking upstream. XDMCP was recently discussed in
relation to fallback mode, but other than that I don't know much
(assumed it was working).
--
Regards,
Olav
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="019611.html">[Mageia-dev] GDM Configuration
</A></li>
<LI>Next message: <A HREF="019699.html">[Mageia-dev] GDM Configuration
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19646">[ date ]</a>
<a href="thread.html#19646">[ thread ]</a>
<a href="subject.html#19646">[ subject ]</a>
<a href="author.html#19646">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|