Re: lyx-2.3.0 and lyx2lyx

2018-02-01 Thread Wolfgang Engelmann

Am 01.02.2018 um 15:33 schrieb Wolfgang Engelmann:

Hallo,
I have several lyx files made under lyx-2.3.0beta1, but decided to use 
lyx-2.3.0.
I moved the lyx2lyx folder of the beta1 folder to my 2.3.0, but did 
not find in the lyx help books a description how to use it. Could 
somebody point to a place where to find a description?

Thanks,
Wolfgang
I have reinstalled lyx-2.3.0beta1 parallel to lyx-2-3-0 and use it to 
export my files for it (and to test the version). But would still like 
to know how to use lyx2lyx, although its not urgent anymore.

Wolfgang


Re: Problem: version control suddenly no longer works in LyX 2.2 and 2.3rc1

2018-02-01 Thread Pavel Sanda
Busch, Andreas wrote:
> I use GNU RCS 5.9.0 which appears to be the most recent, on a Mac with High 
> Sierra (10.13.2) and LyX 2.2. Updating to LyX 2.3rc1 made no difference. I am 
> not sure whether the last successful use of rcs with LyX predates upgrading 
> to High Sierra, otherwise there were no changes to my setup.
> 
> Having checked the mailing list archive, I find no recent discussion of 
> problems around rcs. If anyone has an idea where the cause of the error may 
> be or any suggestions what else I should try I'd be very grateful!

First idea: change of username (rcs lock is saved under your login name).

Then looking at debug would be helpful:
1. View->Message Pane
2. Settings panel->Selected & "lyxvc - Version control"
3. Switch back to Output panel
4. run your erring command and check (post here) the message.

You can also play with the commands after "doVCCommandCall:"
msg on your own to check what is going on if you know how
to work with terminal/rcs.

Pavel


lyx-2.3.0 and lyx2lyx

2018-02-01 Thread Wolfgang Engelmann

Hallo,
I have several lyx files made under lyx-2.3.0beta1, but decided to use 
lyx-2.3.0.
I moved the lyx2lyx folder of the beta1 folder to my 2.3.0, but did not 
find in the lyx help books a description how to use it. Could somebody 
point to a place where to find a description?

Thanks,
Wolfgang


Re: LyX version 2.3.0rc2 available

2018-02-01 Thread emile lunardon
LyX for Windows offers incomplete support for non-TeX fonts. This is the
case, for example, of the Gyre Schola font, which although proposed by
Miktex 2.9 , is unknown to LyX 2.3 RC2 (this is not the case of LyX 2.3
compiled under Linux Ubuntu 16.04).

2018-01-31 7:36 GMT+01:00 Scott Kostyshak :

> Public release of LyX version 2.3.0rc2
> 
>
> We are proud to announce the second public release candidate of the new
> LyX 2.3
> series. This pre-release is meant for testing and should not be used for
> serious work. For curious users who would like to test in order to help
> catch
> bugs before the 2.3.0 release, please back up all of your documents and be
> prepared for the worst to happen. Most users (who desire a stable LyX
> version)
> should not use this pre-release.
>
> The 2.3 series has a rich set of new features compared to the current
> stable
> series. An overview of the new features can be found here:
>
>   https://wiki.lyx.org/LyX/NewInLyX23
>
> You can download LyX 2.3.0rc2 from ftp://ftp.lyx.org/pub/lyx/devel/.
>
> We appreciate your help in testing this pre-release!
>
> If a file from an earlier version of LyX is opened *and saved* with
> any version of 2.3.x, then the original file will automatically be
> backed up. The backup file will be found in the backup directory, if one
> is set under Tools> Preferences> Paths, or else in the same folder as
> the original file, if no backup directory is set. The filename of the
> backup file will be:
> ORIGNAME-lyxformat-NUM.lyx~
> where NUM is the LyX format number of the original file. In the case of
> 2.2.x file, this will be 508, but in the case of older files it will be
> different.
>
> The file lib/RELEASE-NOTES lists some known issues and problems compared
> to the current stable releases (LyX 2.2.x). We strongly recommend that
> packagers of LyX on various platforms and distributions read this file.
>
> As with any major release, this one comes with a lot of new features but
> also some bugs. If you think you have found a bug in LyX 2.3.0rc2, either
> email the LyX developers' mailing list (lyx-devel at lists.lyx.org),
> or open a bug report at https://www.lyx.org/trac/wiki/BugTrackerHome.
> Please specify if the behavior you are reporting is different from behavior
> in a previous LyX version.
>
> If you have trouble using LyX or have a question, consult the
> documentation that comes with LyX (under Help) and the LyX wiki, which you
> will find at https://wiki.lyx.org/. You can also send email to the LyX
> users'
> list (lyx-users at lists.lyx.org).
>
> The LyX team.
> https://www.lyx.org
>
>


