Home/ Questions/Q 202867
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T17:19:40+00:00

I am developing a JSF web application on a Windows box using Emacs as

  • 0

I am developing a JSF web application on a Windows box using Emacs as my editor but I far prefer to use Emacs in a Linux environment. In the (somewhat distant) past it was a no-brainer to use a remote X display to accomplish this very useful programming aid. Cygwin helps out somewhat but true remote X is the preferred solution. However, in recent Fedora (and Ubuntu) distros, remote X is a royal pain in the butt (Google remote X or XDMCP) and you will see there are now many configuration settings for GDM, XDM and KDM not to mention xhost and the firewall configurations that make remote X more difficult than convincing Barry Kelley that this type of question is TRULY programming related.

Now, I am running Fedora 10 with an XFCE environment and KDM as my display manager. I have turned the firewall off, selinux off, enabled XDMCP (in /etc/kde/kdm/kdmrc), but I still get “Can’t open display” when testing using (Cywin) “$ export DISPLAY= myfedora10box:0.0; xclock”. The test works fine when I remote display to another windows box running Cygwin/X. So the problem is clearly a configuration setting in Fedora 10.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Some of the answers I received helped, especially the one from Bryan Childs. For once I confirmed that “$ ps -ef | grep X” showed the -nolisten tcp arguments on the X command it was a no-brainer to go from there to grep for “-nolisten” under /etc (Emacs’ rgrep to be precise) where I found the culprit in /etc/kde/kdm/kdmrc:457 where “ServerArgsLocal=-br -nolisten tcp” was specified.

    Thanks to all who responded.

    -pmr

    • 0