CDE Bugs

Date Prompt String Uses LC_MESSAGES When It Should Use LC_TIME (4053983)

If your system's LC_TIME environment variable is set to a locale different from the locale that is set in the LC_MESSAGES environment variable, then the date prompt displays a format that is not compatible with what the CDE Mailer expects.

Workaround: Before you start your vacation mail, make sure that your system's LC_MESSAGES and LC_TIME environment variables are set to the same locale.

Copy/Paste Functions Fail in dtterm When Using the ls -l Command in CTL Locales (4129969)

The Copy/Paste functions do not work properly if you try to copy and paste any text that includes Hebrew and Arabic characters and numbers, such as 1, 2, 3, 4, etc.

Names For Attachments Are Displayed in Reversed Order in Hebrew and Arabic Locales (4130010)

If you are using dtmail in either Hebrew or Arabic locales and you have attachments with Hebrew or Arabic names, these names are displayed in reversed order in the dtmail attachment.

The Name of the Month in the Calendar Manager Icon of the CDE Workspace Manager is Incorrectly Reversed (4136966)

If you are using dtcm in either Hebrew or Arabic locales, the name of the Month in the Calendar Manager icon on the front is incorrectly reversed.

Dtmail May Truncate the Body of an Email Message (4133964)

Dtmail may truncate the body of an email message if the message body contains non-printable characters.

The following warning message is displayed:

Message contains a binary code which is invalid as a character in the
current locale. For this reason part of this message may be truncated.
If you run CDE in the same locale that this message came from, you
will be able to view the entire message.

If an email message is created in one locale and then emailed to another locale, email may be truncated because it contains a binary code that is invalid as a character in the locale to which the email was sent.

For example, this bug may occur when:

• email composed in the ko locale and emailed to the ko_UTF.8 locale

• email composed in the zh locale and emailed to the zh.GBK locale

Workaround: Perform the following steps:

1. Exit CDE.

2. Log into CDE in the locale where the email was composed

   or

   quit dtmail and set the environment variable LANG to the correct locale; then restart dtmail.

The same data that is sent as an attachment is not truncated when viewed.

SPARC only: When Selecting dtmail in the Common Desktop Environment (CDE), It Is Not CTL-Enabled in the Arabic Locale (4140698)

If you open dtmail in the Arabic locale on your Common Desktop Environment, the Arabic date and time is neither correctly shaped nor correctly laid out. Also, if you insert Arabic characters in a new message dialog, it results in a row of Arabic characters that is displayed without being correctly shaped or laid out.

SPARC only: The Arabic Font Size Is Very Large (4140700)

If you select ar, the Arabic locale, from the login screen, the dtlogin is displayed with a very large font. The default font is also very large after signing on.

SPARC only: Appointments Are Not Displayed in the Calendar Manager In Arabic When Selecting dtcm From CDE (4140701)

You are unable to view any appointments in the Calendar Manager in Arabic when you select dtcm in the Common Desktop Environment.

Workaround: Perform the following steps:

1. Select ar, the Arabic locale, from the dtlogin screen.

2. Start dtcm to open the Appointment Editor.

3. Add a new appointment that includes Arabic text.

4. Close the Appointment Editor.

The new appointment is now displayed in the Calender Manager.

Core Dumps May Occur for Motif Programs on Systems with the Solaris 2.5.1 Operating Environment Running (4157689)

This bug only affects Motif programs that have been compiled on systems that run the Solaris 2.5.1 operating environment and also contain a custom Motif widget that subclasses the XmText widget. Such a program may cause a core dump when it is executed on a system with the Solaris 2.6 or Solaris 7 operating environment running.

Workaround: Recompile the program on a system with either the Solaris 2.4, 2.5, 2.5.1, 2.6 or Solaris 7 operating environment running.

Compiling Motif Programs on Solaris 7 (4172061)

This problem occurs when compiling a Motif program in the Solaris 7 operating environment if you link to an older shared library that has been compiled in the Solaris 2.5 or Solaris 2.6 operating environments and if the older library also uses the Motif API. In this case the Motif program uses Motif version 2.1 and the old shared library uses Motif version 1.2. A core dump occurs. This is not a binary compatibility problem for applications compiled in the Solaris 2.4, 2.5, 2.5.1, 2.6 operating environments. Those applications should run correctly in the Solaris 7 operating environment.

Workaround: When you use either one of the following two workarounds, copy the Solaris 2.6 Motif header file directory Xm located in /usr/dt/include/ to a temporary directory.

• Modify the compile line that is usually represented as:

  cc m.c -I/usr/openwin/include -I/usr/dt/include -lXm -lXt -lX11

  to be:

  cc m.c -I/usr/openwin/include -I/tmp -I/usr/dt/include /usr/lib/libXm.so.3 -lXt -lX11

• Alternatively:

  1. Copy /usr/dt/lib/libXm.so.3 to a temporary directory /tmp.

  2. Execute the command ln -s libXm.so.3 libXm.so in the directory /tmp.

  3. Use a Motif compile line similar to the following:

     cc m.c -I/usr/openwin/include -I/tmp -I/usr/dt/include -L/tmp -lXm -lXt -lX1

SPARC only: restore from sys-suspend Sometimes Does Not Restore CDE (4174133)

sys-suspend(1M) may hang and not refresh the screen on some slow systems. After a system is resumed, Screen Lock is in effect by default. This problem occurs after you enter a user password. A white screen is displayed instead of a Common Desktop Environment (CDE) screen. Although you can gain access to the system remotely, you cannot enter anything because the screen is still locked. If this problem occurs, you can recover the CDE session by remotely logging on the system as superuser and then killing the sys-suspend process.

Workaround: If this problem has occurred as a result of executing autoshutdown, use the dtpower(1M) application to disable autoshutdown. The problem does not occur if you execute sys-suspend without the Screen Lock option.

Refer to "Disabling the Screen Lock" in Using Power ManagementSolaris 7 Reference Manual Collection for a description on how to disable the Screen Lock for sys-suspend invoked by the keyboard's power key. To disable the Screen Lock for the sys-suspend command that is invoked from the CDE Workspace Menu:

1. Become superuser.

2. Create the following dtaction file /etc/dt/appconfig/types/locale/sunOW.dt. The locale is the name of the language option that is selected when you start CDE.

3. Copy the ACTION SDTsuspend { ... } definition from /usr/dt/appconfig/types/locale/sunOW.dt to /etc/dt/appconfig/types/locale/sunOW.dt.

4. Add the -x flag to sys-suspend command in the /etc/dt/appconfig/types/locale/sunOW.dt file.

5. Exit the CDE session and log in again.