Bug 41869 - Writer not responding after save a document on a crypted volume, after timemachine is run
Summary: Writer not responding after save a document on a crypted volume, after timema...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.4.3 RC1
Hardware: Other macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-17 04:22 UTC by marcus.kuhn
Modified: 2012-11-16 14:47 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description marcus.kuhn 2011-10-17 04:22:39 UTC
Hello,

hope i'm right here, cause it's my first bug i report.
I have some docs on a crypted volume-image (dosn't matter it's truecrypt or Apples dmg) on Mac OS Lion (Snowleopard works fine!). 

When i open the doc all is fine. Save works normal till Apples timemachine starts an make a backup. After this, save will not work anymore. It lead to a "not responding" Writer in the first step and a system crash in the second. In the worst case all changes will be lost since open the doc. 

The problem is reproducible. (At least on my mac)

Please help.

Marcus
Comment 1 Alex Thurgood 2012-02-09 11:41:03 UTC
The problem is that we don't have (m)any QA testers with your particular setup :
- OSX Lion
- encrypted backup used to store, access, and write a file
- TimeMachine running in the background

Just out of interest, your TimeMachine isn't backing up to the same volume as you are reading/writing your file to ?


I have found that TimeMachine, when running, stops a lot of other disk activity from happening, most noticeably file writes, for example online backups to MobileMe are always deferred while TimeMachine is running. Maybe not so coincidental ?

Alex
Comment 2 marcus.kuhn 2012-02-09 12:14:28 UTC
Hello Alex,

sad, but i've allready thougt it.

My TimeMachine Volume is a NAS from WD and a completely different disk.

In meanwhile i have found some things, that reduces the error counts: 
1. Check user rights with the diskutility then repair the user rights. (The check is important.)
2. Don't use Networkvolumes.
3. Crypted Volumes from diskutility works better than TrueCrypt Volumes

Yesterday I installed Lion 10.7.3 should I give You some information about this problem?

Marcus
 
Am 09.02.2012 um 20:41 schrieb bugzilla-daemon@freedesktop.org:

> https://bugs.freedesktop.org/show_bug.cgi?id=41869
> 
> --- Comment #1 from Alex Thurgood <iplaw67@yahoo.co.uk> 2012-02-09 11:41:03 PST ---
> The problem is that we don't have (m)any QA testers with your particular setup
> :
> - OSX Lion
> - encrypted backup used to store, access, and write a file
> - TimeMachine running in the background
> 
> Just out of interest, your TimeMachine isn't backing up to the same volume as
> you are reading/writing your file to ?
> 
> 
> I have found that TimeMachine, when running, stops a lot of other disk activity
> from happening, most noticeably file writes, for example online backups to
> MobileMe are always deferred while TimeMachine is running. Maybe not so
> coincidental ?
> 
> Alex
> 
> -- 
> Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
Comment 3 Julien Nabet 2012-05-16 16:06:16 UTC
In the meantime, 10.7.4 has been released (http://osxdaily.com/tag/mac-os-x-10-7/) perhaps it may help.
Above all, could you try to reproduce this problem with a new LO version, 3.5.3 and a brand new LO profile (to be sure not to have junk or corrupted elements), see http://wiki.documentfoundation.org/UserProfile ?
Comment 4 Roman Eisele 2012-11-16 14:47:06 UTC
Dear bug reporter,
dear commenters,

I am sorry, but we can not make any progress about this issue without further information from you. The important question in comment #3 has not been answered for a long time. Therefore we need to close this bug report for now.
Feel free to open it again, if you can reproduce this issue in a current version of LibreOffice (3.5.7, or better: 3.6.3 or newer).

Thank you very much!