![]() ![]() ![]() ![]() |
Table of Contents |
You can report any problems you're having with VolanoChat by sending a complete description along with your VolanoChat server support.log
file to Volano Support <service@volano.com>. Below are some of the problems of which we are already aware.
The pop-up blockers in the following browsers block the VolanoChat applets from displaying content in a new window, such as when a banner, user profile link, or text advertisement is clicked, or when Web touring is enabled:
There is no solution for bypassing the pop-up blockers at this time.
The close button in the applet window frame fails to close the window on Linux. If possible, use the window's Room or Places menu to close the window by selecting the Close or Exit menu item.
The list of users in the chat room can often display with a width narrower than appropriate on Mac OS X. You may be able to fix the problem by resizing the chat room window in the VolanoChat and MyVolanoChat applets so that the user list width is adjusted.
If you reload the page after starting the VolanoChat applet when using the Sun Java Plug-in 1.5 in Firefox 1.5, the applet (and Java Plug-in itself) can hang. Avoid reloading the Web page after starting the applet, or close and relaunch the browser to recover.
The Microsoft Virtual Machine in Internet Explorer for Windows can hang when the VolanoChat applet chat room window is resized while a message is being received in the chat room. The problem can be solved by upgrading to the Sun Java 2 Plug-in.
Most Java applet display problems with the mouse, windows, and scroll bars on the Mac can be solved by upgrading to Mac OS X Panther v10.3 (or later) and Java version 1.4.2 (or later), supported in the Safari Web browser.
The WebVolanoChat applet does not recognize the applet property webtouring.default=true
.
A bug in the name service lookup on Linux could cause the VolanoChat server to crash with a segmentation violation, printing a message like this:
./startup.sh: line 93: 21554 Segmentation fault (core dumped)
or this:
SIGSEGV 11* segmentation violation si_signo [11]: SIGSEGV 11* segmentation violation si_errno [0]: Success si_code [0]: SI_USER [pid: 0, uid: 0] stackpointer=0x526dccc4
The problem can be corrected by installing the latest updates for the Glibc library on your Linux system. For details, see the Red Hat Errata, "Updated glibc packages fix vulnerabilities in resolver."
![]() ![]() ![]() ![]() |
XHTML 1.0 | Table of Contents |