lyx-2.3.0 New thread: lyx-2.3.0 error after make. SOLVED

2018-02-01 Thread Wolfgang Engelmann

After compiling and make I started lyx with
src/lyx
I got an error concerning the configuration file.
However, after removing the .lyx file, Lyx started ok. Glad it did.
Wolfgang
#
LyX: Unknown tag `\jbibtex_alternatives' [around line 458 of file 
~/.lyx/lyxrc.defaults current token: '\jbibtex_alternatives' context: '']
LyX: Unknown tag `\jbibtex_alternatives' [around line 459 of file 
~/.lyx/lyxrc.defaults current token: '\jbibtex_alternatives' context: '']
LyX: Unknown tag `\jbibtex_alternatives' [around line 460 of file 
~/.lyx/lyxrc.defaults current token: '\jbibtex_alternatives' context: '']
LyX: Unknown tag `\jbibtex_alternatives' [around line 461 of file 
~/.lyx/lyxrc.defaults current token: '\jbibtex_alternatives' context: '']
LyX: Unknown tag `\pygmentize_command' [around line 469 of file 
~/.lyx/lyxrc.defaults current token: '\pygmentize_command' context: '']

Warning: Die Konfigurationsdatei konnte nicht gelesen werden

Fehler beim Lesen der Konfigurationsdatei
preferences.
Bitte prüfen Sie Ihre Installation.
we@wolfgang-Mr-Whisper-Ultra-SSD-II:~/lyx-2.2.3$ src/lyx
LyX: Unknown tag `\jbibtex_alternatives' [around line 458 of file 
~/.lyx/lyxrc.defaults current token: '\jbibtex_alternatives' context: '']
LyX: Unknown tag `\jbibtex_alternatives' [around line 459 of file 
~/.lyx/lyxrc.defaults current token: '\jbibtex_alternatives' context: '']
LyX: Unknown tag `\jbibtex_alternatives' [around line 460 of file 
~/.lyx/lyxrc.defaults current token: '\jbibtex_alternatives' context: '']
LyX: Unknown tag `\jbibtex_alternatives' [around line 461 of file 
~/.lyx/lyxrc.defaults current token: '\jbibtex_alternatives' context: '']
LyX: Unknown tag `\pygmentize_command' [around line 469 of file 
~/.lyx/lyxrc.defaults current token: '\pygmentize_command' context: '']

Warning: Die Konfigurationsdatei konnte nicht gelesen werden

Fehler beim Lesen der Konfigurationsdatei
preferences.
Bitte prüfen Sie Ihre Installation.
###





Re: lyx-2.3.1beta-1 finished > New thread: lyx-2.3.0 error after make

2018-02-01 Thread Wolfgang Engelmann



Am 01.02.2018 um 13:27 schrieb Kornel Benko:

Am Donnerstag, 1. Februar 2018 12:56:48 CET schrieb Wolfgang Engelmann
:

Am 01.02.2018 um 11:49 schrieb Kornel Benko:

Am Donnerstag, 1. Februar 2018 11:21:26 CET schrieb Wolfgang Engelmann

:

Am 01.02.2018 um 10:04 schrieb Kornel Benko:

Am Donnerstag, 1. Februar 2018 09:39:11 CET schrieb Wolfgang Engelmann

:

Am 01.02.2018 um 09:24 schrieb Kornel Benko:

Am Donnerstag, 1. Februar 2018 09:07:50 CET schrieb Wolfgang Engelmann

:

Am 31.01.2018 um 18:23 schrieb Joel Kulesza:

On Wed, Jan 31, 2018 at 9:11 AM, Uwe Stöhr > wrote:
Am 31.01.2018 um 10:31 schrieb Wolfgang Engelmann:
2- How do I use the tar.xz.sig file in respect to the
tar.xz?

This is the signature file to check if the file you

downloaded
was
not modified.

Uwe described what the file is, but how it is used is summarized
here:
http://www.lyx.org/Download#toc11


- Joel

Using the instruction given and after installing xz-utils

sudo gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D

gives me

