Locked files in libreoffice calc within a directory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libreoffice (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hi
I have accidentally locked three libreoffice calc files within a directory. It initially happened within a dropbox directory but was soon apparent within the original directory where these files were housed. Even if I rename one of these files, it still won't open within the directory. All I get is a 'locked' file icon. I am the only user of this PC. I think libreoffice calc believes there is another user editing the file, hence the lock. However I can easily delete this locked file by right click, delete.
However the strange thing is that I can access these same three files through the applications menu. The file(s) will open, can be edited and saved. This has been the only way I have been accessing these calc files over the last three weeks. Please note that I don't have an issue with libreoffice writer within these directories.
I am at a complete loss as to what happened here. Even if I create a new calc file, it will still lock if I attempt to open it with a directory but not if I open it via the applications menu.
I am using ubuntu 11.04. The version is 1:3.3.3-Ubuntu1
Many thanks
Eddie
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: libreoffice-core 1:3.3.3-1ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-10-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Jul 20 18:10:28 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: Upgraded to natty on 2011-05-25 (56 days ago)
Thank you for reporting this bug to Ubuntu. Ubuntu 11.04 reached EOL on October 28, 2012. /wiki.ubuntu. com/Releases
See this document for currently supported Ubuntu releases: https:/
Can you reproduce this bug on a newer Ubuntu release? Ubuntu 12.04 or newer preferably.
This bug sounds like an issue that might end up being fixed by a restart.
Do feel free to report any other bugs you may find.