Public bug reported:
Ubuntu 64 bit version cannot read all the file names created in the 32 bit
version or in the Doze.
More simply, I finally built a file server and copied all of our files over to
it using a 32 bit version of Ubuntu........
ALL of the document files are VISIBLE in the 32 bit version on ALL of our
Ubuntu computers!
They can be opened with Open Office, Edited and rewritten (or even simply
copied) to ANY shared folder on ANY 32 bit Ubuntu Computer, including the File
Server, EXCEPT the computer with the newly installed 64 bit version of Ubuntu.
It generates the error, Invalid Argument! (Actually this is GOOD! So the
complaint is not here! It's how I found the problem!)
Where the problem lies is that the 64 bit version of Ubuntu cannot SEE
these particular files as they reside on any computer or on the file
server. If the file is on the hard drive, and the 32 bit versions can
see it, open it, copy it, etc. Then so should the 64 bit version.
It's OBVIOUS there is a illegal naming convention in the files. They
CAN be opened and the filenames corrected using a 32 bit version of
Ubuntu. But it will take virtually FOREVER to amend the file names of
over 150,000 files doing them one at a time! It took long enough to go
through all of our .doc files and convert them to .odt files AND we were
able to save all of these files over the three recent months it took to
do this!
It's OK to NOT ALLOW illegal characters to be used in file names! And give a
Warning!
But it's NOT OK to SHOW these files in ONE Version of Ubuntu and NOT in another
version of Ubuntu!
They are there, so SHOW THEM and allow them to be opened to be fixed.
As it stand right now, our ONLY alternative is to DELETE the 64 bit
version and return to the more user friendly 32 bit version! Checking
on PROPERTIES shows these files are there! But they do NOT appear in
the 64 bit version.
The 32 bit version of Ubuntu will NOT allow a file search for the illegal
characters, in order to find and correct them!
But it doesn't know they are errors either as through todays date, we have been
using this file naming convention on numerous documents and the 32 bit version
never complained that there were ANY illegal file name characters in use.
Didn't see my log-in when I started this, so I am:
Gary V Deutschmann Sr
classichauslimi...@bbs.galilei.com
Kellemora on the Ubuntu Forums
If you need any more information!
I'm also reporting to Open Office that their OOoWriter allows one to
save files with illegal characters with no warnings!
TTUL
Gary
** Affects: ubuntu
Importance: Undecided
Status: New
--
Files don't appear in 64 bit Hardy that appear in 32 bit Hardy
https://bugs.launchpad.net/bugs/325129
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
