Hi, I in danger of making this a rant, but is XDMCP no longer something
that Fedora supports?


I have just installed F17 x64 in a VM to tinker with it and systemd and
I'd like to enable XDMCP. Or what is the favoured remote access method
these days.


I've put DisallowTCP=0 in the [security] section and Enable=1 in the
[xdmcp] section of custom.conf in /etc/gdm/ and opened port 177 UDP in
the firewall on the F17 machine.


Oddly, on my remote X server when I run "X -query machinename :1" the
desktop of the remote X server freezes when connecting to this rogue F17
install. As I would expect I can see an open UDP session on UDP 177 but
I don't see any traffic on TCP 6000 or 6001 that I would expect. The
same remote X server connects to FC6, Centos5.6 etc etc without any issue.


What gives?

Thanks for any hints and guidance.

Ken



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Mon, 25 Jun 2012 22:27:34 +0100
Ken Smith <kens@kensnet.org> wrote:

> Hi, I in danger of making this a rant, but is XDMCP no longer something
> that Fedora supports?

It's not properly been supported in Fedora for years but it does work
most releases.

See

/etc/dconf/db/gdm.d/00-upstream-settings

then go read all about the totally obfuscated dconf mess that Gnome uses.

That should be enough to get you going (I found you also had to restart
gdm)



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/26/2012 05:27 AM, Ken Smith wrote:
> I have just installed F17 x64 in a VM to tinker with it and systemd and I'd like to
> enable XDMCP. Or what is the favoured remote access method these days.

What are your requirements for remote access?

Is there something missing from using VNC or xrdp?

--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Ed Greshko wrote:

On 06/26/2012 05:27 AM, Ken Smith wrote:


I have just installed F17 x64 in a VM to tinker with it and systemd and I'd like to
enable XDMCP. Or what is the favoured remote access method these days.


What are your requirements for remote access?

Is there something missing from using VNC or xrdp?




To Alan:

I see what you mean about /etc/dconf/db/gdm.d/00-upstream-settings. Its
a comment free zone! I'll dig a little deeper. I have made XDMCP work on
recent incarnations of Fedora up to 14


To Ed:




I've tried xrdp out.

Installing xrdp installed the package but it arrived disabled in systemd
- grrr: a tad user aggressive - if the aim is to make Fedora more user
accessible then installing a service should enable and start it. It
fails to show up in the "Service Configuration" applet until I used bash
to tell systemd that its enabled. I don't see how to use the Enable and
Disable function in "Service Configuration" because a service needs to
be enabled before it shows up. Gnome 3 runs in fall-back mode in xrdp -
a good reason to use X.


Vnc does not look too bad in this instance, although in an MS
environment I find that the image quality often lacking.


I have been used to using XDMCP with *nix systems for years it seems a
pity to remove the function that could/might be kept. I could ask the
question the other way, how does removing XDMCP functionality further
Fedora's cause?


This could get into a discussion about the target audience for
Fedora/Gnome and what Fedora is trying to achieve. A topic for another
thread me thinks. I know one of Fedoras' aims is a technology test bed.
The advice is not to use it for production and here is a good example of
why.


Thanks

Ken






--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

> I have been used to using XDMCP with *nix systems for years it seems a
> pity to remove the function that could/might be kept. I could ask the
> question the other way, how does removing XDMCP functionality further
> Fedora's cause?

It's not a Fedora thing, it's a Gnome thing. Fedora ships several other
display managers all of which do xdmcp just fine. The Gnome one is
primarily a docs/config problem. It does it, but the configuration is
undocumented almost every document on Gnome about gdm is stale, obsolete
or misleading.

The setup I run inside firewall is novnc + websockets proxy + Xvnc. I did
play with x11vnc but its basically impossible to make it do what I needed
even if you fiddle with all the config options.

The end result though is that pointing a vaguely modern web browser at the
box gives you a VNC session in browser.

