Ximian and Solaris - dtlogin failure
- From: "John J. LeMay Jr." <jlemay njmc com>
- To: gnome-list <gnome-list gnome org>
- Subject: Ximian and Solaris - dtlogin failure
- Date: Sat, 15 Sep 2001 18:44:47 -0400
Hi folks,
This may be a bit off topic since this isn't a Ximian list, but I couldn't find
a Ximian specific list around.
I just completed installing Ximain on my Sun Ultra 5 (on Solaris 8). When I
login with my user id/password and try to start Gnome, I get kicked back out the
dtlogin screen. However, when I login as root or if I create a new user id and
login, I get my Ximian desktop and Nautilus. I found one article on Ximian's
site talking about this very problem. It recommended creating a script file to
call gnome that redirects everything to a log file. Unfortunately when I login
with my id, no log file is created. However, my startlog file in ~/.dt shows
this:
[jlemay logan njmc com] $ cat startlog.old
--- Sat Sep 15 18:26:01 EDT 2001
--- /usr/dt/bin/Xsession starting...
fbconsole: ioctl SRIOCSREDIR: Device busy
--- starting /usr/openwin/bin/speckeysd
--- Xsession started by Xsession
--- setting font path...
--- starting /usr/dt/bin/dtsession_res -load -system
--- sourcing /export/home/jlemay/.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- sourcing /usr/dt/config/Xsession.d/1000.solregis...
--- starting /usr/dt/bin/dtsearchpath
--- starting /usr/dt/bin/dtappgather &
--- starting /usr/dt/bin/dsdm &
--- session log file is /dev/null
--- DTSOURCEPROFILE is 'true' (see /export/home/jlemay/.dtprofile)
--- execing /etc/dt/config/Xsession.gnome2 with a /usr/bin/ksh login shell ...
--- starting desktop on /dev/pts/1
Sun Microsystems Inc. SunOS 5.8 Generic February 2000
/usr/dt/bin/ttsession[2926]: starting
/usr/dt/bin/Xsession[748]: 2911 Hangup
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
Could anyone lend a hand here and let me know where I should start looking for
the problem?
thanks!
John LeMay Jr.
Senior Enterprise Consultant
NJMC, LLC.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]