gpg: Schlüssel DE7A44FAC7FB382D: Öffentlicher Schlüssel "LyX Release
Manager (Signing LyX tarballs and binaries) "
importiert
gpg: keine ultimativ vertrauenswürdigen Schlüssel gefunden
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg:  importiert: 1
(open key, no ultimative reliable key found, number of used keys )

Is this to be expected?
Wolfgang

Yes, and you should _not_ use 'sudo' here.

Kornel

Thanks, Kornel,

I tried it first without sudo and got

gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
gpg: lookup_hashtable failed: Unbekannter Systemfehler
/unknown system error/
gpg: trustdb: searching trust record failed: Unbekannter Systemfehler
gpg: Fehler: Die Vertrauensdatenbank ist fehlerhaft
/trusting databank erraneous/
gpg: Sie können versuchen die Vertrauensdatenbank durch folgende
Befehle
wiederherzustellen:
gpg:   cd ~/.gnupg
gpg:   gpg --export-ownertrust > otrust.tmp
gpg:   rm trustdb.gpg
gpg:   gpg --import-ownertrust < otrust.tmp
gpg: Falls dies nicht funktioniert, sehen Sie bitte im Handbuch nach
/if not working, check manual

after the wrong sudo I tried again without sudo:
/~$ gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
gpg: Empfangen vom Schlüsselserver fehlgeschlagen: Keine Daten

Maybe some data not readable by you.


/receiving of keyserver failed: No data

Should I have first canceled my wrong attempt to use sudo, and how
would
I do that?

Wolfgang
/

I would first check that all data in ~/.gnupg/ belongs to me.

yes, they do


And _never_ use
sudo for gpg.

now I know. Thanks


To check if a file 'fxxx' and the signature are in sync:
# gpg --verify fxxx.sig fxxx

To import a public key I would use a gui like  e.g. seahorse.

I have installed seahorse and tried it. But I need a hint.
I have a folder
lyx-2-3-new
which contains the
.tar.xz and the tar.xz.sig
Seahorse does not seem to recognize the content of the tar.xz stuff.
Do I have to extract the .tar.xz and the tar.xz.sig first, move the sig
into the folder with the extracted stuff and than run it?
Sorry for these probably naive questions, but I am in the 80s and it
takes all its time.
Thanks for your patience
Wolfgang

# seahorse

Entfernt->Entfernte Schlüssel suchen...->Suche nach: sanda@lyx

Suchort: 
hkp://keyserver.ubuntu.com:11371

click on the entry with 'Signing LyX tarballs and binaries'
click on '+ Importieren
leave the dialog
goto GnuPG-Schlüssel
left click on this new key ->Eigenschaften->Vertrauen
click on 'Vertrauen in diesen Schlüssel'
close dialog

You should be done

Kornel

I guess, you meant with # seahorse
run as superuser.

PLEASE NO
Never as superuser, if you are doing something private.


The terminal from which I ran it, tells
# seahorse
(seahorse:32621): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion
'G_IS_DBUS_CONNECTION (connection)' failed
(seahorse:32621): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner:
assertion 'G_IS_DBUS_PROXY (proxy)' failed
(seahorse:32621): seahorse-WARNING **: gkr-backend.vala:90: couldn't
connect to secret service: Verbindung ist geschlossen

Might have to do with your

To check if a file 'fxxx' and the signature are in sync:
# gpg --verify fxxx.sig fxxx
?? Wolfgang
Thanks all who helped me. I gave up with the signature and compiled the 
lyx2.3.0 version.

I got an error after make, see New thread: lyx-2.3.0 error after make
Wolfgang



Re: lyx-2.3.1beta-1

