Sign In Sign-Up

Welcome!

Close

Would you like to make this site your homepage? It's fast and easy...

Yes, Please make this my home page!

No Thanks

  Don't show this to me again.

Close

E	Known bugs

Updated: 10 Dec 97

See also the CHANGES for info on fixed problems!

• Extension editor:

  When you press <Button-1> down and move the pointer out of a listbox, only that listbox scrolls. The idea is that all of them would scroll.
  FIXED IN VERSION 1.30
  Seems to work incorrectly with wish4.0




• Virtual filesystems:

  File operations do not work properly with files that have whitespaces within their names.
  FIXED IN VERSION 1.30




• Virtual filesystems:

  If you open a gzipped tar-package, you cannot do any file operations (e.g. copy files) INTO the package. This is limitation in the tar program, so we will not try to go around it in anyway. If you want to do such operations, unpack the package first.




• Virtual filesystems:

  Tar-packages that have filenames starting with ../ do not open.




• Virtual filesystems:

  When deleting from a tar-package (Linux), the deletion sometimes deletes also/entirely other files than those intended. This seems to be a "bug" in the tar-program.




• Mounting floppies with [Mount]

  If you mount a floppy with the [Mount] procedure, remove the floppy from the drive and then try to do fileoperations to the floppy you get of course an error. But for some reason this makes the [Mount] unusable i.e. you cannot change to another floppy with it after this. You either have to restart X-Files or do from shell an umount operation for the device. Or you could make an Umount actionbutton for that, too.




• Output Windows Fileselector

  Sometimes if you change the directory using the middle mousebutton you get an error "...TKPRIV(x)..." .




• Error message

  Sometimes when you get an error, you get immediately after that another error: "can't read "env(XF_HOME)": no such element in array".
  FIXED IN VERSION 1.30




• File links

  Links cause occasional error messages with some operations and also if you have the Autoupdate-option on.
  FIXED IN VERSION 1.30




• Filenames with spaces.

  These do not work as they should. We will fix this in the next release (v1.30)
  FIXED IN VERSION 1.30




• Command-line argument

  If you give as command-line argument a subdir (ie. X-Files subdir/) it resulted in error.
  FIXED IN VERSION 1.30




• Virtual filesystems:

  In Silicon Graphic- and Alpha-machines VirtualOutput (ie. double-clicking a file in VirtualTar) does not work. Instead it extracts the file to the same directory where the package is. This has to do with the flags of tar, they are not the same as in Linux-machines.




• X-Files and Solaris:

  On Solaris, when starting X-Files you get an error about "(block / 2)", you must go to the directory ~/.x-files/ and edit the file xfiles.commands???. There change the line that says
  set xf(DISKFREE) {df}
  to
  set xf(DISKFREE) {df -k}




• X-Files and new HP-UX:

  At least at our school when they upgraded the OS version of HP-UX:s, the DiskFree functionality stopped working correctly.




• The AutoUpdate-option

  It would seem that on some occasions the AutoUpdate and the real situation on the filesystem 'get out of sync' and it results in error. Eg. can't read vdleft(size), no such variable
  FIXED IN VERSION 1.42




• MailCheck -option

  If you had an empty mailbox when starting X-Files with MailCheck option on, the option was disabled altogether!
  FIXED IN VERSION 1.40b




• Resource Editor

  If you add by hand your own resource to xfilesrc, Resource Editor gets confused the next time you open it: it duplicates your resource.




• SafeDelete and the trash directory

  If you set the trash directory to point to any directory that had important data in it and you had the SafeDelete-option on, the directory was cleared every time you deleted something. Also, if you emptied the trash directory field in the Resource Editor ie. you did not define any trash directory, it got set as '/'. Fatal if you were running X-Files as root!
  Now the trash directory entry defines the place where the actual trash directory will be created.
  FIXED IN VERSION 1.42




• The "Additional Info" -field in "Mail X-Files Error" -dialog

  When filling in the "Additional Info" field in the "Error Mail" -dialog, the actual error contents changed due to a bug in Tk ie. the error and your info were not anymore related. We now have a workaround for this.
  FIXED IN VERSION 1.42