This list covers some of the known problems with the Sun Java Desktop System Configuration Manager. Read the list before reporting any new bugs.
Problem ID |
Description and Workaround. |
|
---|---|---|
4982026 |
Minor accessibility issues. Some screen readers place the hidden Jump Over Tab Navigation Area link at the end of the page instead of at the beginning. |
|
5004807 |
When installing on Red Hat 7.3, the following error occurs:
The error has no negative impact, and can be ignored. |
If exceptions are displayed in your HTML pages directly after entering the Configuration Manager from the SunTM Web Console, try the following:
Clear the cache directory (/usr/share/webconsole/work/Standalone/localhost/apoc/jsp/) where tomcat stores its compiled JSPs.
Verify that the file policymgr.cfg exists (/usr/share/webconsole/apoc/WEB-INF/).
Verify that the file policymgr.cfg has correct user rights (read access for noaccess:noaccess).
Verify that the LDAP data stored in the file policymgr.cfg corresponds to your LDAP server, such as host, port, baseDN, and so on.
This patch should be applied to avail of the fix for bug 4903368. Without this fix, if a user chooses to remove five or more policy groups assigned to an entity, then the Configuration Manager will remove all the assigned policy groups from that entity. More importantly, if a user chooses to remove five or more policy groups assigned to the root entity, then not only will all assigned policy groups be removed from that entity, but the Configuration Manager LDAP metaconfiguration data will also be deleted from the Directory Server. The Directory Server cannot then be used by the Configuration Manager until the createServiceTree installation script is run again.
Users who want to use the Configuration Manager to manage the JavaTM Desktop System Release 2 for the Solaris operating platform will need to use the Configuration Manager Release 1 that was delivered with the JavaTM Desktop System Release 2 for Linux. In so doing, users should note that the following managed configuration options of the Configuration Manager are currently not applicable:
Policies – Gnome 2.2 – Advanced – Panels
Policies – Gnome 2.2 – Lockdown (except for Terminal Settings)