2018-02-01 Thread Kornel Benko
Am Donnerstag, 1. Februar 2018 12:56:48 CET schrieb Wolfgang Engelmann 
:
> Am 01.02.2018 um 11:49 schrieb Kornel Benko:
> > Am Donnerstag, 1. Februar 2018 11:21:26 CET schrieb Wolfgang Engelmann
> > 
> > :
> >> Am 01.02.2018 um 10:04 schrieb Kornel Benko:
> >>> Am Donnerstag, 1. Februar 2018 09:39:11 CET schrieb Wolfgang Engelmann
> >>> 
> >>> :
>  Am 01.02.2018 um 09:24 schrieb Kornel Benko:
> > Am Donnerstag, 1. Februar 2018 09:07:50 CET schrieb Wolfgang Engelmann
> > 
> > :
> >> Am 31.01.2018 um 18:23 schrieb Joel Kulesza:
> >>> On Wed, Jan 31, 2018 at 9:11 AM, Uwe Stöhr  >>> 
> >>> > wrote:
> >>>Am 31.01.2018 um 10:31 schrieb Wolfgang Engelmann:
> >>>2- How do I use the tar.xz.sig file in respect to the
> >>>tar.xz?
> >>>
> >>>This is the signature file to check if the file you
> >>>downloaded
> >>>was
> >>>not modified.
> >>> 
> >>> Uwe described what the file is, but how it is used is summarized
> >>> here:
> >>> http://www.lyx.org/Download#toc11
> >>> 
> >>> 
> >>> - Joel
> >> 
> >> Using the instruction given and after installing xz-utils
> >> 
> >> sudo gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
> >> 
> >> gives me
> >> 
> >> gpg: Schlüssel DE7A44FAC7FB382D: Öffentlicher Schlüssel "LyX Release
> >> Manager (Signing LyX tarballs and binaries) "
> >> importiert
> >> gpg: keine ultimativ vertrauenswürdigen Schlüssel gefunden
> >> gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
> >> gpg:  importiert: 1
> >> (open key, no ultimative reliable key found, number of used keys )
> >> 
> >> Is this to be expected?
> >> Wolfgang
> > 
> > Yes, and you should _not_ use 'sudo' here.
> > 
> > Kornel
>  
>  Thanks, Kornel,
>  
>  I tried it first without sudo and got
>  
>  gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
>  gpg: lookup_hashtable failed: Unbekannter Systemfehler
>  /unknown system error/
>  gpg: trustdb: searching trust record failed: Unbekannter Systemfehler
>  gpg: Fehler: Die Vertrauensdatenbank ist fehlerhaft
>  /trusting databank erraneous/
>  gpg: Sie können versuchen die Vertrauensdatenbank durch folgende
>  Befehle
>  wiederherzustellen:
>  gpg:   cd ~/.gnupg
>  gpg:   gpg --export-ownertrust > otrust.tmp
>  gpg:   rm trustdb.gpg
>  gpg:   gpg --import-ownertrust < otrust.tmp
>  gpg: Falls dies nicht funktioniert, sehen Sie bitte im Handbuch nach
>  /if not working, check manual
>  
>  after the wrong sudo I tried again without sudo:
>  /~$ gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
>  gpg: Empfangen vom Schlüsselserver fehlgeschlagen: Keine Daten
> >>> 
> >>> Maybe some data not readable by you.
> >>> 
>  /receiving of keyserver failed: No data
>  
>  Should I have first canceled my wrong attempt to use sudo, and how
>  would
>  I do that?
>  
>  Wolfgang
>  /
> >>> 
> >>> I would first check that all data in ~/.gnupg/ belongs to me.
> >> 
> >> yes, they do
> >> 
> >>> And _never_ use
> >>> sudo for gpg.
> >> 
> >> now I know. Thanks
> >> 
> >>> To check if a file 'fxxx' and the signature are in sync:
> >>>   # gpg --verify fxxx.sig fxxx
> >>> 
> >>> To import a public key I would use a gui like  e.g. seahorse.
> >> 
> >> I have installed seahorse and tried it. But I need a hint.
> >> I have a folder
> >> lyx-2-3-new
> >> which contains the
> >> .tar.xz and the tar.xz.sig
> >> Seahorse does not seem to recognize the content of the tar.xz stuff.
> >> Do I have to extract the .tar.xz and the tar.xz.sig first, move the sig
> >> into the folder with the extracted stuff and than run it?
> >> Sorry for these probably naive questions, but I am in the 80s and it
> >> takes all its time.
> >> Thanks for your patience
> >> Wolfgang
> > 
> > # seahorse
> > 
> > Entfernt->Entfernte Schlüssel suchen...->Suche nach: sanda@lyx
> > 
> > Suchort: 
> > hkp://keyserver.ubuntu.com:11371
> > 
> > click on the entry with 'Signing LyX tarballs and binaries'
> > click on '+ Importieren
> > leave the dialog
> > goto GnuPG-Schlüssel
> > left click on this new key ->Eigenschaften->Vertrauen
> > click on 'Vertrauen in diesen Schlüssel'
> > close dialog
> > 
> > You should be done
> > 
> > Kornel
> 
> I guess, you meant with # seahorse
> run as superuser.

PLEASE NO
Never as superuser, if you are doing something private.

