Re: Fwd: Re: no modules availables

[José Abílio Matos]

On Saturday, 15 August 2020 15.26.27 WEST Jose Ramom Flores das Seixas wrote:
> You got it right, as I had several old modules from Editorium of type:
> 
> Non-ISO extended-ASCII text, with CRLF line terminators
> 
> I have converted them to
> 
>  UTF-8 Unicode text
> 
> and now configure.py recognizes all the modules.
> 
> On the other hand, executing  Reconfigure inside LyX no longer gives an
> error message.

Thank you for reporting this problem.

For reference this is another manifestation of
https://www.lyx.org/trac/ticket/11736

In this bug we fixed the corresponding issue with layout files.

I have committed a fix for this issue in the development branch (to be lyx 
2.4.0) and soon it will also committed to the stable branch (for 2.3.6).

Regards,
-- 
José Abílio


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

Re: Fwd: Re: no modules availables

[José Abílio Matos]

On Saturday, 15 August 2020 16.44.37 WEST Richard Kimberly Heck wrote:
> Do you think that is worth doing?

If it can be done easily then why not? :-)
Basically that and people asking for it. :-)

The configure code has annoyed me for a long time and at the next development 
cycle I would like to refactor it so that there is specific platform code. 
Then flatpack code could go there.

> It's too bad there's no consistent
> translation from command names to flatpack commands.

The solution would be to create an associative array with the program name and 
the url (or whatever it is called) name. That would be an static table.

We could also go the next stage and use a dynamic table built asking flatpack 
what are the packages available.

> Riki

-- 
José Abílio


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

Re: Fwd: Re: no modules availables

[Richard Kimberly Heck]

On 8/15/20 10:47 AM, José Abílio Matos wrote:
>
> On Saturday, 15 August 2020 15.26.27 WEST Jose Ramom Flores das Seixas
> wrote:
>
> > The problem with Inkscape was that I had installed it as a flatpak
> package.
>
> > I've removed it and installed the deb package and now all seem OK.
>
> >
>
> > Cheers
>
> >
>
> > Ramom
>
>  
>
> Yes, that is the problem. :-)
>
>  
>
> The issue is that to call inkscape from the command line the right way
> would be:
>
>  
>
> flatpack run org.inkscape.Inkscape
>
>  
>
> while we simply test
>
>  
>
> inkscape
>
>  
>
>  
>
> FWIW the same happens for other flatpack packages. At moment we do not
> test for flatpacks.
>
Do you think that is worth doing? It's too bad there's no consistent
translation from command names to flatpack commands.

Riki


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

Re: Fwd: Re: no modules availables

[José Abílio Matos]

On Saturday, 15 August 2020 15.26.27 WEST Jose Ramom Flores das Seixas wrote:
> The problem with Inkscape was that I had installed it as a flatpak package.
> I've removed it and installed the deb package and now all seem OK.
> 
> Cheers
> 
> Ramom

Yes, that is the problem. :-)

The issue is that to call inkscape from the command line the right way would 
be:

flatpack run org.inkscape.Inkscape

while we simply test

inkscape


FWIW the same happens for other flatpack packages. At moment we do not test 
for flatpacks.

-- 
José Abílio-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Fwd: Re: no modules availables

[Jose Ramom Flores das Seixas]

Às 16:23 de 15/08/20, Jose Ramom Flores das Seixas escreveu:


 Mensagem reencaminhada 
Assunto:Re: no modules availables
Data:   Sat, 15 Aug 2020 15:56:29 +0200
De: 	Jose Ramom Flores das Seixas 


Para:   José Abílio Matos 



Às 23:37 de 14/08/20, José Abílio Matos escreveu:


On Friday, 14 August 2020 16.28.22 WEST Jose Ramom Flores das Seixas 
wrote:


> Hi:

>

> I take a long time without using LyX, but my package manager has been

> updating lyx when new versions come out. Nowadays, I have installed 
version


> 2.3.5.2 (OS: Ubuntu 18.04).

>

> Today I tried to edit a file, with lyxformat 544, but LyX tells me 
a module


> is missing. Looking at the module dialogue I found that no module is

> available.

>

> I've checked that the standard module files are in 
/usr/share/lyx/layouts,


> and besides them I have some other modules in ~/.lyx/layouts.

>

> When I run LyX from a terminal I can notice the following error:

