SOLVED > lyx not a readable Lyx document

[Wolfgang Engelmann]

As described behind the #

I followed JMarcs adviced:

If you still have the directory where you built LyX, then
>>gitpull >(should be git pull)

I think I forgot to merge after git pull

I guess it is the easiest to get the dev version anew

By the way, when will the 2.4 version be available?

Wolfgang


#
Am 13.04.22 um 16:48 schrieb Wolfgang Engelmann:

This is a kind reminder to those, who might be able to help
Wolfgang

Am 09.04.22 um 19:15 schrieb Wolfgang Engelmann:

 >>> I followed the advice of JMarc >

If you still have the directory where you built LyX, then
   gitpull >(should be git pull)
   make
should be enough (you can add "./autogen.sh" as a second line to play 
safe). > this I omitted


But you have a newer LyX 2.4 somewhere, since you produced a file with 
it!


JMarc



The LyX format itself changes regularly during the 2.4.0dev timeline. 
lyx2lyx is updated simultaneously.


When 2.4.0 is released, the format will be fixed and lyx2lyx (barring 
bugs) will stay the same during the lifetime of the branch.
The only exception is that the last 2.4 version will get an updated 
lyx2lyx that can read the 2.5 format.


Likewise, LyX 2.3.7 will be able to read and produce the 2.4.0 format.

JMarc

___

and from https://www.lyx.org/HowToUseGIT >

4.  Anonymous Git clone

 From within the directory where you want to place your local copy of 
the sources, do:


  git clone git://git.lyx.org/lyx

This will make a directory lyx and download lots of files into that 
directory. (A fresh copy will need about 400MB. However, you will need 
a lot more space for the compiled version -- up to 2 GB).


You can switch to maintenance branch via git checkout 2.3.x inside the 
lyx directory.

5.  After the first download

If the code is updated, just cd to the lyx directory and say:

  git pull

This will magically download or patch only those files which have been 
changed or added, saving you (and the server) lots of time.


If you just want to check what's changed in your local copy as opposed 
to the repository, do:


  git status
__
git status
Auf Branch master
Ihr Branch ist auf demselben Stand wie 'origin/master'.

Änderungen, die nicht zum Commit vorgemerkt sind:
   (benutzen Sie "git add ...", um die Änderungen zum Commit 
vorzumerken)
   (benutzen Sie "git restore ...", um die Änderungen im 
Arbeitsverzeichnis zu verwerfen)

 geändert:   po/ar.gmo 

keine Änderungen zum Commit vorgemerkt (benutzen Sie "git add" 
und/oder "git commit -a")


___

 > however, after it and after
./configure --with-version-suffix=lyx24n
(I unfortunately forgot --bindir=/usr/local/bin)
make
make install

and running a lyx file I get again:

Warning: 609: Format not supported.
Warning: Quitting.
Error: Dokumentformat-Fehler

/tmp/lyx_tmpdir.VqwdxGawWrac/Buffer_convertLyXFormatZYzSIl.lyx ist 
kein lesbares LyX-Dokument.
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 818, 
resource id: 0, major code: 20 (GetProperty), minor code: 0

Warning: 609: Format not supported.
Warning: Quitting.
Error: Dokumentformat-Fehler

 
I am confused.

Does it mean, I have to get all the git stuff again, because for some 
reason the git pull does not update the git stuff, although it says so 
in the https://www.lyx.org/HowToUseGIT ?


Wolfgang

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Re: lyx not a readable Lyx document

[Wolfgang Engelmann]

Am 16.04.22 um 11:04 schrieb Wolfgang Engelmann:

I got this message:

Am 14.04.22 um 22:24 schrieb Nathan Blodgett:
Alright then, I will post to lyx-devel and with more info. 
Basically Pacstall is package manager for Debian based systems and for 
more info see pacstall.dev .



and the reply after the http was
502 Bad Gateway
nginx/1.18.0
I have sent a message to Nathan Blodgett a few minutes ago privately.
Wolfgang Engelmann

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx not a readable Lyx document

[José Abílio Matos]

On Saturday, 9 April 2022 18.15.31 WEST Wolfgang Engelmann via lyx-users 
wrote:
>  > however, after it and after
> 
> ./configure --with-version-suffix=lyx24n
> (I unfortunately forgot --bindir=/usr/local/bin)
> make
> make install
> 
> and running a lyx file I get again:
> 
> Warning: 609: Format not supported.
> Warning: Quitting.
> Error: Dokumentformat-Fehler
> 

What is the version you are running?

Help->About LyX

I suspect that you have different versions in your path and that the older one 
is selected.

I hope that this help.
-- 
José Abílio-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx not a readable Lyx document

[Wolfgang Engelmann via lyx-users]

This is a kind reminder to those, who might be able to help
Wolfgang

Am 09.04.22 um 19:15 schrieb Wolfgang Engelmann:

 >>> I followed the advice of JMarc >

If you still have the directory where you built LyX, then
   gitpull >(should be git pull)
   make
should be enough (you can add "./autogen.sh" as a second line to play 
safe). > this I omitted


But you have a newer LyX 2.4 somewhere, since you produced a file with it!

JMarc



The LyX format itself changes regularly during the 2.4.0dev timeline. 
lyx2lyx is updated simultaneously.


When 2.4.0 is released, the format will be fixed and lyx2lyx (barring 
bugs) will stay the same during the lifetime of the branch.
The only exception is that the last 2.4 version will get an updated 
lyx2lyx that can read the 2.5 format.


Likewise, LyX 2.3.7 will be able to read and produce the 2.4.0 format.

JMarc

___

and from https://www.lyx.org/HowToUseGIT >

