Red Hat Bugzilla – Bug 39547
vfat and staroffice are not friends
Last modified: 2008-05-01 11:38:00 EDT
Description of Problem:
staroffice and maby other programs have "problems" working with the vfat
module which shipped with 7.1. It can no write files and delete folders
How Reproducible: infinately, happens every time
Steps to Reproduce:
1. mount a vfat filesystem
2. try and access with staroffice
I have tried the msdos module and there is no problem but short
filenames. I know this was working in 7.0 because I still use it that
way on one computer and I did on the machine I am now having problems on
then. A fix or a workaround would be very much so appreciated. btw I am
running KDE, not sure if it matters.
Description of Distutils:
"A collection of modules to aid in the distribution and installation of
Python modules, extensions, and (ultimately) applications. A standard
part of Python 1.6 and 2.0, but also distributed separately for use with
This is not remotely distutils related... if this is a bug, and not simply a
permissions problem, it would be kernel-related. However, I believe this would
be caused by your setup - root can read and write files, right?
Yes, does root have write access ?
root can access the files as can everyone else except from staroffice. I know
it is not KDE because it happens when I am not running a windows manager, just
a terminal to launch staroffice.
Are you running Star Office as the root user?
This starts to look like a Staroffice bug
I thought it might be a staroffice bug except that it works with every other
filesystem I have tried and on vfat on a 7.0 filesystem.
I am running staroffice as root or myself. Either way it happens. I do not
think it is staroffice because I could access vfat filesystems from staroffice
in 7.0 but not 7.1.
To get things 100% clear: you are able to make files etc on the same
partition from, say, the shell or the KDE filemanager?
yes, I have yet to find another program it does not work with but I can not see
the differences between the 2.2 and the 2.4 kernel affecting only staroffice in
Star Office erroneously assumes it may ftruncate() a file larger than before.
This isnt guaranteed to work and 2.4 vfat legitimately errors it.
So yes - it really is star office, its one of only two apps I know that make
this sssumption blindly (the other is one part of the netscape messenger mailbox
Holy finger pointing! Red Hat! Ain't we all happy? So what if Star Office can't
be used with vfat in 7.1? It's resolved!
Tell me how I can fix a bug in Star Office and I'll consider it.
Until then there's nothing we can do