Jean-Paul: > Note: I'm now working and referring to Open Solaris Indiana and no longer to > SXCE/Nevada. > > I've modified the svc manifest so the dependency is removed and the service > starts correctly:
How did you modify the dependency? Did you remove the 'hal' dependency? If so, that should be okay. GDM does not really depend on HAL. This dependency was added because if GDM allows users to log in before HAL starts up, this can cause problems for the user session. You might be running into bug #6787060 bugs.opensolaris.org/view_bug.do?bug_id=6787060 The issue should probably be fixed a different way than making GDM depend on the HAL service, but not sure how to fix this in a better way. > svcs | grep gdm > online 20:24:27 svc:/application/graphical-login/gdm:default > > and > > ps -elf | grep gdm > 0 S root 21683 21388 0 40 20 ? 1433 ? 20:24:28 ? > 0:00 /usr/sbin/gdm-binary > > I've tried two methods of connecting to the desktop. > > The first is through XDMCP. I have modified /etc/X11/gdm/custom.conf to > enable XDMCP and allow TCP connections. Note that you also may be running into bug #6633238 bugs.opensolaris.org/view_bug.do?bug_id=6633238 > When running XDMCP from another OpenSolaris machine, the zone desktop is > detected correctly and listed accordingly in the chooser. However when > selecting and connecting, I'm presented with a black screen with an 'X' in > the middle and that it. I can move the mouse around but no gnome login screen. If the above doesn't help... Try setting Enable=true in the [debug] section of the GDM configuration file, and restart GDM by running gdm-restart. Then debug messages should be echoed to the syslog (/var/adm/messages). Share the gdm related messages, and that might help debugging. > The other method is through secure global desktop (SGD) configured to execute > gnome-session. The same stack trace is returned: > > Jul 8 20:32:52 sun gnome-session[21843]: [ID 124589 daemon.crit] > ******************* START ******************************** > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 0: > /usr/bin/gnome-session'gdm_signal_handler_backtrace+0x90 [0x806cf98] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 1: > /usr/bin/gnome-session'signal_handler+0x75 [0x806d139] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 2: > /lib/libc.so.1'__sighndlr+0xf [0xfeeed1bf] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 3: > /lib/libc.so.1'call_user_handler+0x2af [0xfeee024f] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 4: > /lib/libc.so.1'_lwp_kill+0x7 [0xfeef1aa7] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 5: > /lib/libc.so.1'raise+0x22 [0xfee9ac1a] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 6: > /lib/libc.so.1'abort+0x74 [0xfee7202c] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 7: > /usr/lib/libdbus-1.so.3.4.0'_dbus_abort+0x67 [0xfae626e3] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 8: > /usr/lib/libdbus-1.so.3.4.0'_dbus_warn_check_failed+0x6b [0xfae5e65f] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 9: > /usr/lib/libdbus-1.so.3.4.0'_dbus_get_local_machine_uuid_encoded+0xb0 > [0xfae5ed5c] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 10: > /usr/lib/libdbus-1.so.3.4.0'_dbus_get_autolaunch_address+0x5c [0xfae65f24] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 11: > /usr/lib/libdbus-1.so.3.4.0'_dbus_transport_open_autolaunch+0x62 [0xfae5acfe] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 12: > /usr/lib/libdbus-1.so.3.4.0'_dbus_transport_open+0xd6 [0xfae5ae8a] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 13: > /usr/lib/libdbus-1.so.3.4.0'connection_try_from_address_entry+0x23 > [0xfae4458f] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 14: > /usr/lib/libdbus-1.so.3.4.0'_dbus_connection_open_internal+0x280 [0xfae44860] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 15: > /usr/lib/libdbus-1.so.3.4.0'dbus_connection_open+0x2d [0xfae452b5] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 16: > /usr/lib/libdbus-1.so.3.4.0'internal_bus_get+0xe0 [0xfae422e0] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 17: > /usr/lib/libdbus-1.so.3.4.0'dbus_bus_get+0x13 [0xfae4249b] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 18: > /usr/lib/libdbus-glib-1.so.2.1.0'dbus_g_bus_get+0x74 [0xfae8aa6c] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 19: > /usr/bin/gnome-session'gsm_util_setenv+0x4b [0x8077567] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 20: > /usr/bin/gnome-session'main+0x249 [0x806eae1] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 883141 daemon.crit] Frame 21: > /usr/bin/gnome-session'_start+0x7d [0x80603ad] > Jul 8 20:32:52 sun gnome-session[21843]: [ID 166210 daemon.crit] > ******************* END ********************************** You need to run gnome-session with D-Bus, which you can do like this: dbus-launch --exit-with-session gnome-session > a) Can someone confirm what I'm trying to do is actually possible/correct? > b) Assuming the above is true, I presume I'm seeing two different errors > rather than the same error differently? > c) Pointers to help greatly appreciated Hope this helps. Brian
