Well we can see that GDM is quickly terminating the user session.
Perhaps there's a way to get more info by enabling debugging in GDM.
Brian - can you let us know how to do that please? Do you have any other
ideas as to why a Gnome session would immediately terminate, or
suggestions on where to look for clues?
-Bob
Alan Coopersmith wrote:
Bob wrote:
The X packages for build 134 are available for testing if you want to
try them before the whole OS is ready on the official pkg servers:
http://mail.opensolaris.org/pipermail/xwin-discuss/2010-February/004310.html
I tried Build 134 but still the same . The Bug No. 6926250 is not fixed.
Are you saying that you installed those packages and rebooted into the new boot
environment and still had no /usr/lib/xorg/sparcv9/libdrm.so.2 file? Or was
there another problem?
I am now working with Build 134 on sparc64 and on x86 both Server have the same
configuration
On the x86 Server SRSS 4.2 is OK on the sparc64 the sunray is hanging at 26 D.
Both are showing the same Log files except the sparc is showing:
Feb 23 19:43:59 sparc gdm-binary[768]: [ID 702911 daemon.warning] WARNING:
GdmDisplay: display lasted 0.128917 seconds
The log in /var/log/gdm/ are the same x86 and sparc64
the only difference between sparc and x86 is in
/usr/lib/xorg/modules/extensions/
all Files :
libdbe.so libdri2.so libglx.so
libdri.so libextmod.so libia.so
are on x86 in 32-bit and on sparc in 64-bit. I don't know if this is causing
the problem ?
That should not cause any problems - since there are no 32-bit sparcs any more,
there's no reason to ship 32-bit binaries for them, but there are still lots
of 32-bit machines.
It sounds like you have a different bug than 6926250. (BTW, those are just the
X updates for build 134 - when build 134 hits the pkg.opensolaris.org servers it
will also include the updates for the other 95% of the OS packages.)
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
