Re: [gdm-list] gdm-list Digest, Vol 101, Issue 1

["John D. Hendrickson and Sara Darnell" <johnandsara2 cox net>]

> This command no longer works with Fedora 19.  The command returns
> immediately and there is no VNC listener on port 5921.

yes and surely.  you answered your own question: it is not there.

$ netstat -a  # list port listeners

check your firewall too

that assumes Xvnc is not somehow configured incorrectly !  X is 
already network enabled.  is Xvnc a copy-left of Xnest ?

this part i'm pasting in because your querying localhost and that is 
applicable:

in
      http://sourceforge.net/projects/xdm-options/

it was shown that for X11R6 or X.org

-nolisten tcp

applies to your LOCAL tcp but not remote tcp: that's left open.


(redhat i know made the option to Xserver default on pkg(1) installs)



issuegdm-list-request gnome org wrote:
> Send gdm-list mailing list submissions to
>         gdm-list gnome org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://mail.gnome.org/mailman/listinfo/gdm-list
> or, via email, send a message with subject or body 'help' to
>         gdm-list-request gnome org
>
> You can reach the person managing the list at
>         gdm-list-owner gnome org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gdm-list digest..."
>
>
> Today's Topics:
>
>    1.  gdm and tigervnc problem on Fedora 19 (Bob B.)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 02 Dec 2013 13:17:23 -0500
> From: "Bob B." <bb1 halebob net>
> To: gdm-list gnome org
> Subject: [gdm-list] gdm and tigervnc problem on Fedora 19
> Message-ID: <529CCEB3 4010706 halebob net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hello,
>
> I used to be able to start a remote gdm login session through VNC by 
> issuing the following command:
>
> Xvnc :21 -query localhost -once -geometry 1280x1024 -depth 24 
> -DisconnectClients=0 -NeverShared -SecurityTypes=none
>
> This command no longer works with Fedora 19.  The command returns 
> immediately and there is no VNC listener on port 5921.  Any ideas why?  
> I have xdmcp enabled.
>
> Here is what shows up in /var/log/messages after running the above command:
> ...
> Dec  2 13:09:31 sherpa dbus-daemon[526]: dbus[526]: [system] Rejected 
> send message, 1 matched rules; type="method_call", sender=":1.14" (uid=0 
> pid=795 comm="/usr/sbin/gdm ") 
> interface="org.freedesktop.DBus.Properties" member="GetAll" error 
> name="(unset)" requested_reply="0" destination=":1.498" (uid=0 pid=29220 
> comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
> Dec  2 13:09:31 sherpa dbus[526]: [system] Rejected send message, 1 
> matched rules; type="method_call", sender=":1.14" (uid=0 pid=795 
> comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties" 
> member="GetAll" error name="(unset)" requested_reply="0" 
> destination=":1.498" (uid=0 pid=29220 
> comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
> Dec  2 13:09:32 sherpa gdm[795]: non-network local connections being 
> added to access control list
> Dec  2 13:09:32 sherpa systemd-logind[515]: New session c4 of user 
> gnome-initial-setup.
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[828]: gnome-session[828]: 
> DEBUG(+): GsmSystemd: received logind signal: SessionNew
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[828]: gnome-session[828]: 
> DEBUG(+): GsmSystemd: ignoring SessionNew signal
> Dec  2 13:09:32 sherpa gnome-session[828]: DEBUG(+): GsmSystemd: 
> received logind signal: SessionNew
> Dec  2 13:09:32 sherpa gnome-session[828]: DEBUG(+): GsmSystemd: 
> ignoring SessionNew signal
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: No protocol specified
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: ** 
> (gnome-session-check-accelerated:29244): WARNING **: Could not open X 
> display
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: No protocol specified
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: 
> (gnome-session-check-accelerated:29244): Gtk-WARNING **: cannot open 
> display: 127.0.0.1:21
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: No protocol specified
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: ** 
> (gnome-session-check-accelerated:29257): WARNING **: Could not open X 
> display
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: No protocol specified
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: 
> (gnome-session-check-accelerated:29257): Gtk-WARNING **: cannot open 
> display: 127.0.0.1:21
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: ** (process:29237): 
> WARNING **: software acceleration check failed: Child process exited 
> with code 1
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: No protocol specified
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: ** 
> (gnome-session:29237): WARNING **: Could not open X display
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: No protocol specified
> Dec  2 13:09:32 sherpa /usr/bin/dbus-launch[29237]: ** 
> (gnome-session:29237): WARNING **: Cannot open display:
> Dec  2 13:09:32 sherpa gdm[795]: Child process -29237 was already dead.
> Dec  2 13:09:32 sherpa gdm[795]: GLib-GObject: g_object_ref: assertion 
> `object->ref_count > 0' failed
> Dec  2 13:09:32 sherpa gdm[795]: GLib-GObject: g_object_unref: assertion 
> `object->ref_count > 0' failed
> Dec  2 13:09:32 sherpa gdm[795]: GdmDisplay: display lasted 0.777427 seconds
>
> Thanks for help anyone can provide.
>
> Regards,
> Bob
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> gdm-list mailing list
> gdm-list gnome org
> https://mail.gnome.org/mailman/listinfo/gdm-list
>
>
> ------------------------------
>
> End of gdm-list Digest, Vol 101, Issue 1
> ****************************************