LyX error - the document could not be saved
I have just installed LyX on my Laptop.
I tried to edit an existing .lyx document I had and then I tried to save it.
I am getting the following error: "The document could not be saved. Do you want to rename the document and try again?"
When trying to rename and save in the same location I get the following error:
More information:
I'm running windows 10
I tried to run LyX as administrator but those errors stay the same.
The UAC is set as low as possible, and I am logged on as the administrator.The file is also not read-only.
The file is in a local folder within Dropbox, which may be related to the issue. I tried exiting dropbox process but I still get the same error, clicking "Retry" also gets this error.
Any ideas?
errors lyx
asked Nov 10 '17 at 9:19
BelgiBelgi
1171616
|
show 10 more comments
I have just installed LyX on my Laptop.
I tried to edit an existing .lyx document I had and then I tried to save it.
I am getting the following error: "The document could not be saved. Do you want to rename the document and try again?"
When trying to rename and save in the same location I get the following error:
More information:
I'm running windows 10
I tried to run LyX as administrator but those errors stay the same.
The UAC is set as low as possible, and I am logged on as the administrator.The file is also not read-only.
The file is in a local folder within Dropbox, which may be related to the issue. I tried exiting dropbox process but I still get the same error, clicking "Retry" also gets this error.
Any ideas?
errors lyx
asked Nov 10 '17 at 9:19
BelgiBelgi
1171616
Did saving with a new name help? Perhaps the file was write-protected somehow.
– Torbjørn T.
Nov 10 '17 at 9:20
1
Sometimes, Windows locks a document or directory because it is used or modified by another program. The reason is not always obvious. If so, a reboot will help.
– user24582
Nov 10 '17 at 10:07
1
Then something blocks probably specifically .lyx files. Check if some firewall or virus protection / defender is active and overeager. Check also the content of the pathext environment variable. Check your dropbox settings. And don't run lyx as admin but with your normal user rights: admins often don't have the rights to write into user folders.
– Ulrike Fischer
Nov 10 '17 at 11:52
1
I've seen Windows users have this error occasionally and I've never been able to reproduce on Ubuntu. If you find the problem, please let us know. Note that LyX 2.3.0rc1 should be out soon. You could give that a try if you were very daring (but of course you should back everything up before a big change).
– scottkosty
Nov 10 '17 at 19:06
1
I've noticed this as well on Windows (but not Ubuntu), and it does seem to be Dropbox related. If you just pause the syncing while saving these errors never occur, and then resume syncing when done. Frustrating.
– philchalmers
Jul 11 '18 at 6:11
|
show 10 more comments
I have just installed LyX on my Laptop.
I tried to edit an existing .lyx document I had and then I tried to save it.
I am getting the following error: "The document could not be saved. Do you want to rename the document and try again?"
When trying to rename and save in the same location I get the following error:
More information:
I'm running windows 10
I tried to run LyX as administrator but those errors stay the same.
The UAC is set as low as possible, and I am logged on as the administrator.The file is also not read-only.
The file is in a local folder within Dropbox, which may be related to the issue. I tried exiting dropbox process but I still get the same error, clicking "Retry" also gets this error.
Any ideas?
errors lyx
asked Nov 10 '17 at 9:19
BelgiBelgi
1171616
I have just installed LyX on my Laptop.
I tried to edit an existing .lyx document I had and then I tried to save it.
I am getting the following error: "The document could not be saved. Do you want to rename the document and try again?"
When trying to rename and save in the same location I get the following error:
More information:
I'm running windows 10
I tried to run LyX as administrator but those errors stay the same.
The UAC is set as low as possible, and I am logged on as the administrator.The file is also not read-only.
The file is in a local folder within Dropbox, which may be related to the issue. I tried exiting dropbox process but I still get the same error, clicking "Retry" also gets this error.
Any ideas?
errors lyx
errors lyx
asked Nov 10 '17 at 9:19
BelgiBelgi
1171616
asked Nov 10 '17 at 9:19
BelgiBelgi
1171616
edited Nov 22 '17 at 21:31
Belgi
asked Nov 10 '17 at 9:19
BelgiBelgi
1171616
asked Nov 10 '17 at 9:19
BelgiBelgi
1171616
asked Nov 10 '17 at 9:19
BelgiBelgi
1171616
1171616
Did saving with a new name help? Perhaps the file was write-protected somehow.
– Torbjørn T.
Nov 10 '17 at 9:20
1
Sometimes, Windows locks a document or directory because it is used or modified by another program. The reason is not always obvious. If so, a reboot will help.
– user24582
Nov 10 '17 at 10:07
1
Then something blocks probably specifically .lyx files. Check if some firewall or virus protection / defender is active and overeager. Check also the content of the pathext environment variable. Check your dropbox settings. And don't run lyx as admin but with your normal user rights: admins often don't have the rights to write into user folders.
– Ulrike Fischer
Nov 10 '17 at 11:52
1
I've seen Windows users have this error occasionally and I've never been able to reproduce on Ubuntu. If you find the problem, please let us know. Note that LyX 2.3.0rc1 should be out soon. You could give that a try if you were very daring (but of course you should back everything up before a big change).
– scottkosty
Nov 10 '17 at 19:06
1
I've noticed this as well on Windows (but not Ubuntu), and it does seem to be Dropbox related. If you just pause the syncing while saving these errors never occur, and then resume syncing when done. Frustrating.
– philchalmers
Jul 11 '18 at 6:11
|
show 10 more comments
Did saving with a new name help? Perhaps the file was write-protected somehow.
– Torbjørn T.
Nov 10 '17 at 9:20
1
Sometimes, Windows locks a document or directory because it is used or modified by another program. The reason is not always obvious. If so, a reboot will help.
– user24582
Nov 10 '17 at 10:07
1
Then something blocks probably specifically .lyx files. Check if some firewall or virus protection / defender is active and overeager. Check also the content of the pathext environment variable. Check your dropbox settings. And don't run lyx as admin but with your normal user rights: admins often don't have the rights to write into user folders.
– Ulrike Fischer
Nov 10 '17 at 11:52
1
I've seen Windows users have this error occasionally and I've never been able to reproduce on Ubuntu. If you find the problem, please let us know. Note that LyX 2.3.0rc1 should be out soon. You could give that a try if you were very daring (but of course you should back everything up before a big change).
– scottkosty
Nov 10 '17 at 19:06
1
I've noticed this as well on Windows (but not Ubuntu), and it does seem to be Dropbox related. If you just pause the syncing while saving these errors never occur, and then resume syncing when done. Frustrating.
– philchalmers
Jul 11 '18 at 6:11
Did saving with a new name help? Perhaps the file was write-protected somehow.
– Torbjørn T.
Nov 10 '17 at 9:20
Did saving with a new name help? Perhaps the file was write-protected somehow.
– Torbjørn T.
Nov 10 '17 at 9:20
1
1
Sometimes, Windows locks a document or directory because it is used or modified by another program. The reason is not always obvious. If so, a reboot will help.
– user24582
Nov 10 '17 at 10:07
Sometimes, Windows locks a document or directory because it is used or modified by another program. The reason is not always obvious. If so, a reboot will help.
– user24582
Nov 10 '17 at 10:07
1
1
Then something blocks probably specifically .lyx files. Check if some firewall or virus protection / defender is active and overeager. Check also the content of the pathext environment variable. Check your dropbox settings. And don't run lyx as admin but with your normal user rights: admins often don't have the rights to write into user folders.
– Ulrike Fischer
Nov 10 '17 at 11:52
Then something blocks probably specifically .lyx files. Check if some firewall or virus protection / defender is active and overeager. Check also the content of the pathext environment variable. Check your dropbox settings. And don't run lyx as admin but with your normal user rights: admins often don't have the rights to write into user folders.
– Ulrike Fischer
Nov 10 '17 at 11:52
1
1
I've seen Windows users have this error occasionally and I've never been able to reproduce on Ubuntu. If you find the problem, please let us know. Note that LyX 2.3.0rc1 should be out soon. You could give that a try if you were very daring (but of course you should back everything up before a big change).
– scottkosty
Nov 10 '17 at 19:06
I've seen Windows users have this error occasionally and I've never been able to reproduce on Ubuntu. If you find the problem, please let us know. Note that LyX 2.3.0rc1 should be out soon. You could give that a try if you were very daring (but of course you should back everything up before a big change).
– scottkosty
Nov 10 '17 at 19:06
1
1
I've noticed this as well on Windows (but not Ubuntu), and it does seem to be Dropbox related. If you just pause the syncing while saving these errors never occur, and then resume syncing when done. Frustrating.
– philchalmers
Jul 11 '18 at 6:11
I've noticed this as well on Windows (but not Ubuntu), and it does seem to be Dropbox related. If you just pause the syncing while saving these errors never occur, and then resume syncing when done. Frustrating.
– philchalmers
Jul 11 '18 at 6:11
|
show 10 more comments
2 Answers
2
active
oldest
votes
I have the same problem, I think it is caused by the way dropbox manages files on windows.
Lyx creates a new file and then tries to change its name, which under dropbox creates a conflict which cannot be resolved automatically.
I suggest working outside the dropbox folder and only move the finished files there.
edited Oct 16 '18 at 10:49
samcarter
1
answered Oct 16 '18 at 10:27
GiladGilad
212
add a comment |
As of Windows 10 (1803), the issue may also be caused by Windows Defender's optional ransomware protection, which doesn't recognize LyX as a legitimate program by default.
Note that nothing will indicate, that this feature is the cause.
answered Feb 13 at 18:57
kdbkdb
832514
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f400615%2flyx-error-the-document-could-not-be-saved%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have the same problem, I think it is caused by the way dropbox manages files on windows.
Lyx creates a new file and then tries to change its name, which under dropbox creates a conflict which cannot be resolved automatically.
I suggest working outside the dropbox folder and only move the finished files there.
edited Oct 16 '18 at 10:49
samcarter
1
answered Oct 16 '18 at 10:27
GiladGilad
212
add a comment |
I have the same problem, I think it is caused by the way dropbox manages files on windows.
Lyx creates a new file and then tries to change its name, which under dropbox creates a conflict which cannot be resolved automatically.
I suggest working outside the dropbox folder and only move the finished files there.
edited Oct 16 '18 at 10:49
samcarter
1
answered Oct 16 '18 at 10:27
GiladGilad
212
add a comment |
I have the same problem, I think it is caused by the way dropbox manages files on windows.
Lyx creates a new file and then tries to change its name, which under dropbox creates a conflict which cannot be resolved automatically.
I suggest working outside the dropbox folder and only move the finished files there.
edited Oct 16 '18 at 10:49
samcarter
1
answered Oct 16 '18 at 10:27
GiladGilad
212
I have the same problem, I think it is caused by the way dropbox manages files on windows.
Lyx creates a new file and then tries to change its name, which under dropbox creates a conflict which cannot be resolved automatically.
I suggest working outside the dropbox folder and only move the finished files there.
edited Oct 16 '18 at 10:49
samcarter
1
answered Oct 16 '18 at 10:27
GiladGilad
212
edited Oct 16 '18 at 10:49
samcarter
1
edited Oct 16 '18 at 10:49
samcarter
1
edited Oct 16 '18 at 10:49
samcarter
1
1
answered Oct 16 '18 at 10:27
GiladGilad
212
answered Oct 16 '18 at 10:27
GiladGilad
212
answered Oct 16 '18 at 10:27
GiladGilad
212
212
add a comment |
add a comment |
As of Windows 10 (1803), the issue may also be caused by Windows Defender's optional ransomware protection, which doesn't recognize LyX as a legitimate program by default.
Note that nothing will indicate, that this feature is the cause.
answered Feb 13 at 18:57
kdbkdb
832514
add a comment |
As of Windows 10 (1803), the issue may also be caused by Windows Defender's optional ransomware protection, which doesn't recognize LyX as a legitimate program by default.
Note that nothing will indicate, that this feature is the cause.
answered Feb 13 at 18:57
kdbkdb
832514
add a comment |
As of Windows 10 (1803), the issue may also be caused by Windows Defender's optional ransomware protection, which doesn't recognize LyX as a legitimate program by default.
Note that nothing will indicate, that this feature is the cause.
answered Feb 13 at 18:57
kdbkdb
832514
As of Windows 10 (1803), the issue may also be caused by Windows Defender's optional ransomware protection, which doesn't recognize LyX as a legitimate program by default.
Note that nothing will indicate, that this feature is the cause.
answered Feb 13 at 18:57
kdbkdb
832514
answered Feb 13 at 18:57
kdbkdb
832514
answered Feb 13 at 18:57
kdbkdb
832514
answered Feb 13 at 18:57
kdbkdb
832514
832514
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f400615%2flyx-error-the-document-could-not-be-saved%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did saving with a new name help? Perhaps the file was write-protected somehow.
– Torbjørn T.
Nov 10 '17 at 9:20
1
Sometimes, Windows locks a document or directory because it is used or modified by another program. The reason is not always obvious. If so, a reboot will help.
– user24582
Nov 10 '17 at 10:07
1
Then something blocks probably specifically .lyx files. Check if some firewall or virus protection / defender is active and overeager. Check also the content of the pathext environment variable. Check your dropbox settings. And don't run lyx as admin but with your normal user rights: admins often don't have the rights to write into user folders.
– Ulrike Fischer
Nov 10 '17 at 11:52
1
I've seen Windows users have this error occasionally and I've never been able to reproduce on Ubuntu. If you find the problem, please let us know. Note that LyX 2.3.0rc1 should be out soon. You could give that a try if you were very daring (but of course you should back everything up before a big change).
– scottkosty
Nov 10 '17 at 19:06
1
I've noticed this as well on Windows (but not Ubuntu), and it does seem to be Dropbox related. If you just pause the syncing while saving these errors never occur, and then resume syncing when done. Frustrating.
– philchalmers
Jul 11 '18 at 6:11