> The terminal from which I ran it, tells
> # seahorse
> (seahorse:32621): GLib-GIO-CRITICAL 

Re: lyx-2.3.1beta-1

2018-02-01 Thread Wolfgang Engelmann



Am 01.02.2018 um 11:49 schrieb Kornel Benko:

Am Donnerstag, 1. Februar 2018 11:21:26 CET schrieb Wolfgang Engelmann
:

Am 01.02.2018 um 10:04 schrieb Kornel Benko:

Am Donnerstag, 1. Februar 2018 09:39:11 CET schrieb Wolfgang Engelmann

:

Am 01.02.2018 um 09:24 schrieb Kornel Benko:

Am Donnerstag, 1. Februar 2018 09:07:50 CET schrieb Wolfgang Engelmann

:

Am 31.01.2018 um 18:23 schrieb Joel Kulesza:

On Wed, Jan 31, 2018 at 9:11 AM, Uwe Stöhr > wrote:
   Am 31.01.2018 um 10:31 schrieb Wolfgang Engelmann:
   2- How do I use the tar.xz.sig file in respect to the
   tar.xz?
   
   This is the signature file to check if the file you downloaded

   was
   not modified.

Uwe described what the file is, but how it is used is summarized here:
http://www.lyx.org/Download#toc11 

- Joel

Using the instruction given and after installing xz-utils

sudo gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D

gives me

gpg: Schlüssel DE7A44FAC7FB382D: Öffentlicher Schlüssel "LyX Release
Manager (Signing LyX tarballs and binaries) " importiert
gpg: keine ultimativ vertrauenswürdigen Schlüssel gefunden
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg:  importiert: 1
(open key, no ultimative reliable key found, number of used keys )

Is this to be expected?
Wolfgang

Yes, and you should _not_ use 'sudo' here.

Kornel

Thanks, Kornel,

I tried it first without sudo and got

gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
gpg: lookup_hashtable failed: Unbekannter Systemfehler
/unknown system error/
gpg: trustdb: searching trust record failed: Unbekannter Systemfehler
gpg: Fehler: Die Vertrauensdatenbank ist fehlerhaft
/trusting databank erraneous/
gpg: Sie können versuchen die Vertrauensdatenbank durch folgende Befehle
wiederherzustellen:
gpg:   cd ~/.gnupg
gpg:   gpg --export-ownertrust > otrust.tmp
gpg:   rm trustdb.gpg
gpg:   gpg --import-ownertrust < otrust.tmp
gpg: Falls dies nicht funktioniert, sehen Sie bitte im Handbuch nach
/if not working, check manual

after the wrong sudo I tried again without sudo:
/~$ gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
gpg: Empfangen vom Schlüsselserver fehlgeschlagen: Keine Daten

Maybe some data not readable by you.


/receiving of keyserver failed: No data

Should I have first canceled my wrong attempt to use sudo, and how would
I do that?

Wolfgang
/

I would first check that all data in ~/.gnupg/ belongs to me.

yes, they do


And _never_ use
sudo for gpg.

now I know. Thanks


To check if a file 'fxxx' and the signature are in sync:
# gpg --verify fxxx.sig fxxx

To import a public key I would use a gui like  e.g. seahorse.

I have installed seahorse and tried it. But I need a hint.
I have a folder
lyx-2-3-new
which contains the
.tar.xz and the tar.xz.sig
Seahorse does not seem to recognize the content of the tar.xz stuff.
Do I have to extract the .tar.xz and the tar.xz.sig first, move the sig
into the folder with the extracted stuff and than run it?
Sorry for these probably naive questions, but I am in the 80s and it
takes all its time.
Thanks for your patience
Wolfgang

# seahorse
Entfernt->Entfernte Schlüssel suchen...->Suche nach: sanda@lyx
Suchort: 
hkp://keyserver.ubuntu.com:11371

click on the entry with 'Signing LyX tarballs and binaries'
click on '+ Importieren
leave the dialog
goto GnuPG-Schlüssel
left click on this new key ->Eigenschaften->Vertrauen
click on 'Vertrauen in diesen Schlüssel'
close dialog

You should be done

Kornel

I guess, you meant with # seahorse
run as superuser.
The terminal from which I ran it, tells
# seahorse
(seahorse:32621): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion 
'G_IS_DBUS_CONNECTION (connection)' failed
(seahorse:32621): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner: 
assertion 'G_IS_DBUS_PROXY (proxy)' failed
(seahorse:32621): seahorse-WARNING **: gkr-backend.vala:90: couldn't 
connect to secret service: Verbindung ist geschlossen


