Java Desktop System Release 2 Troubleshooting Guide

General Desktop Problems

Files Do Not Open

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. 

File Manager Crashes

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.

Blueprint Theme Does Not Display Correctly

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 ViewApply ThemeBlueprint Beta.

Blank Pages Print Out From Ghostscript

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.

Cannot Eject a Floppy Disk

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.

Cannot Eject a CDROM

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

Mouse Wheel Does Not Work

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"