4.  Anonymous Git clone

 From within the directory where you want to place your local copy of 
the sources, do:


  git clone git://git.lyx.org/lyx

This will make a directory lyx and download lots of files into that 
directory. (A fresh copy will need about 400MB. However, you will need a 
lot more space for the compiled version -- up to 2 GB).


You can switch to maintenance branch via git checkout 2.3.x inside the 
lyx directory.

5.  After the first download

If the code is updated, just cd to the lyx directory and say:

  git pull

This will magically download or patch only those files which have been 
changed or added, saving you (and the server) lots of time.


If you just want to check what's changed in your local copy as opposed 
to the repository, do:


  git status
__
git status
Auf Branch master
Ihr Branch ist auf demselben Stand wie 'origin/master'.

Änderungen, die nicht zum Commit vorgemerkt sind:
   (benutzen Sie "git add ...", um die Änderungen zum Commit 
vorzumerken)
   (benutzen Sie "git restore ...", um die Änderungen im 
Arbeitsverzeichnis zu verwerfen)

     geändert:   po/ar.gmo 

keine Änderungen zum Commit vorgemerkt (benutzen Sie "git add" und/oder 
"git commit -a")


___

 > however, after it and after
./configure --with-version-suffix=lyx24n
(I unfortunately forgot --bindir=/usr/local/bin)
make
make install

and running a lyx file I get again:

Warning: 609: Format not supported.
Warning: Quitting.
Error: Dokumentformat-Fehler

/tmp/lyx_tmpdir.VqwdxGawWrac/Buffer_convertLyXFormatZYzSIl.lyx ist kein 
lesbares LyX-Dokument.
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 818, 
resource id: 0, major code: 20 (GetProperty), minor code: 0

Warning: 609: Format not supported.
Warning: Quitting.
Error: Dokumentformat-Fehler

 
I am confused.

Does it mean, I have to get all the git stuff again, because for some 
reason the git pull does not update the git stuff, although it says so 
in the https://www.lyx.org/HowToUseGIT ?


Wolfgang

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

lyx not a readable Lyx document

[Wolfgang Engelmann via lyx-users]

>>> I followed the advice of JMarc >

If you still have the directory where you built LyX, then
  gitpull >(should be git pull)
  make
should be enough (you can add "./autogen.sh" as a second line to play 
safe). > this I omitted


But you have a newer LyX 2.4 somewhere, since you produced a file with it!

JMarc



The LyX format itself changes regularly during the 2.4.0dev timeline. 
lyx2lyx is updated simultaneously.


When 2.4.0 is released, the format will be fixed and lyx2lyx (barring 
bugs) will stay the same during the lifetime of the branch.
The only exception is that the last 2.4 version will get an updated 
lyx2lyx that can read the 2.5 format.


Likewise, LyX 2.3.7 will be able to read and produce the 2.4.0 format.

JMarc

___

and from https://www.lyx.org/HowToUseGIT >

4.  Anonymous Git clone

From within the directory where you want to place your local copy of 
the sources, do:


 git clone git://git.lyx.org/lyx

This will make a directory lyx and download lots of files into that 
directory. (A fresh copy will need about 400MB. However, you will need a 
lot more space for the compiled version -- up to 2 GB).


You can switch to maintenance branch via git checkout 2.3.x inside the 
lyx directory.

5.  After the first download

If the code is updated, just cd to the lyx directory and say:

 git pull

This will magically download or patch only those files which have been 
changed or added, saving you (and the server) lots of time.


If you just want to check what's changed in your local copy as opposed 
to the repository, do:


 git status
__
git status
Auf Branch master
Ihr Branch ist auf demselben Stand wie 'origin/master'.

Änderungen, die nicht zum Commit vorgemerkt sind:
  (benutzen Sie "git add ...", um die Änderungen zum Commit 
vorzumerken)
  (benutzen Sie "git restore ...", um die Änderungen im 
Arbeitsverzeichnis zu verwerfen)

geändert:   po/ar.gmo 

keine Änderungen zum Commit vorgemerkt (benutzen Sie "git add" und/oder 
"git commit -a")


___

> however, after it and after
./configure --with-version-suffix=lyx24n
(I unfortunately forgot --bindir=/usr/local/bin)
make
make install

and running a lyx file I get again:

Warning: 609: Format not supported.
Warning: Quitting.
Error: Dokumentformat-Fehler

/tmp/lyx_tmpdir.VqwdxGawWrac/Buffer_convertLyXFormatZYzSIl.lyx ist kein 
lesbares LyX-Dokument.
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 818, 
resource id: 0, major code: 20 (GetProperty), minor code: 0

Warning: 609: Format not supported.
Warning: Quitting.
Error: Dokumentformat-Fehler


I am confused.

Does it mean, I have to get all the git stuff again, because for some 
reason the git pull does not update the git stuff, although it says so 
in the https://www.lyx.org/HowToUseGIT ?


Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx not a readable Lyx document

[Wolfgang Engelmann via lyx-users]

Am 08.04.22 um 09:15 schrieb Jean-Marc Lasgouttes via lyx-users:

Le 08/04/2022 à 08:18, Wolfgang Engelmann via lyx-users a écrit :

are you saying, the lyx2lyx is changing in the 2.4.x?


The LyX format itself changes regularly during the 2.4.0dev timeline. 
lyx2lyx is updated simultaneously.


When 2.4.0 is released, the format will be fixed and lyx2lyx (barring 
bugs) will stay the same during the lifetime of the branch.
The only exception is that the last 2.4 version will get an updated 
lyx2lyx that can read the 2.5 format.


Likewise, LyX 2.3.7 will be able to read and produce the 2.4.0 format.