Alan
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/26/2012 12:35 PM, Ed Greshko wrote:
> On 06/26/2012 05:27 AM, Ken Smith wrote:
>> I have just installed F17 x64 in a VM to tinker with it and systemd and I'd like to
>> enable XDMCP. Or what is the favoured remote access method these days.
>
> What are your requirements for remote access?
>
> Is there something missing from using VNC or xrdp?
>
Or,
there are something - not missing at all - excess pixels!

regards,
poma
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/26/2012 09:54 PM, Ken Smith wrote:
> Installing xrdp installed the package but it arrived disabled in systemd - grrr: a
> tad user aggressive - if the aim is to make Fedora more user accessible then
> installing a service should enable and start it. It fails to show up in the
> "Service Configuration" applet until I used bash to tell systemd that its enabled.
> I don't see how to use the Enable and Disable function in "Service Configuration"
> because a service needs to be enabled before it shows up. Gnome 3 runs in fall-back
> mode in xrdp - a good reason to use X.

Well, IMO, server software should default to disabled. It is not unusual for users
(novices and even experienced) to install server side software they aren't going to
use...at least initially. To have them default to start seems a good choice. This
is especially true when you probably should alter any default configurations.

I personally don't find it difficult to enter "systemctl enable some.service" and
"systemctl start some.service". I am sure there will be a GUI some day.

As for GNOME in fallback mode. I don't use GNOME....but my impression is that it
needs certain functionality in the graphics that I'm not sure will work in any remote
environment.

>
> Vnc does not look too bad in this instance, although in an MS environment I find
> that the image quality often lacking.

I've only found that to be true when using the defaults.
>
> I have been used to using XDMCP with *nix systems for years it seems a pity to
> remove the function that could/might be kept. I could ask the question the other
> way, how does removing XDMCP functionality further Fedora's cause?

I've not used XDMCP in years. I think part of the reason I moved away from it is
that when I do "remote" it can be *remote* and the performance over low bandwidth or
high latency links was lacking.


--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/25/2012 02:27 PM, Ken Smith wrote:

Oddly, on my remote X server when I run "X -query machinename :1" the
desktop of the remote X server freezes when connecting to this rogue F17
install.


I noticed the same thing when I tried to use F17 as the XDMCP server for
a CentOS 6 X11 display. I didn't look into it much, then. I just ran
it again, and noticed that it's printing the following to the console.
It looks like XDMCP isn't disabled, but may be exposing a bug in
previous versions of the X11 display server. See if you're getting a
similar message on the system console.



*** glibc detected *** X: free(): corrupted unsorted chunks:
0x00000000018fe830 ***

======= Backtrace: =========
/lib64/libc.so.6[0x3c9d275296]
X(SrvXkbResizeKeyType+0x4ef)[0x50ecdf]
X[0x508db5]
X[0x509a08]
X[0x4321a1]
X[0x421ebb]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x3c9d21ecdd]
X[0x421a49]
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Mon, Jun 25, 2012 at 5:27 PM, Ken Smith <kens@kensnet.org> wrote:

Hi, I in danger of making this a rant, but is XDMCP no longer something that Fedora supports?


gives?

<snip>*


Thanks for any hints and guidance.

I have more than a hint and guidance. *I have emphatic advice. *Stop trying to import and export desktops, no matter the system. *Import and export windows or create virtual machines, but do not ever under any circumstances attempt to deal with virtual desktops, no matter the Windows or Linux distribution. *If you get it right once for some circumstance, whatever you have gotten right will soon become wrong in some intolerable way just as soon as some weenie somewhere has a better idea. *No one is more or less a sinner. *All are. *I know what a virtual machine is and I know what a window is and so do most systems. *No one seems to be able to agree on what a desktop is or what its powers are, and that problem is absolutely fundamental.

Robert Myers
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Alan Cox wrote:

{snip} how does removing XDMCP functionality further
Fedora's cause?


It's not a Fedora thing, it's a Gnome thing. Fedora ships several other
display managers all of which do xdmcp just fine.

In appreciate that its a Gnome thing

Thanks

Ken






--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org