file corruption on samba shares

Bug #239497 reported by arttherapylinux
This bug affects 1 person
Affects Status Importance Assigned to Milestone (Ubuntu)

Bug Description

When accessing files from Windows server the file states it is corrupt. It is then able to open but saving it again is a pain which often leads to another corrupt file.

Revision history for this message
Richard Seguin (sectech) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" [WWW] We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at [WWW]

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

Revision history for this message
Richard Seguin (sectech) wrote :

*Marking as incomplete pending enough information to complete triage

Revision history for this message
arttherapylinux (arttherapylinux) wrote :

Ok, I'll try again,

when I attempt to open an open office odt file I get the following screen.

I use the computer at work. I am using Ubuntu 8.04. I connect through window share to a folder on a server with windows 2003 on it.

When I upgraded to 8.04 from 7.10 I noticed that this error would show up. Say I am working with file1.odt located in this location. folder1/folder2/folder3/file1.odt then I get the error. My default save location in open office is set up to be folder1 not folder3 then I have to start at folder1 locate folder3 again and then retype the name of the file and save. If I do this or give the file a new name then the next time I open the file I often get the same message.

I hope this helps


Revision history for this message
Richard Seguin (sectech) wrote :

Do you know if this happens with other files (that might not be open office)?

Revision history for this message
arttherapylinux (arttherapylinux) wrote :

Appears to be just open office. However, when I first upgraded I could not see other files on the server. Such as PDF, jpg. I was not allowed to link like I have in the past. I would open openoffice then open recent files. I started to have so many problems with 8.04 that I then used a clean install. This problem has continued as well as loosing my insert button on my keyboard. I wondered if the files I used during this time were corrupt, however, opening older files gave me the same problem.

Revision history for this message
Marko Gnjidic (markog-iskon) wrote :

I may have a bit more info on this since I have the same problem.

The situation in question only happens while editing files in OpenOffice 2.4 over network directly thru smb:// protocol. This did not happen in 7.10

The exact behaviour is: I open an existing spreadsheet file on 8.04 (over smb://), do some work on it, and save it. After I save it, it becomes corrupted 80% of the time. At that point the document is not openable by any OS/OpenOffice combination, it just reports a corrupt file which cannot be repaired.

Working with other programs and documents over smb:// works properly.

Any clues?

Revision history for this message
arttherapylinux (arttherapylinux) wrote :

I am wondering if this could be connected with samba some how.
I have been asked to type in my password more then once, and I do not know how to make the new active directory component functional.

Also this morning the computer was on but typing and using the mouse would not wake it up. I was forced to do a hard reboot. When I attempted to recover an open office file then a file that was not corrupt before was now corrupt. The repair function has always been able to open the file.

Revision history for this message
Chris Cheney (ccheney) wrote :


If you copy the file from the Windows server to your local system then try to open it does it still say it is corrupted then?

It also sounds like you may be having hardware problems with your computer if the screen goes black and won't come back on, especially if you hadn't put your system into suspend mode. Some systems have trouble coming out of suspend mode, but if your system wasn't actually in suspend and still wouldn't turn the display back on that is a bad sign.


Revision history for this message
arttherapylinux (arttherapylinux) wrote :

yes, after copying to desktop file is still corrupt.

I do not use suspend mode. I leave computer on all the time. Hard drive light will be on and blinking when locked up. Should this be linked to a new bug?


Revision history for this message
Chris Cheney (ccheney) wrote :

So you are saying if you take a known good file put it on the smb share then edit it with and save it again it becomes corrupted?

Revision history for this message
RG (drats77) wrote :

I was linked into this problem through one I reported #32500.

Symptoms almost identical. Known good file on an smb share is edited with OpenOffice app and file is reported as corrupt when it is subsequently open for editing. For me the file is repairable, also it only corrupts maybe 10 or 20 percent of the time. This happens on two servers: a maxtor network drive, or a share on another Ubuntu box.

This problem only appeared after upgrading to Ubuntu 8.04.... 7.10 worked wonderfully.

I've just installed SUSE 11.0 I have the same problem with OpenOffice on it corrupting files when editing a file on a network share.

gedit works just fine. I've never had any trouble editing files on the network shares.

Chris Cheney (ccheney)
Changed in
status: Incomplete → Confirmed
Revision history for this message
sofie (sofie4you) wrote :

Good evening,

I posted sometime ago the same bug. Only under another description. In my case it mostly happens with spreadsheets an also corrputs in 20% of the time. Larger files more often. I use Hardy.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments