[GnomeMeeting-devel-list] Problems with openmcu and gnomemeeting-1.0

[David Ronis <ronis ronispc chem mcgill ca>]

I'm not sure this is really a gnomemeeting issue, but thought I'd post
it here, just to be sure.

I'm running on several ix86-linux(2.6.3)-slackware(9.1) boxes and
after some help from #gnomemeeting folks have successfully installed.

[as long as I'm at it, there were some important install issues that
had to be overcome, and might be worth mentioning in the FAQ:

1.  Broken accessibility modules leading to memory corruption and a
hang.  

2.  I built and installed with --prefix=/usr/local (i.e., the
default).  It turns out that gnomemeeting.server is, no surprise,
installed in the /usr/local subtree; however, by default, slackware's
gnome doesn't look for it there.  Not finding the file breaks the -c
command-line option (a new gnomemeeting is started even if there is
already one running).  Running

		 /usr/sbin/bonobo-activation-sysconf
	    --add-directory=/usr/local/lib/bonobo/servers

fixes the problem.
]

OK, now back to the openmcu problem.  I built version 1.1.7.  It runs,
albeit with occasional crashes, and sort of works.  However, when
anybody types in the text-message window, I or the other people
connected don't see anything.  My understanding is that we should all
see the mcu repeating the message.  I've built a debugging version of
openmcu and ran with -t -t -t.  The log shows nothing related to any
of the text being typed. 

Another openmcu/gnomemeeting problem is related to making gnomemeeting
an icon; popping down gnomemeeting causes openmcu to crash.

Lastly, a feature-request.  I'd like to be able to choose a custom
font for gnomemeeting, without changing that for the entire desktop.
If this is not yet possible, and if not, it shouldn't be too hard to
add.

In any event, problems aside, this is great software.


David