Might have to do with your

To check if a file 'fxxx' and the signature are in sync:
# gpg --verify fxxx.sig fxxx
?? Wolfgang





Re: lyx-2.3.1beta-1

2018-02-01 Thread Wolfgang Engelmann



Am 01.02.2018 um 10:04 schrieb Kornel Benko:

Am Donnerstag, 1. Februar 2018 09:39:11 CET schrieb Wolfgang Engelmann
:

Am 01.02.2018 um 09:24 schrieb Kornel Benko:

Am Donnerstag, 1. Februar 2018 09:07:50 CET schrieb Wolfgang Engelmann

:

Am 31.01.2018 um 18:23 schrieb Joel Kulesza:

On Wed, Jan 31, 2018 at 9:11 AM, Uwe Stöhr > wrote:
  Am 31.01.2018 um 10:31 schrieb Wolfgang Engelmann:
  2- How do I use the tar.xz.sig file in respect to the tar.xz?
  
  This is the signature file to check if the file you downloaded was

  not modified.

Uwe described what the file is, but how it is used is summarized here:
http://www.lyx.org/Download#toc11 

- Joel

Using the instruction given and after installing xz-utils

sudo gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D

gives me

gpg: Schlüssel DE7A44FAC7FB382D: Öffentlicher Schlüssel "LyX Release
Manager (Signing LyX tarballs and binaries) " importiert
gpg: keine ultimativ vertrauenswürdigen Schlüssel gefunden
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg:  importiert: 1
(open key, no ultimative reliable key found, number of used keys )

Is this to be expected?
Wolfgang

Yes, and you should _not_ use 'sudo' here.

Kornel

Thanks, Kornel,

I tried it first without sudo and got

gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
gpg: lookup_hashtable failed: Unbekannter Systemfehler
/unknown system error/
gpg: trustdb: searching trust record failed: Unbekannter Systemfehler
gpg: Fehler: Die Vertrauensdatenbank ist fehlerhaft
/trusting databank erraneous/
gpg: Sie können versuchen die Vertrauensdatenbank durch folgende Befehle
wiederherzustellen:
gpg:   cd ~/.gnupg
gpg:   gpg --export-ownertrust > otrust.tmp
gpg:   rm trustdb.gpg
gpg:   gpg --import-ownertrust < otrust.tmp
gpg: Falls dies nicht funktioniert, sehen Sie bitte im Handbuch nach
/if not working, check manual

after the wrong sudo I tried again without sudo:
/~$ gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
gpg: Empfangen vom Schlüsselserver fehlgeschlagen: Keine Daten

Maybe some data not readable by you.
  

/receiving of keyserver failed: No data

Should I have first canceled my wrong attempt to use sudo, and how would
I do that?

Wolfgang
/

I would first check that all data in ~/.gnupg/ belongs to me.

yes, they do

And _never_ use
sudo for gpg.

now I know. Thanks


To check if a file 'fxxx' and the signature are in sync:
# gpg --verify fxxx.sig fxxx

To import a public key I would use a gui like  e.g. seahorse.

I have installed seahorse and tried it. But I need a hint.
I have a folder
lyx-2-3-new
which contains the
.tar.xz and the tar.xz.sig
Seahorse does not seem to recognize the content of the tar.xz stuff.
Do I have to extract the .tar.xz and the tar.xz.sig first, move the sig 
into the folder with the extracted stuff and than run it?
Sorry for these probably naive questions, but I am in the 80s and it 
takes all its time.

Thanks for your patience
Wolfgang



Again, not as
root.

Kornel





Re: “Missing Glyphs!” / LinLibertine

2018-02-01 Thread S. Noble
>> Am Dienstag, den 30.01.2018, 13:09 -0500 schrieb Scott Kostyshak: 

>> Thank you for your detailed explanations. 

>> Scott 

> +1.

> Jürgen. 

+ 2. 

It's much appreciated.

Seb.

Re: lyx-2.3.1beta-1

