I've got Sun Ray 4 0907 w/ the -01 patch running on Nevada build 82 (x86 & 
SPARC).  When I configure a Sun Ray multi-head group & login (to GNOME), 
gnome-panel dies.  

Sun Ray GNOME sessions run fine on single headed Sun Ray clients, i.e., not 
configured for a MH group.  

MH CDE sessions work fine.

This problem does NOT occur on build 74 (MH Group GNOME logins work perfectly), 
I first observed this when I tried to LU from b74 to b77 (on SPARC).

Xinerama is not configured.

I configured a SR MH group as follows:

    utmhadm -a studymh -g 2x1 -p IEEE802.0003baa8bb6d \
        -l IEEE802.0003baa8bb6d,IEEE802.0003baa8bd0b

When I login to GNOME, gnome-panel dies w the following errors in 
~/.dt/sessionlogs/myhost_DISPLAY=:2

GNOME Desktop Environment
using xinitrc file: /usr/dt/config/Xinitrc.jds
Cleaned 0 files 0 still live
Starting gnome-session
[ApocSource] Source apoc:readonly:mandatory@ is unavailable: Failed: [ApocPapi] 
Cannot initialise PAPI: PAPI Connection Failure.
[ApocSource] Source apoc:readonly: is unavailable: Failed: [ApocPapi] Cannot 
initialise PAPI: PAPI Connection Failure.
X_mkdir: Not owner
X_mkdir: Not owner
SESSION_MANAGER=inet6/vm-52:54728,inet/vm-52:32859
Window manager warning: Failed to read saved session file 
/home/guest/.metacity/sessions/default0.ms: Failed to open file '/home/guest/
.metacity/sessions/default0.ms': No such file or directory
Window manager warning: Log level 32: could not find XKB extension.
/usr/bin/gnome-at-visual: syntax error at line 38: `CMDLINE=$' unexpected
Initializing nautilus-open-terminal extension
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 794 error_code 8 request_code 72 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

** ERROR **: file poa.c: line 1022: assertion failed: ((poa->life_flags & 
ORBit_LifeF_DeactivateDo) == 0)
aborting...

warning: Lowest section in /lib/libpthread.so.1 is .dynamic at 00000074

warning: Lowest section in /lib/libthread.so.1 is .dynamic at 00000074
Backtrace limit of 200 exceeded
Backtrace limit of 200 exceeded
Backtrace limit of 200 exceeded

Then the gnome-panel error msg (w/ badmatch) repeats about 20 times.

Any ideas?

TIA,

Matt
 
 
This message posted from opensolaris.org

Reply via email to