JMarc



ok, I understand.

That explains the troubles I had with
lyx not a readable Lyx document

Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx not a readable Lyx document

[Jean-Marc Lasgouttes via lyx-users]

Le 08/04/2022 à 08:18, Wolfgang Engelmann via lyx-users a écrit :

are you saying, the lyx2lyx is changing in the 2.4.x?


The LyX format itself changes regularly during the 2.4.0dev timeline. 
lyx2lyx is updated simultaneously.


When 2.4.0 is released, the format will be fixed and lyx2lyx (barring 
bugs) will stay the same during the lifetime of the branch.
The only exception is that the last 2.4 version will get an updated 
lyx2lyx that can read the 2.5 format.


Likewise, LyX 2.3.7 will be able to read and produce the 2.4.0 format.

JMarc

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx not a readable Lyx document

[Dr Eberhard Lisse via lyx-users]

Yes and no,

LyX 2.4 uses a different format from 2.3 and hence the (2.3) lyx2lyx
does not know the new (2.4) format (yet).

That happens during (almost) every major upgrade and the developers
then usually "backport" that so I would think the eventual 2.3.6.3 (or
2.3.7) will be able to read the 2.4 format.

el

On 2022-04-08 08:18 , Wolfgang Engelmann via lyx-users wrote:



Am 08.04.22 um 07:21 schrieb Dr Eberhard Lisse via lyx-users:

An older version of lyx2lyx can't know about newer formats?

el


On 2022-04-07 09:55 , Wolfgang Engelmann via lyx-users wrote:
[...]

I remember, that one does not need a lyx2lyx in the same version, here
2.4.x
Has this changed?

Wolfgang




are you saying, the lyx2lyx is changing in the 2.4.x?
Wolfgang


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx not a readable Lyx document

[Wolfgang Engelmann via lyx-users]

Am 08.04.22 um 07:21 schrieb Dr Eberhard Lisse via lyx-users:

An older version of lyx2lyx can't know about newer formats?

el


On 2022-04-07 09:55 , Wolfgang Engelmann via lyx-users wrote:
[...]

I remember, that one does not need a lyx2lyx in the same version, here
2.4.x
Has this changed?

Wolfgang




are you saying, the lyx2lyx is changing in the 2.4.x?
Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx not a readable Lyx document

[Dr Eberhard Lisse via lyx-users]

An older version of lyx2lyx can't know about newer formats?

el


On 2022-04-07 09:55 , Wolfgang Engelmann via lyx-users wrote:
[...]

I remember, that one does not need a lyx2lyx in the same version, here
2.4.x
Has this changed?

Wolfgang


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx not a readable Lyx document

[Wolfgang Engelmann via lyx-users]

Am 06.04.22 um 18:05 schrieb Jean-Marc Lasgouttes:

Le 06/04/2022 à 17:58, Wolfgang Engelmann a écrit :



Am 06.04.22 um 17:52 schrieb Jean-Marc Lasgouttes:

Le 06/04/2022 à 17:44, Wolfgang Engelmann a écrit :

And this is the output from the terminal starting lyx there:

lyx24x MEINLEBEN2020-B.lyx
Warning: 609: Format not supported.
Warning: Quitting.
Error: Document format failure


This is what I thought. It seems that you have a working recent lyx 
somewhere (the 609 version) and that now you try to read the file 
with an older version.


JMarc


Thanks a lot, JMarc.

Yes, it works now, very glad it does!
What is the best way to update the 2.4 version?
Do I have to use git again ?


If you still have the directory where you built LyX, then
   gitpull
   make
should be enough (you can add "./autogen.sh" as a second line to play 
safe).


But you have a newer LyX 2.4 somewhere, since you produced a file with it!

JMarc


I remember, that one does not need a lyx2lyx in the same version, here 2.4.x
Has this changed?

Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

SOLVED: lyx not a readable Lyx document

[Wolfgang Engelmann via lyx-users]

JMarc found out that the version was an older one.

Wolfgang

Am 06.04.22 um 17:52 schrieb Jean-Marc Lasgouttes:

Le 06/04/2022 à 17:44, Wolfgang Engelmann a écrit :

And this is the output from the terminal starting lyx there:

lyx24x MEINLEBEN2020-B.lyx
Warning: 609: Format not supported.
Warning: Quitting.
Error: Document format failure


This is what I thought. It seems that you have a working recent lyx 
somewhere (the 609 version) and that now you try to read the file with 
an older version.


JMarc

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx not a readable Lyx document

[Jean-Marc Lasgouttes via lyx-users]

Le 31/03/2022 à 10:48, Wolfgang Engelmann via lyx-users a écrit :

I posted this already under
tmp/lyx not a readable file
(01March22)

The error message:

/tmp/lyx_tmpdir.MQUsZMBvAPQl/Buffer_convertLyXFormatwrdYvM.lyx is not a 
readable LyX document.


since quite a number of my older (March 22) lyx files are affected and I 
can't open them, I would very much appreciate if somebody could have a 
look at it.


I found 2 lyx files close to each other, one of which gives the error 
message above, the other one is alright. I could send both privately 
(because of the size and the content) to somebody for checking them.


I use lyx 2.4.dev under Debian.


Sorry for not answering earlier, I was busy at the time and then forgot.

Please send the two files to me.

JMarc
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

lyx not a readable Lyx document

[Wolfgang Engelmann via lyx-users]

I posted this already under
tmp/lyx not a readable file
(01March22)

The error message:

/tmp/lyx_tmpdir.MQUsZMBvAPQl/Buffer_convertLyXFormatwrdYvM.lyx is not a 
readable LyX document.


since quite a number of my older (March 22) lyx files are affected and I 
can't open them, I would very much appreciate if somebody could have a 
look at it.


I found 2 lyx files close to each other, one of which gives the error 
message above, the other one is alright. I could send both privately 
(because of the size and the content) to somebody for checking them.


I use lyx 2.4.dev under Debian.

Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[NANDI D.A.]

I think it was 1.6 or 1.7 at the start, but I have been constantly editing it 
with updated versions of LyX up to 2.0.x

David

Sent from my iPhone

> On 20 May 2014, at 19:37, "Richard Heck"  wrote:
> 
>> On 05/20/2014 09:52 AM, David Nandi wrote:
>> Richard Heck  comcast.net> writes:
>> 
>>>> On 04/23/2012 09:38 AM, John Enright wrote:
>>>> Since upgrading to 2.0.3, Many of my files will not open. I get an error
>> message
>>>> during the open operation saying:
>>>> 
>>>> C:\Users\myusername\AppData\Local\Temp\lyx_tmpdir.p10476
>>>> \Buffer_convertLyxFormat.h is not a readable LyX document.
>>>> 
>>>> The temp directory exits (as specified in the message); the temp file is
>>>> zero-bytes long.
>>>> 
>>>> - I'm running Win7 (x64). My MikTex is up to date. I've reinstalled LyX
>> several
>>>> times (including uninstalling it). No difference.
>>>> 
>> 
>>> Sounds like some sort of lyx2lyx conversion error. If you can run LyX
>>> from a terminal, you should get more error messages, though that won't
>>> solve the problem by itself. So, alternatively, try posting one of the
>>> problematic files here, or sending it to me privately, if you prefer,
>>> and we can try to figure it out.
>>> 
>>> Richard
>> 
>> I get the same problem after upgrading to LyX 2.0.7 (I'm not sure from which
>> version), when trying to open files that I had been using daily. I have
>> tried re-installing 2.0.7 as well as using version 1.6.10, but the same
>> error appears. What do you suggest, is there a way to access other LyX
>> versions?
> 
> What version of LyX were these files created in?
> 
> Richard
> 

Re: Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[Richard Heck]

On 05/20/2014 09:52 AM, David Nandi wrote:

Richard Heck  comcast.net> writes:


On 04/23/2012 09:38 AM, John Enright wrote:

Since upgrading to 2.0.3, Many of my files will not open. I get an error

message

during the open operation saying:

C:\Users\myusername\AppData\Local\Temp\lyx_tmpdir.p10476
\Buffer_convertLyxFormat.h is not a readable LyX document.

The temp directory exits (as specified in the message); the temp file is
zero-bytes long.

- I'm running Win7 (x64). My MikTex is up to date. I've reinstalled LyX

several

times (including uninstalling it). No difference.




Sounds like some sort of lyx2lyx conversion error. If you can run LyX
from a terminal, you should get more error messages, though that won't
solve the problem by itself. So, alternatively, try posting one of the
problematic files here, or sending it to me privately, if you prefer,
and we can try to figure it out.

Richard


I get the same problem after upgrading to LyX 2.0.7 (I'm not sure from which
version), when trying to open files that I had been using daily. I have
tried re-installing 2.0.7 as well as using version 1.6.10, but the same
error appears. What do you suggest, is there a way to access other LyX
versions?


What version of LyX were these files created in?

Richard

Re: Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[David Nandi]

Richard Heck  comcast.net> writes:

> 
> On 04/23/2012 09:38 AM, John Enright wrote:
> > Since upgrading to 2.0.3, Many of my files will not open. I get an error 
message
> > during the open operation saying:
> >
> > C:\Users\myusername\AppData\Local\Temp\lyx_tmpdir.p10476
> > \Buffer_convertLyxFormat.h is not a readable LyX document.
> >
> > The temp directory exits (as specified in the message); the temp file is
> > zero-bytes long.
> >
> > - I'm running Win7 (x64). My MikTex is up to date. I've reinstalled LyX 
several
> > times (including uninstalling it). No difference.
> >


> Sounds like some sort of lyx2lyx conversion error. If you can run LyX 
> from a terminal, you should get more error messages, though that won't 
> solve the problem by itself. So, alternatively, try posting one of the 
> problematic files here, or sending it to me privately, if you prefer, 
> and we can try to figure it out.
> 
> Richard


I get the same problem after upgrading to LyX 2.0.7 (I'm not sure from which 
version), when trying to open files that I had been using daily. I have 
tried re-installing 2.0.7 as well as using version 1.6.10, but the same 
error appears. What do you suggest, is there a way to access other LyX 
versions?

Thanks, David 

Re: "Not a readable lyx document"

[José Matos]

On 2012-11-25 16:53, David L. Johnson wrote:
> My students would testify that many of my notes are far, far more than
> 8-12 months old when I open and "revise" them for the current term,
> and this has never happened to me [except on very, very old files
> whose format is no longer supported directly by lyx]. 
>>

If you still have those, and the file content is not sensitive I would
appreciate to look in to them to guarantee lyx2lyx's motto that "if lyx
wrote it then lyx should read it". :-)

Regards,

-- 
José Matos

Re: "Not a readable lyx document"

[Graham Smith]

Thanks to everyone for the further comments, good to hear that it seems I
am unusual in having corrupt files.

Time Machine is, as Liviu says, a Mac solution and I share with Ubuntu and
occasionally Windows. Dropbox will retain files indefinitely, for an extra
fee, but I didn't know that SiderOak did it for their standard fee.

Certainly it looks as if I need to improve my backup procedures in some
way, but these few files with Lyx are the only times I have had this
problem.