2018-02-01 Thread Kornel Benko
Am Donnerstag, 1. Februar 2018 09:39:11 CET schrieb Wolfgang Engelmann 
:
> Am 01.02.2018 um 09:24 schrieb Kornel Benko:
> > Am Donnerstag, 1. Februar 2018 09:07:50 CET schrieb Wolfgang Engelmann
> > 
> > :
> >> Am 31.01.2018 um 18:23 schrieb Joel Kulesza:
> >>> On Wed, Jan 31, 2018 at 9:11 AM, Uwe Stöhr  >>> 
> >>> > wrote:
> >>>  Am 31.01.2018 um 10:31 schrieb Wolfgang Engelmann:
> >>>  2- How do I use the tar.xz.sig file in respect to the tar.xz?
> >>>  
> >>>  This is the signature file to check if the file you downloaded was
> >>>  not modified.
> >>> 
> >>> Uwe described what the file is, but how it is used is summarized here:
> >>> http://www.lyx.org/Download#toc11 
> >>> 
> >>> - Joel
> >> 
> >> Using the instruction given and after installing xz-utils
> >> 
> >> sudo gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
> >> 
> >> gives me
> >> 
> >> gpg: Schlüssel DE7A44FAC7FB382D: Öffentlicher Schlüssel "LyX Release
> >> Manager (Signing LyX tarballs and binaries) " importiert
> >> gpg: keine ultimativ vertrauenswürdigen Schlüssel gefunden
> >> gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
> >> gpg:  importiert: 1
> >> (open key, no ultimative reliable key found, number of used keys )
> >> 
> >> Is this to be expected?
> >> Wolfgang
> > 
> > Yes, and you should _not_ use 'sudo' here.
> > 
> > Kornel
> 
> Thanks, Kornel,
> 
> I tried it first without sudo and got
> 
> gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
> gpg: lookup_hashtable failed: Unbekannter Systemfehler
> /unknown system error/
> gpg: trustdb: searching trust record failed: Unbekannter Systemfehler
> gpg: Fehler: Die Vertrauensdatenbank ist fehlerhaft
> /trusting databank erraneous/
> gpg: Sie können versuchen die Vertrauensdatenbank durch folgende Befehle
> wiederherzustellen:
> gpg:   cd ~/.gnupg
> gpg:   gpg --export-ownertrust > otrust.tmp
> gpg:   rm trustdb.gpg
> gpg:   gpg --import-ownertrust < otrust.tmp
> gpg: Falls dies nicht funktioniert, sehen Sie bitte im Handbuch nach
> /if not working, check manual
> 
> after the wrong sudo I tried again without sudo:
> /~$ gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
> gpg: Empfangen vom Schlüsselserver fehlgeschlagen: Keine Daten

Maybe some data not readable by you.
 
> /receiving of keyserver failed: No data
> 
> Should I have first canceled my wrong attempt to use sudo, and how would
> I do that?
> 
> Wolfgang
> /

I would first check that all data in ~/.gnupg/ belongs to me. And _never_ use 
sudo for gpg.

To check if a file 'fxxx' and the signature are in sync:
# gpg --verify fxxx.sig fxxx

To import a public key I would use a gui like  e.g. seahorse. Again, not as 
root.

Kornel



Re: lyx-2.3.1beta-1

2018-02-01 Thread Wolfgang Engelmann



Am 01.02.2018 um 09:24 schrieb Kornel Benko:

Am Donnerstag, 1. Februar 2018 09:07:50 CET schrieb Wolfgang Engelmann
:

Am 31.01.2018 um 18:23 schrieb Joel Kulesza:

On Wed, Jan 31, 2018 at 9:11 AM, Uwe Stöhr > wrote:
 Am 31.01.2018 um 10:31 schrieb Wolfgang Engelmann:
 2- How do I use the tar.xz.sig file in respect to the tar.xz?
 
 This is the signature file to check if the file you downloaded was

 not modified.

Uwe described what the file is, but how it is used is summarized here:
http://www.lyx.org/Download#toc11 

- Joel

Using the instruction given and after installing xz-utils

sudo gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D

gives me

gpg: Schlüssel DE7A44FAC7FB382D: Öffentlicher Schlüssel "LyX Release
Manager (Signing LyX tarballs and binaries) " importiert
gpg: keine ultimativ vertrauenswürdigen Schlüssel gefunden
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg:  importiert: 1
(open key, no ultimative reliable key found, number of used keys )

Is this to be expected?
Wolfgang

Yes, and you should _not_ use 'sudo' here.

Kornel


Thanks, Kornel,

I tried it first without sudo and got

gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
gpg: lookup_hashtable failed: Unbekannter Systemfehler
/unknown system error/
gpg: trustdb: searching trust record failed: Unbekannter Systemfehler
gpg: Fehler: Die Vertrauensdatenbank ist fehlerhaft
/trusting databank erraneous/
gpg: Sie können versuchen die Vertrauensdatenbank durch folgende Befehle
wiederherzustellen:
gpg:   cd ~/.gnupg
gpg:   gpg --export-ownertrust > otrust.tmp
gpg:   rm trustdb.gpg
gpg:   gpg --import-ownertrust < otrust.tmp
gpg: Falls dies nicht funktioniert, sehen Sie bitte im Handbuch nach
/if not working, check manual

after the wrong sudo I tried again without sudo:
/~$ gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
gpg: Empfangen vom Schlüsselserver fehlgeschlagen: Keine Daten

/receiving of keyserver failed: No data

Should I have first canceled my wrong attempt to use sudo, and how would 
I do that?


Wolfgang
/


Re: lyx-2.3.1beta-1

2018-02-01 Thread Kornel Benko
Am Donnerstag, 1. Februar 2018 09:07:50 CET schrieb Wolfgang Engelmann 
:
> Am 31.01.2018 um 18:23 schrieb Joel Kulesza:
> > On Wed, Jan 31, 2018 at 9:11 AM, Uwe Stöhr  > 
> > > wrote:
> > Am 31.01.2018 um 10:31 schrieb Wolfgang Engelmann:
> > 2- How do I use the tar.xz.sig file in respect to the tar.xz?
> > 
> > This is the signature file to check if the file you downloaded was
> > not modified.
> > 
> > Uwe described what the file is, but how it is used is summarized here:
> > http://www.lyx.org/Download#toc11 
> > 
> > - Joel
> 
> Using the instruction given and after installing xz-utils
> 
> sudo gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D
> 
> gives me
> 
> gpg: Schlüssel DE7A44FAC7FB382D: Öffentlicher Schlüssel "LyX Release
> Manager (Signing LyX tarballs and binaries) " importiert
> gpg: keine ultimativ vertrauenswürdigen Schlüssel gefunden
> gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
> gpg:  importiert: 1
> (open key, no ultimative reliable key found, number of used keys )
> 
> Is this to be expected?
> Wolfgang

Yes, and you should _not_ use 'sudo' here.

Kornel



Re: lyx-2.3.1beta-1

2018-02-01 Thread Wolfgang Engelmann



Am 31.01.2018 um 18:23 schrieb Joel Kulesza:
On Wed, Jan 31, 2018 at 9:11 AM, Uwe Stöhr > wrote:


Am 31.01.2018 um 10:31 schrieb Wolfgang Engelmann:

2- How do I use the tar.xz.sig file in respect to the tar.xz?


This is the signature file to check if the file you downloaded was
not modified.


Uwe described what the file is, but how it is used is summarized here: 
http://www.lyx.org/Download#toc11 


- Joel


Using the instruction given and after installing xz-utils

sudo gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D

gives me

gpg: Schlüssel DE7A44FAC7FB382D: Öffentlicher Schlüssel "LyX Release 
Manager (Signing LyX tarballs and binaries) " importiert

gpg: keine ultimativ vertrauenswürdigen Schlüssel gefunden
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg:  importiert: 1
(open key, no ultimative reliable key found, number of used keys )

Is this to be expected?
Wolfgang
##
NOTE ADDED:
I use Debian stretch and did a cut and paste for the key
Wolfgang


Re: lyx-2.3.1beta-1

2018-02-01 Thread Wolfgang Engelmann



Am 31.01.2018 um 18:23 schrieb Joel Kulesza:
On Wed, Jan 31, 2018 at 9:11 AM, Uwe Stöhr > wrote:


Am 31.01.2018 um 10:31 schrieb Wolfgang Engelmann:

2- How do I use the tar.xz.sig file in respect to the tar.xz?


This is the signature file to check if the file you downloaded was
not modified.


Uwe described what the file is, but how it is used is summarized here: 
http://www.lyx.org/Download#toc11 


- Joel


Using the instruction given and after installing xz-utils

sudo gpg --recv-keys FE66471B43559707AFDAD955DE7A44FAC7FB382D

gives me

gpg: Schlüssel DE7A44FAC7FB382D: Öffentlicher Schlüssel "LyX Release 
Manager (Signing LyX tarballs and binaries) " importiert

gpg: keine ultimativ vertrauenswürdigen Schlüssel gefunden
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg:  importiert: 1
(open key, no ultimative reliable key found, number of used keys )

Is this to be expected?
Wolfgang