>

> UnicodeDecodeError: 'utf8' codec can't decode byte 0xa9 in position 
395:


> invalid start byte support/Systemcall.cpp (276): Systemcall: 
'python -tt


> "/usr/share/lyx/configure.py" --binary-dir="/usr/bin/"' finished 
with exit


> code 1

>

> LyX: Done!

From experience this means that you have a old layout file or module 
that have an encoding that is not utf-8. In your case I assume that 
the culprit is either in latin1 or latin9 (the difference between 
those is the presence/absence of the euro sign).


Also I thought that we had fixed all the remainder errors like this 
in 2.3.5.2


So my suggestion is to go to your personal lyx directory and check 
the encoding of file. By default in linux the location of the 
personal directory is ~/.lyx. You can see this in LyX using the menu: 
Help->About LyX->Version and see the User dir entry there.


Using the shell in my case I have:

$ cd ~/.lyx

$ file bind/*

bind/user.bind: ASCII text

My suggestion is to check the layouts directory that could be the 
likely source of the problem:


$ file layouts/*

You got it right, as I had several old modules from Editorium 
 of type:


Non-ISO extended-ASCII text, with CRLF line terminators

I have converted them to

UTF-8 Unicode text

and now configure.py recognizes all the modules.

On the other hand, executing *Reconfigure* inside LyX no longer gives 
an error message.


However, it still does not recognize Inkscape, even though it is 
installed. So in the log file the following is listed:


INFO: checking for a SVG -> PDFTeX converter...INFO: +checking for
"inkscape"... no

The problem with Inkscape was that I had installed it as a flatpak 
package. I've removed it and installed the deb package and now all seem OK.


Cheers

Ramom

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

Fwd: Re: no modules availables

[Jose Ramom Flores das Seixas]

 Mensagem reencaminhada 
Assunto:Re: no modules availables
Data:   Sat, 15 Aug 2020 15:56:29 +0200
De: Jose Ramom Flores das Seixas 
Para:   José Abílio Matos 



Às 23:37 de 14/08/20, José Abílio Matos escreveu:


On Friday, 14 August 2020 16.28.22 WEST Jose Ramom Flores das Seixas 
wrote:


> Hi:

>

> I take a long time without using LyX, but my package manager has been

> updating lyx when new versions come out. Nowadays, I have installed 
version


> 2.3.5.2 (OS: Ubuntu 18.04).

>

> Today I tried to edit a file, with lyxformat 544, but LyX tells me a 
module


> is missing. Looking at the module dialogue I found that no module is

> available.

>

> I've checked that the standard module files are in 
/usr/share/lyx/layouts,


> and besides them I have some other modules in ~/.lyx/layouts.

>

> When I run LyX from a terminal I can notice the following error:

>

> UnicodeDecodeError: 'utf8' codec can't decode byte 0xa9 in position 395:

> invalid start byte support/Systemcall.cpp (276): Systemcall: 'python -tt

> "/usr/share/lyx/configure.py" --binary-dir="/usr/bin/"' finished 
with exit


> code 1

>

> LyX: Done!

From experience this means that you have a old layout file or module 
that have an encoding that is not utf-8. In your case I assume that 
the culprit is either in latin1 or latin9 (the difference between 
those is the presence/absence of the euro sign).


Also I thought that we had fixed all the remainder errors like this in 
2.3.5.2


So my suggestion is to go to your personal lyx directory and check the 
encoding of file. By default in linux the location of the personal 
directory is ~/.lyx. You can see this in LyX using the menu: 
Help->About LyX->Version and see the User dir entry there.


Using the shell in my case I have:

$ cd ~/.lyx

$ file bind/*

bind/user.bind: ASCII text

My suggestion is to check the layouts directory that could be the 
likely source of the problem:


$ file layouts/*

You got it right, as I had several old modules from Editorium 
 of type:


   Non-ISO extended-ASCII text, with CRLF line terminators

I have converted them to

   UTF-8 Unicode text

and now configure.py recognizes all the modules.

On the other hand, executing *Reconfigure* inside LyX no longer gives an 
error message.


However, it still does not recognize Inkscape, even though it is 
installed. So in the log file the following is listed:


   INFO: checking for a SVG -> PDFTeX converter...INFO: +checking for
   "inkscape"... no

Thanks you very much

Ramom

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