Graham

Re: "Not a readable lyx document"

[Dr Eberhard Lisse]

What is wrong with Time Machine?

BTW, the DropBox people might be able to dig up a version from 8 months
or so back, if you are a paying client.

el


On 2012-11-25 21:17 , Graham Smith wrote:
> Liviu,
> 
> I have 100+Gb on Dropbox that I use, and it gives me version control for
> 30 days, which is good for falling back on a previous version, but the
> Dropbox version will have long been replaced by the corrupt version.
> This then syncs to a few computers in different locations
> 
> But, I do need a better long term backup, and a more flexible version
> control.
> 
> I also have a Spider Oak account, as it so happens.
> 
> Thanks,
> 
> Graham
> 

Re: "Not a readable lyx document"

[Dr Eberhard Lisse]

Never had a problem.

I exchange regularly between Ubuntu and the Mac and on and off with Windoze.

el

On 2012-11-25 17:29 , Liviu Andronic wrote:
> On Sun, Nov 25, 2012 at 4:20 PM, Graham Smith  wrote:
>> So far, I have never had occasion to edit lyx files directly, I was just
>>
> Then the question is whether LyX produces identical .lyx source files
> on different platforms. Perhaps other Mac OS X users could chip in.
> 
> Liviu
> 

Re: "Not a readable lyx document"

[Graham Smith]

Liviu,

I have 100+Gb on Dropbox that I use, and it gives me version control for 30
days, which is good for falling back on a previous version, but the Dropbox
version will have long been replaced by the corrupt version. This then
syncs to a few computers in different locations

But, I do need a better long term backup, and a more flexible version
control.

I also have a Spider Oak account, as it so happens.

Thanks,

Graham

Re: "Not a readable lyx document"

[Liviu Andronic]

On Sun, Nov 25, 2012 at 6:09 PM, Graham Smith  wrote:
> Hard drives have all recently had some form of hardware check run on them in
> the last few weeks, and this may in fact be the first file to go wrong with
> my current computer set up, so maybe its a legacy of a past hard drive.
>
For this very reason it is generally a good idea to keep (at least)
text files such as *.lyx under a version control system or, if you'd
like to minimize the overhead, some automatic backup system.

Dropbox seems to be most popular of the lot, and although reliable it
is not very flexible (and not privacy aware). SpiderOak is what
prefer, and although it has some rough edges here and there it usually
does its job well. Also it is more generous in terms of free storage
provided to users (see [1] for my referral link so that we both get 1
extra GB) and is privacy aware (you're uploading blocks of encrypted
data, with their staff technically unable to decrypt your personal
stuff).

My 00.02€
Liviu

[1] 
http://landroni.wordpress.com/2012/07/03/spideroak-generosity-making-an-offer-you-cant-refuse/

Re: "Not a readable lyx document"

[Graham Smith]

David,

>   My students would testify that many of my notes are far, far more than
> 8-12 months old when I open and "revise" them for the current term, and
> this has never happened to me [except on very, very old files whose format
> is no longer supported directly by lyx].
>
>
>  Thinking about it the computer that probably produced this file is no
> longer in use, but it wasn't corrupt when last used as I printed out the
> PDF from it, so it has become corrupt sitting on my hard drive.
>
> Well, your hard drive has probably begun to fail, corrupting random areas
> on the disk.  Although disk drives do seem more reliable than they used to
> be, it does still happen.
>

I think I am going to put it down to just being one of those things, for
now and see if it happens again. I'm not having any problems with other
files, and so far this year, only this file has been a problem. I keep a
note of the revisions I want to make from one year to the next, so I can
just ask students to annotate the hard copy. I don't have time to redo the
document.

Hard drives have all recently had some form of hardware check run on them
in the last few weeks, and this may in fact be the first file to go wrong
with my current computer set up, so maybe its a legacy of a past hard drive.

Thanks,

Graham

Re: "Not a readable lyx document"

[David L. Johnson]

On 11/25/2012 11:11 AM, Graham Smith wrote:


Richard,

 so I will just be more cautious in future.

This file is definitley corrupt. Here's the result of "hexdump -c
| head -n 25":


If you've had this problem more than once, you may want to think
about whether you have a hardware problem that is corrupting your
files.


It has happened occasionally before, maybe 3 or 4 times over the same 
number of years. It's difficult to track, as its always the same 
 situation lecture notes or a tutorial than has sat there for 8 to 12 
months untouched, and then I can't open it to revise for the current term.
My students would testify that many of my notes are far, far more than 
8-12 months old when I open and "revise" them for the current term, and 
this has never happened to me [except on very, very old files whose 
format is no longer supported directly by lyx].


Thinking about it the computer that probably produced this file is no 
longer in use, but it wasn't corrupt when last used as I printed out 
the PDF from it, so it has become corrupt sitting on my hard drive.
Well, your hard drive has probably begun to fail, corrupting random 
areas on the disk.  Although disk drives do seem more reliable than they 
used to be, it does still happen.


--

David L. Johnson

As far as the laws of mathematics refer to reality, they are not
certain, and as far as they are certain, they do not refer to reality.
-- Albert Einstein

Re: "Not a readable lyx document"

[Graham Smith]

Richard,

 so I will just be more cautious in future.
>>
>>  This file is definitley corrupt. Here's the result of "hexdump -c | head
> -n 25":
>
>
> If you've had this problem more than once, you may want to think about
> whether you have a hardware problem that is corrupting your files.


It has happened occasionally before, maybe 3 or 4 times over the same
number of years. It's difficult to track, as its always the same  situation
lecture notes or a tutorial than has sat there for 8 to 12 months
untouched, and then I can't open it to revise for the current term.

