Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I want to thank everyone for helping me out with this problem. The final fix was the following. Run gdmsetup which pops open a gui with several tabbed displays. Clicking on the Security tab, has a checkbox option of not allowing tcp connections which was checked. I 'unchecked it', logged out (i.e. <ctl><alt><backsp>) and relogged in under gdm. The X server would then allow direct tcp connections. It looks like gnome is shipped so that direct connections are disallowed by default. kde, I suspect ships with direct tcp connections allowed by default. Cheers. Steve. Go SOX! On Tue, 2004-10-26 at 15:52, Matt Brodeur wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, Oct 26, 2004 at 02:37:24PM -0400, Stephen Adler wrote: > > > yup.. that was it! I'm running gnome out of the box from a Fedora Core 1 > > install. My next bit of home work is to figure out where the -nolisten > > gets set... > > I think you're looking for "DisallowTCP" in /etc/X11/gdm.conf. > That is, assuming you're running gdm. In general all of your X > configuration will be somewhere in /etc/X11. > > - -- > Matt Brodeur RHCE > MBrodeur at NextTime.com http://www.NextTime.com > > A fool must now and then be right by chance. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.5 (GNU/Linux) > > iD4DBQFBfqr7c8/WFSz+GKMRAs4DAKCBd2bH5KV/fI5AZrGJ+xqRp8cLxACVGqY7 > 3KykBvNVIrajYI9soCQ0qQ== > =OF+x > -----END PGP SIGNATURE----- > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://olduvai.blu.org/mailman/listinfo/discuss >
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |