Java Desktop System Release 2 Troubleshooting Guide

Getting Started

Version Mismatch During Compilation of Kernel Modules

Problem  

Users of Pentium 4 and other hyper-threading capable processors might experience version mismatch errors when compiling kernel modules. 

Solution  

Perform the following steps:

  1. Edit the following file: /usr/src/linux-2.4.19.SuSE/linux/version.h

  2. Replace the following line: #define UTS_RELEASE "2.4.19-4GB"

    With the following line: #define UTS_RELEASE "2.4.19-64GB-SMP"

Mounts From /net Do Not Work

Problem  

Bug ID: 4908595 

Mounts from /net do not work. This problem occurs because the autofs4 utility loads the wrong kernel module by default

Solution  

Perform the following actions when you install the system: 

  1. Open the following file with a text editor: /etc/modules.conf

  2. Uncomment the following line:

    # alias autofs autofs4

Installation Fails

Problem  

Some Red Hat Package Managers (RPMs) might not recognize the underlying Linux release on your machine. If you attempt to install these RPM files on your system, the installation might fail.

Solution  

RPMs require a specific Linux version in the /etc/SuSE-release file for the installation to succeed on your system.

Change to a version of Linux that the RPM recognizes, for example SuSE Linux 8.1 (i386) Version=8.1

Screen Display Problems

Problem  

The screen resolution set by the installation process might be inappropriate for your system. This mismatch might cause screen display problems. Depending on your system hardware you can reconfigure your screen resolution during system setup. 

Solution  

After the initial Welcome screen is presented, the Installation screen is displayed. Perform the following actions: 

  1. Press F2 immediately to verify that the resolution you want is selected.

  2. Choose the desired resolution, then press Enter. If you choose a resolution that is above the capabilities of your display hardware the lower part of the screen is not visible during the installation. In that case, restart the installation and select a lower resolution.

  3. Use the arrow keys to select Installation, then press Enter.

Only resolution values that are enabled in YaST are available in the screen resolution dialog.

System Does Not Eject RPM CD

Problem  

If you install RPMs from a CD in multi-user mode, the system cannot eject the CD automatically.  

Solution  

Enter the eject cdrom command to eject the CD.

Backspace Erroneously Inserted

Problem  

If you log in to a Java Desktop System session from a Sun Ray™ client or Solaris machine, each time you press the L key on your keyboard, a backspace is inserted.

Solution  

Use either of the following solutions: 

  • After you log in to the Java Desktop System, use the xmodmap command to redefine the L key.

  • Log in to the Java Desktop System as root and remove the /etc/X11/Xmodmap file.

Panel Crashes on Log In

Problem  

When you log in to the Java Desktop System after rebooting the system, panels might crash.

Solution  

Wait for the Panel application to restart.

Users Preferences Not Fully Compatible

Problem  

Preferences set up in your home account for the GNOME 2.0 Desktop might not be fully compatible with the GNOME 2.2 Desktop on the Java Desktop System.

Solution  

Reset your preferences. 

Boot Splash Screen Not Visible After Updating the Installation

Problem  

Bug ID: 5026577 

After you have performed an installation to update an earlier version of the Java Desktop System, the boot splash screen does not appear. This problem is caused by a missing link in the /usr/share/splash/themes directory.

Solution  

Perform the following steps: 

  1. Log in as root user.

  2. Execute the following command: cd /usr/share/splash/theme

  3. Execute the following command: execute ln -s Sun current

  4. Execute the following command: execute mkinitrd

File System RPM Install Fails After Updating the Installation

Problem  

Bug ID: 5028130 

After you have performed an installation to update an earlier version of the Java Desktop System, the file system RPM fails to install.

This problem occurs when you perform a YaST2 system update from CDs, with the default automount enabled in the Nautilus file manager. The problem also occurs when you perform a YaST2 system NFS update when a CD is mounted at /media/cdrom.

This problem does not occur when you perform a network update, after booting from a CD. 

Solution  

Perform the following steps before you start a YaST2 system update installation:

  1. Remove all CDROMs from system.

  2. Select LaunchPreferencesAdvancedCD Device Options.

  3. Deselect the Mount CD when Inserted option, then select Close.

  4. Continue as normal with the system installation update.

Boxes Attached To Windows After Updating the Installation

Problem  

Bug ID: 5017762 

After you have performed an installation to update an earlier version of the Java Desktop System the Input Method Switcher applet is not added to the default panel. A symptom of this problem is that boxes are attached to windows.

The default panel configuration on Java Desktop System Release 2 is different from earlier releases of the Java Desktop System. You might experience this problem if you log into an earlier version of the Java Desktop System.

Solution  

Right-click on a panel, then choose Add to PanelUtilityInput Method Switcher.