Thinking about it the computer that probably produced this file is no
longer in use, but it wasn't corrupt when last used as I printed out the
PDF from it, so it has become corrupt sitting on my hard drive.

I am unaware of any other problems, so I suspect I will just need to wait
and see.

Thanks,

Graham

Re: "Not a readable lyx document"

[Richard Heck]

On 11/25/2012 08:05 AM, Graham Smith wrote:

Liviu

That's odd. The first question that pops to mind: Do you use the
Document > Compressed option? Maybe this corrupts things.


What is also odd is that  I can open the file with no problem using a 
text editor on the Mac, indeed the file preview in the Mac file 
Manager (Pathfinder) reads it without any problems. BUT I have just 
tried on Ubuntu (open with text editor) , and it won't open.


I certainly haven't selected the compressed option, but this 
particular file is 7 months old, and I can't remember whether it 
originated on the Mac or Ubuntu or even the version of Lyx. I will 
check the compressed option in future.


However, it seems there is no obvious answer, so I will just be more 
cautious in future.


This file is definitley corrupt. Here's the result of "hexdump -c | head 
-n 25":


000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0 \0
*
0008050  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0   . \n   \
0008060   e   n   d   _   l   a   y   o   u   t  \n  \n   \   b e   g
0008070   i   n   _   l   a   y   o   u   t   S   t   a   n d   a
0008080   r   d  \n   A   d   d   i   t   i   o   n   a   l   l y
0008090   t   o   g   e   t   t   h   e   m   a p   t
00080a0   o   e   x   a   c   t   l   y   f   i   l l   t
00080b0   h   e   b   o   u   n   d   i   n   g   b   o x
00080c0   a   s   y   o   u   w   a   n   t  \n   i t   ,
00080d0   y   o   u   c   a   n   a   d   j   u   s t
00080e0   t   h   e   s   c   a   l   e   u   n   d   e r
00080f0   t   h   e   i   t   e   m   t   a   b   t o
0008100   t   h   e   r   i   g   h   t   ,   w   h   e n
0008110   t   h   e  \n   m   a   p   b   o   x   i s
0008120   s   e   l   e   c   t   e   d   .  \n   I   t w   i
0008130   l   l   p   r   o   b   a   b   l   y   b e   a
0008140   t   s   o   m   e   t   i   n   g   l   i   k e
0008150   7   0   0   0   ,   b   y   r   e   d   u   c i   n
0008160   g   a   n   d   i   n   c   r   e   a   s   i n   g
0008170   t   h   i   s  \n   n   u   m   b   e   r t   h
0008180   e   m   a   p   w   i   l   l   g   e t   l
0008190   a   r   g   e   r   o   r   s   m   a   l   l e   r
00081a0   .  \n   \   e   n   d   _   l   a   y   o   u   t  \n \n   \
00081b0   b   e   g   i   n   _   l   a   y   o   u   t   S t   a

As you see, the file begins with some huge number of zeros, and then 
starts up again in the middle of a LyX file, with "\end_layout", as 
Liviu noted. Most of the file has thus been zero'd out.


If you've had this problem more than once, you may want to think about 
whether you have a hardware problem that is corrupting your files.


Richard

Re: "Not a readable lyx document"

[Liviu Andronic]

On Sun, Nov 25, 2012 at 4:20 PM, Graham Smith  wrote:
> So far, I have never had occasion to edit lyx files directly, I was just
>
Then the question is whether LyX produces identical .lyx source files
on different platforms. Perhaps other Mac OS X users could chip in.

Liviu

Re: "Not a readable lyx document"

[Graham Smith]

Thanks Liviu

If you ever manually edit your .lyx files in a text editor, try to
> make sure that the result is accessible on both your platforms.


So far, I have never had occasion to edit lyx files directly, I was just
using  a text editor here, because I wanted to have a look at the file when
it wouldn't open in Lyx.

Cheers,

Graham

Re: "Not a readable lyx document"

[Liviu Andronic]

On Sun, Nov 25, 2012 at 2:05 PM, Graham Smith  wrote:
>> That's odd. The first question that pops to mind: Do you use the
>> Document > Compressed option? Maybe this corrupts things.
>
> What is also odd is that  I can open the file with no problem using a text
> editor on the Mac, indeed the file preview in the Mac file Manager
> (Pathfinder) reads it without any problems. BUT I have just tried on Ubuntu
> (open with text editor) , and it won't open.
>
Yes, it's rather strange. Geany complains as follows:
15:04:42: The file "/tmp/Phase1_Tutorial.lyx" does not look like a
text file or the file encoding is not supported.

Maybe it's an issue with the linebreaks which can differ from a
platform to another, but I'm surprised that an advanced editor as
Geany would trip on that.


> I certainly haven't selected the compressed option, but this particular file
> is 7 months old, and I can't remember whether it originated on the Mac or
> Ubuntu or even the version of Lyx. I will check the compressed option in
> future.
>
> However, it seems there is no obvious answer, so I will just be more
> cautious in future.
>
If you ever manually edit your .lyx files in a text editor, try to
make sure that the result is accessible on both your platforms.

Liviu

Re: "Not a readable lyx document"

[Graham Smith]

Liviu


> That's odd. The first question that pops to mind: Do you use the
> Document > Compressed option? Maybe this corrupts things.
>

What is also odd is that  I can open the file with no problem using a text
editor on the Mac, indeed the file preview in the Mac file Manager
(Pathfinder) reads it without any problems. BUT I have just tried on Ubuntu
(open with text editor) , and it won't open.

