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"

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

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

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.

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.

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.

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.

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

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.

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.

Problem  

If you try to open a document from a directory that is mounted with NFS the File Manager displays an error if the application owning the document cannot process a filename argument passed as a URL

For example, StarOffice™, OpenOffice, vi, acroread, and ggv applications cannot process URLs, therefore the File Manager encounters errors when opening NFS files with these applications.

The same problem arises for files in directories that are mounted with Samba (SMB). 

Solution  

Copy the files to a local directory, in other words, not a Samba or NFS directory. 

Problem  

Bug ID: 5029196 

The Nautilus file manager might crash if a directory structure is longer than 290 plain Latin characters.

Solution  

Do not create directory structures longer than 290 plain Latin characters, if you want to access the directory structures using the Nautilus file manager. There is no limitation to the character length of a directory structure when you browse the file system using the Terminal application.

Problem  

The Blueprint Beta theme is for evaluation only. Do not use the Blueprint Beta theme under normal circumstances. This theme has known bugs and is not supported. 

Solution  

If you want to evaluate the Blueprint Beta theme, choose View Apply ThemeBlueprint Beta.

Problem  

Bug ID: 4984611 

Blank pages print out when CUPS is used through Ghostscript.

Solution  

Because CUPS accounting information is usually not necessary, you can disable the accounting functionality in the cupsomatic filter. Perform the following steps:

1. Log in as root user.

2. Open the following file: /usr/lib/cups/filter/cupsomatic

3. Change the following line:

   my $ps_accounting = 1;

   To:

   my $ps_accounting = 0;

If you use/etc/foomatic/filter.conf, disable ps_accounting in that location.

Problem  

Bug ID: 4948512 

You cannot eject a floppy disk from the floppy disk drive by using the floppy disk icon on the desktop. An error message says that only the root user can eject the floppy disk. This problem occurs if the floppy disk icon is mounted on the desktop by one user, and then a second user logs in and tries to use the icon to eject a floppy disk. 

Solution  

Change user to users in the /etc/fstab file for fd0.

Problem  

Bug ID: 4966284 

You cannot eject a CDROM from the CDROM drive. This problem occurs because the fam daemon holds onto the CDROM device so that the file manager cannot unmount the device and eject the CDROM.

Solution  

Perform the following steps to eject a CDROM from the CDROM drive: 

1. Log in as root.

2. Open a terminal window.

3. Execute the following command: pkill fam

4. Execute the following command: eject cdrom

Problem  

Bug ID: 4948755 

The mouse wheel does not work when running Java applications. 

Solution  

Perform the following actions when you install the system: 

1. Open the following file with a text editor: XF86Config

2. Insert the following line: Option "ZAxisMapping" "4 5"

Problem  

You cannot connect to the network using a dial-up PPP connection. 

Solution  

If you are using a modem for your network connection, and you require a dial up PPP connection, use the Linux PPP dialer command utility wvdial.

Problem  

Bug ID: 4955086 

Modem dialup does not work for non-root users. This problem occurs because the setuid bit in the pppd utility is not set. The setuid bit on wvdial is also not set.

Solution  

Perform the following actions: 

1. Log in as root user.

2. Execute the following command: chmod +s /usr/sbin/pppd

Problem  

New network places do not appear in the Network Places window.

Solution  

Log out and log in again.