Ever since upgrading to Ubuntu 8.04 I get Java debug messages when starting xmaple or when running maplets from the commandline maple. They look like this:
Locking assertion failure. Backtrace: #0 /usr/lib/libxcb-xlib.so.0 [0x7f5530c8497c] #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_unlock+0x24) [0x7f5530c84a84] #2 /usr/lib/libX11.so.6(_XReply+0x10f) [0x7f55314ddf4f] #3 /usr/local/maple12/jre.X86_64_LINUX/lib/amd64/xawt/libmawt.so [0x7f55319f6416] #4 /usr/local/maple12/jre.X86_64_LINUX/lib/amd64/xawt/libmawt.so [0x7f55319d91db] #5 /usr/local/maple12/jre.X86_64_LINUX/lib/amd64/xawt/libmawt.so [0x7f55319d94ad] #6 /usr/local/maple12/jre.X86_64_LINUX/lib/amd64/xawt/libmawt.so (Java_sun_awt_X11GraphicsEnvironment_initDisplay+0x12) [0x7f55319d9722] #7 [0x7f555092d563]
I don't remember getting these in Ubuntu 7.04. Anything theories on how to get rid of theses? They are especially annoying when running plot maplets from the commandline interface.
stderr
Does all of commandline Maple's useful printout go to stdout rather than stderr? If so then maybe you could just wrap x/maple in another script which directs stderr to /dev/null.
Eg,
acer