I certainly haven't selected the compressed option, but this particular
file is 7 months old, and I can't remember whether it originated on the Mac
or Ubuntu or even the version of Lyx. I will check the compressed option in
future.

However, it seems there is no obvious answer, so I will just be more
cautious in future.

Thanks,

Graham

Re: "Not a readable lyx document"

[Liviu Andronic]

On Sun, Nov 25, 2012 at 11:22 AM, Graham Smith  wrote:
> This happens to me occasionally, when I try and open an old lyx file
> (usually about 11 months old as its always revising lecture/tutorials for
> the current year).
>
I cannot open it either, with latest trunk. And this is odd, and
shouldn't be happening. The file is somehow corrupted, as I cannot
open it in a plain text editor to see the markup contents. If I do
this:
root@liv-laptop:/tmp# less Phase1_Tutorial.lyx
"Phase1_Tutorial.lyx" may be a binary file.  See it anyway?


and this ends up showing a binary blob. If I do this however:
root@liv-laptop:/tmp# head Phase1_Tutorial.lyx
.
\end_layout

\begin_layout Standard
Additionally to get the map to exactly fill the bounding box as you want
 it, you can adjust the scale under the item tab to the right, when the
 map box is selected.
 It will probably be at someting like 7000, by reducing and increasing this
 number the map will get larger or smaller.
\end_layout


I see the text contents of the file. Using 'cat' will yield something similar.

That's odd. The first question that pops to mind: Do you use the
Document > Compressed option? Maybe this corrupts things.

Liviu

Re: Re: Re: Re: Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[Kornel Benko]

Am Mittwoch, 25. April 2012 um 01:10:17, schrieb Pavel Sanda 
> Kornel Benko wrote:
> > Am Dienstag, 24. April 2012 um 10:43:23, schrieb Pavel Sanda 
> > > Kornel Benko wrote:
> > > > I experienced something similar when converting some files created on 
> > > > windows.
> > > > It turned out, that the last line ended with "\end_document" but was 
> > > > not terminated by eol.
> > > > Inserting a new line in such lyx-file with a text editor helped.
> > > 
> > > Can you send example? These sounds like critical bugs.
> > > Pavel
> > 
> > No, I cannot create such files anymore. But it is easy to fake it. Just 
> > remove the trailing line feed
> > of a file created by 2.0.x and try to read with 2.1.x.
> > (Opening this file with 2.0.x will work, since no conversion needed)
> 
> I tried and didn't get the error which was reported by John
> (instead I correctly see  Buffer .. ended unexpectedly, which means that it 
> is probably corrupted.)
> Do you have reproducible behaviour how you get such eoln-missing files?
> Pavel

Sorry, no. It occurred as I wanted to edit some of my old lyx files. I changed 
them in the meantime.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Re: Re: Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[Pavel Sanda]

Kornel Benko wrote:
> Am Dienstag, 24. April 2012 um 10:43:23, schrieb Pavel Sanda 
> > Kornel Benko wrote:
> > > I experienced something similar when converting some files created on 
> > > windows.
> > > It turned out, that the last line ended with "\end_document" but was not 
> > > terminated by eol.
> > > Inserting a new line in such lyx-file with a text editor helped.
> > 
> > Can you send example? These sounds like critical bugs.
> > Pavel
> 
> No, I cannot create such files anymore. But it is easy to fake it. Just 
> remove the trailing line feed
> of a file created by 2.0.x and try to read with 2.1.x.
> (Opening this file with 2.0.x will work, since no conversion needed)

I tried and didn't get the error which was reported by John
(instead I correctly see  Buffer .. ended unexpectedly, which means that it is 
probably corrupted.)
Do you have reproducible behaviour how you get such eoln-missing files?
Pavel

Re: Re: Re: Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[Indrek Tuula]

Hi,


I had similar (i can't remember exact error message but it was it was
closely related) error around of two weeks ago but instead of upgrading
it occurred after unexpected power loss.

Following steps help me to use corrupted files again:

   1. Locate working directory
   2. Instead of your main project file e.g. filename.lyx locate and open
   filename.lyx~ with Lyx (you have to point location of Lyx binary,
   alternatively you can open this file via Lyx file menu > open but on this
   case first you should insert *.* as file name to make all file types
   visible for Lyx)
   3. Save result as new project e.g new.lyx (it is just good practice to
   keep recovery and original files separated)
   4. After manual check of content of file you can rename new.lyx back to
   filename.lyx

I am using Win 7 x 64 Lyx 2.0.3

Br,
Indrek

On 24 April 2012 14:02, Kornel Benko  wrote:

> Am Dienstag, 24. April 2012 um 10:43:23, schrieb Pavel Sanda <
> sa...@lyx.org>
> > Kornel Benko wrote:
> > > I experienced something similar when converting some files created on
> windows.
> > > It turned out, that the last line ended with "\end_document" but was
> not terminated by eol.
> > > Inserting a new line in such lyx-file with a text editor helped.
> >
> > Can you send example? These sounds like critical bugs.
> > Pavel
>
> No, I cannot create such files anymore. But it is easy to fake it. Just
> remove the trailing line feed
> of a file created by 2.0.x and try to read with 2.1.x.
> (Opening this file with 2.0.x will work, since no conversion needed)
>
>Kornel

Re: Re: Re: Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[Kornel Benko]

Am Dienstag, 24. April 2012 um 10:43:23, schrieb Pavel Sanda 
> Kornel Benko wrote:
> > I experienced something similar when converting some files created on 
> > windows.
> > It turned out, that the last line ended with "\end_document" but was not 
> > terminated by eol.
> > Inserting a new line in such lyx-file with a text editor helped.
> 
> Can you send example? These sounds like critical bugs.
> Pavel

No, I cannot create such files anymore. But it is easy to fake it. Just remove 
the trailing line feed
of a file created by 2.0.x and try to read with 2.1.x.
(Opening this file with 2.0.x will work, since no conversion needed)

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Re: Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[Pavel Sanda]

Kornel Benko wrote:
> I experienced something similar when converting some files created on windows.
> It turned out, that the last line ended with "\end_document" but was not 
> terminated by eol.
> Inserting a new line in such lyx-file with a text editor helped.

Can you send example? These sounds like critical bugs.
Pavel

Re: Re: Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[Kornel Benko]

Am Montag, 23. April 2012 um 09:54:05, schrieb Richard Heck 
> On 04/23/2012 09:38 AM, John Enright wrote:
> > Since upgrading to 2.0.3, Many of my files will not open. I get an error 
> > message
> > during the open operation saying:
> >
> > C:\Users\myusername\AppData\Local\Temp\lyx_tmpdir.p10476
> > \Buffer_convertLyxFormat.h is not a readable LyX document.
> >
> > The temp directory exits (as specified in the message); the temp file is
> > zero-bytes long.
> >
> > - I'm running Win7 (x64). My MikTex is up to date. I've reinstalled LyX 
> > several
> > times (including uninstalling it). No difference.
> >
> > - Some old files will open. But many will not. Not sure of what is special 
> > about
> > the affected files. Perhaps some particular floats, but I can't seem to
> > replicate the problem with a new file.
> >
> > - I can create and reopen a completely new file.
> >
> > - The affected files are not corrupted, since they open just fine in LyX 
> > 1.6.X
> > that I still had installed.
> >
> > Any thoughts?
> >
> Sounds like some sort of lyx2lyx conversion error. If you can run LyX 
> from a terminal, you should get more error messages, though that won't 
> solve the problem by itself. So, alternatively, try posting one of the 
> problematic files here, or sending it to me privately, if you prefer, 
> and we can try to figure it out.
> 
> Richard

I experienced something similar when converting some files created on windows.
It turned out, that the last line ended with "\end_document" but was not 
terminated by eol.
Inserting a new line in such lyx-file with a text editor helped.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[John Enright]

On 23/04/2012 9:54 AM, Richard Heck wrote:

On 04/23/2012 09:38 AM, John Enright wrote:

Since upgrading to 2.0.3, Many of my files will not open. I get an
error message
during the open operation saying:

C:\Users\myusername\AppData\Local\Temp\lyx_tmpdir.p10476
\Buffer_convertLyxFormat.h is not a readable LyX document.



Sounds like some sort of lyx2lyx conversion error. If you can run LyX
from a terminal, you should get more error messages, though that won't
solve the problem by itself. So, alternatively, try posting one of the
problematic files here, or sending it to me privately, if you prefer,
and we can try to figure it out.

Richard




Is there some magic to get the debug output from the command line? I run:

lyx -dbg

or

lyx -dbg graphics

and get no additional output. Is this logged to a file somewhere?

BTW, I have verified that I can make the problem disappear by rolling 
back to 2.0.2 (well, uninstalling 2.0.3, and then installing 2.0.2).


John

Re: Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[Richard Heck]

On 04/23/2012 09:38 AM, John Enright wrote:

Since upgrading to 2.0.3, Many of my files will not open. I get an error message
during the open operation saying:

C:\Users\myusername\AppData\Local\Temp\lyx_tmpdir.p10476
\Buffer_convertLyxFormat.h is not a readable LyX document.

The temp directory exits (as specified in the message); the temp file is
zero-bytes long.

- I'm running Win7 (x64). My MikTex is up to date. I've reinstalled LyX several
times (including uninstalling it). No difference.

- Some old files will open. But many will not. Not sure of what is special about
the affected files. Perhaps some particular floats, but I can't seem to
replicate the problem with a new file.

- I can create and reopen a completely new file.

- The affected files are not corrupted, since they open just fine in LyX 1.6.X
that I still had installed.

Any thoughts?

Sounds like some sort of lyx2lyx conversion error. If you can run LyX 
from a terminal, you should get more error messages, though that won't 
solve the problem by itself. So, alternatively, try posting one of the 
problematic files here, or sending it to me privately, if you prefer, 
and we can try to figure it out.


Richard

Can't open files in 2.0.3 (Buffer_convertLyxFormat.hXXXX is not a readable Lyx Document)

[John Enright]

Since upgrading to 2.0.3, Many of my files will not open. I get an error message
during the open operation saying:

C:\Users\myusername\AppData\Local\Temp\lyx_tmpdir.p10476
\Buffer_convertLyxFormat.h is not a readable LyX document.

The temp directory exits (as specified in the message); the temp file is
zero-bytes long.

- I'm running Win7 (x64). My MikTex is up to date. I've reinstalled LyX several
times (including uninstalling it). No difference. 

- Some old files will open. But many will not. Not sure of what is special about
the affected files. Perhaps some particular floats, but I can't seem to
replicate the problem with a new file.

- I can create and reopen a completely new file. 

- The affected files are not corrupted, since they open just fine in LyX 1.6.X
that I still had installed. 

Any thoughts?

Cheers,

John

moderncv.lyx "not a readable lyx document"

[Heaven Hodges]

moderncv.lyx "not a readable lyx document"

Postby StarKid on Sun Nov 13, 2011 12:56 am
I have LyX 2.0.0 on Ubuntu Linux. Attempting to open the moderncv template gives
the error in the post subject heading. I've used this template once before, but
it was months ago and I don't know what could have changed. Other templates open
up fine aside from some warnings about not being able to compile due to missing
.cls files. What could be wrong?