Re: lyx 2.4.0dev crashes

2022-01-31 Thread Pavel Sanda via lyx-users 
On Fri, Jan 28, 2022 at 04:12:29PM +0100, Wolfgang Engelmann via lyx-users 
wrote:
> >Wolfgang
> and after some time:
> 
> Thread 1 "lyx" received signal SIGINT, Interrupt.
> 0x768573ff in poll () from /lib/x86_64-linux-gnu/libc.so.6
> 
> lyx appeared, but got stuck with thunderbird window
> 
> I inserted run again, but
> (gdb) run
> The program being debugged has been started already.
> Start it from the beginning? (y or n) n
> Program not restarted.
> (gdb)
> 
> should I wait longer for a further response of gdb?

No, gdb now waits for your input.
What happens if you ask for backtrace byt typing: bt
and hit enter.

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

Re: lyx 2.4.0dev crashes

2022-01-29 Thread Kornel Benko via lyx-users 
Am Sat, 29 Jan 2022 18:11:18 +0100
schrieb Wolfgang Engelmann via lyx-users :

> Am 29.01.22 um 16:06 schrieb Kornel Benko via lyx-users:
> > Am Sat, 29 Jan 2022 15:27:15 +0100
> > schrieb Wolfgang Engelmann via lyx-users :
> >   
> >> Am 29.01.22 um 15:07 schrieb Wolfgang Engelmann via lyx-users:  
> >>>
> >>>
> >>> Am 29.01.22 um 13:40 schrieb Scott Kostyshak via lyx-users:  
>  which -a lyx  
> >>> /usr/local/bin/lyx
> >>> /usr/bin/lyx
> >>>
> >>> ups! twice??
> >>>
> >>> ldd outputs in appendix
> >>>
> >>> Wolfgang
> >>>  
> >>
> >> This is the
> >> wolfgang@Fuji:/usr/bin$ ls lyx*
> >> lyx  lyxclient
> >> wolfgang@Fuji:/usr/bin$ cd /usr/local/bin/
> >>
> >> wolfgang@Fuji:/usr/local/bin$ ls lyx*
> >> lyx  lyxclient  
> >>   > is Version 2.4.0dev (not released yet)  
> >>
> >> /usr/bin$ ./lyx
> >> LyX: Unknown tag `\citation_search_view' [around line 507 of file
> >> ~/.lyx/lyxrc.defaults current token: '\citation_search_view' context: '']
> >> LyXRC.cpp (417): Conversion failed for /home/wolfgang/.lyx/preferences
> >> Warning: Die Konfigurationsdatei konnte nicht gelesen werden
> >> 
> >> Fehler beim Lesen der Konfigurationsdatei
> >> preferences.
> >> Bitte prüfen Sie Ihre Installation.
> >>  
> >>   > this does not start lyx  
> >>
> >> wolfgang@Fuji:/usr/local/bin$ ./lyx
> >> LyXComm: Pipe /home/wolfgang/.lyx/lyxpipe.in already exists.
> >> If no other LyX program is active, please delete the pipe by hand and
> >> try again.
> >> qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 795,
> >> resource id: 0, major code: 20 (GetProperty), minor code: 0
> >> Warning: Failed to produce 1 preview snippet(s)
> >>  
> >>   > this starts lyx  
> >>
> >> Should I just remove the /usr/bin lyx binary?
> >>
> >> Wolfgang
> >> Warning: Failed to produce 1 preview snippet(s)
> >>
> >>  
> > It may be that /usr/bin/lyx is provided by your package manager. So 
> > removing it
> > manually would be a very bad style IMO.
> > 
> > Better to set
> > a;) either your PATH to have /usr/local/bin prior to /usr/bin
> > or
> > b;) if your OS is debian based, use synaptic to withdraw the lyx.
> >  You may also check if the '/usr/bin/lyx' belongs to a package
> >  $ dpkg -S `which lyx`
> > 
> > Kornel
> > 
> >   
> Thanks, Kornel,
> I have completely removed the lyx 2.3.6 version using synaptic of my Debian.
> Since the 2.4.0. version is not yet available via synaptic, I keep this 
> developmental version which I compiled before.
> Wolfgang

Mark, that if you want to use both versions simultaneously, you should compile 
with
version suffix.
Add to automake configure parameters:
"--with-version-suffix=2.4"
or, if you build with cmake,
add to cmake configure eparameters:
"-DLYX_PROGRAM_SUFFIX:BOOL=ON -DLYX_LOCALVERSIONING:BOOL=ON"

depending on which build tool you use.
The resulting lyx-executable will be named "lyx2.4".

Kornel


pgp1tgpYqHQxm.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx 2.4.0dev crashes

2022-01-29 Thread Wolfgang Engelmann via lyx-users 



Am 29.01.22 um 16:06 schrieb Kornel Benko via lyx-users:

Am Sat, 29 Jan 2022 15:27:15 +0100
schrieb Wolfgang Engelmann via lyx-users :


Am 29.01.22 um 15:07 schrieb Wolfgang Engelmann via lyx-users:



Am 29.01.22 um 13:40 schrieb Scott Kostyshak via lyx-users:

which -a lyx

/usr/local/bin/lyx
/usr/bin/lyx

ups! twice??

ldd outputs in appendix

Wolfgang
   


This is the
wolfgang@Fuji:/usr/bin$ ls lyx*
lyx  lyxclient
wolfgang@Fuji:/usr/bin$ cd /usr/local/bin/

wolfgang@Fuji:/usr/local/bin$ ls lyx*
lyx  lyxclient
  > is Version 2.4.0dev (not released yet)

/usr/bin$ ./lyx
LyX: Unknown tag `\citation_search_view' [around line 507 of file
~/.lyx/lyxrc.defaults current token: '\citation_search_view' context: '']
LyXRC.cpp (417): Conversion failed for /home/wolfgang/.lyx/preferences
Warning: Die Konfigurationsdatei konnte nicht gelesen werden

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

  > this does not start lyx

wolfgang@Fuji:/usr/local/bin$ ./lyx
LyXComm: Pipe /home/wolfgang/.lyx/lyxpipe.in already exists.
If no other LyX program is active, please delete the pipe by hand and
try again.
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 795,
resource id: 0, major code: 20 (GetProperty), minor code: 0
Warning: Failed to produce 1 preview snippet(s)

  > this starts lyx

Should I just remove the /usr/bin lyx binary?

Wolfgang
Warning: Failed to produce 1 preview snippet(s)



It may be that /usr/bin/lyx is provided by your package manager. So removing it
manually would be a very bad style IMO.

Better to set
a;) either your PATH to have /usr/local/bin prior to /usr/bin
or
b;) if your OS is debian based, use synaptic to withdraw the lyx.
 You may also check if the '/usr/bin/lyx' belongs to a package
 $ dpkg -S `which lyx`

Kornel



Thanks, Kornel,
I have completely removed the lyx 2.3.6 version using synaptic of my Debian.
Since the 2.4.0. version is not yet available via synaptic, I keep this 
developmental version which I compiled before.

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

Re: lyx 2.4.0dev crashes

2022-01-29 Thread Kornel Benko via lyx-users 
Am Sat, 29 Jan 2022 15:27:15 +0100
schrieb Wolfgang Engelmann via lyx-users :

> Am 29.01.22 um 15:07 schrieb Wolfgang Engelmann via lyx-users:
> > 
> > 
> > Am 29.01.22 um 13:40 schrieb Scott Kostyshak via lyx-users:  
> >> which -a lyx  
> > /usr/local/bin/lyx
> > /usr/bin/lyx
> > 
> > ups! twice??
> > 
> > ldd outputs in appendix
> > 
> > Wolfgang
> >   
> 
> This is the
> wolfgang@Fuji:/usr/bin$ ls lyx*
> lyx  lyxclient
> wolfgang@Fuji:/usr/bin$ cd /usr/local/bin/
> 
> wolfgang@Fuji:/usr/local/bin$ ls lyx*
> lyx  lyxclient
>  > is Version 2.4.0dev (not released yet)  
> 
> /usr/bin$ ./lyx
> LyX: Unknown tag `\citation_search_view' [around line 507 of file 
> ~/.lyx/lyxrc.defaults current token: '\citation_search_view' context: '']
> LyXRC.cpp (417): Conversion failed for /home/wolfgang/.lyx/preferences
> Warning: Die Konfigurationsdatei konnte nicht gelesen werden
> 
> Fehler beim Lesen der Konfigurationsdatei
> preferences.
> Bitte prüfen Sie Ihre Installation.
> 
>  > this does not start lyx  
> 
> wolfgang@Fuji:/usr/local/bin$ ./lyx
> LyXComm: Pipe /home/wolfgang/.lyx/lyxpipe.in already exists.
> If no other LyX program is active, please delete the pipe by hand and 
> try again.
> qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 795, 
> resource id: 0, major code: 20 (GetProperty), minor code: 0
> Warning: Failed to produce 1 preview snippet(s)
> 
>  > this starts lyx  
> 
> Should I just remove the /usr/bin lyx binary?
> 
> Wolfgang
> Warning: Failed to produce 1 preview snippet(s)
> 
> 
It may be that /usr/bin/lyx is provided by your package manager. So removing it
manually would be a very bad style IMO.

Better to set
a;) either your PATH to have /usr/local/bin prior to /usr/bin
or
b;) if your OS is debian based, use synaptic to withdraw the lyx.
You may also check if the '/usr/bin/lyx' belongs to a package
$ dpkg -S `which lyx`

Kornel



pgpieTzbA7sxw.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx 2.4.0dev crashes

2022-01-29 Thread Wolfgang Engelmann via lyx-users 



Am 29.01.22 um 15:07 schrieb Wolfgang Engelmann via lyx-users:



Am 29.01.22 um 13:40 schrieb Scott Kostyshak via lyx-users:

which -a lyx

/usr/local/bin/lyx
/usr/bin/lyx

ups! twice??

ldd outputs in appendix

Wolfgang



This is the
wolfgang@Fuji:/usr/bin$ ls lyx*
lyx  lyxclient
wolfgang@Fuji:/usr/bin$ cd /usr/local/bin/

wolfgang@Fuji:/usr/local/bin$ ls lyx*
lyx  lyxclient
> is Version 2.4.0dev (not released yet)

/usr/bin$ ./lyx
LyX: Unknown tag `\citation_search_view' [around line 507 of file 
~/.lyx/lyxrc.defaults current token: '\citation_search_view' context: '']

LyXRC.cpp (417): Conversion failed for /home/wolfgang/.lyx/preferences
Warning: Die Konfigurationsdatei konnte nicht gelesen werden

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

> this does not start lyx

wolfgang@Fuji:/usr/local/bin$ ./lyx
LyXComm: Pipe /home/wolfgang/.lyx/lyxpipe.in already exists.
If no other LyX program is active, please delete the pipe by hand and 
try again.
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 795, 
resource id: 0, major code: 20 (GetProperty), minor code: 0

Warning: Failed to produce 1 preview snippet(s)

> this starts lyx

Should I just remove the /usr/bin lyx binary?

Wolfgang
Warning: Failed to produce 1 preview snippet(s)


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

Re: lyx 2.4.0dev crashes

2022-01-29 Thread Wolfgang Engelmann via lyx-users 



Am 29.01.22 um 13:40 schrieb Scott Kostyshak via lyx-users:

which -a lyx

/usr/local/bin/lyx
/usr/bin/lyx

ups! twice??

ldd outputs in appendix

Wolfganglinux-vdso.so.1 (0x7fff5219a000)
libmythes-1.2.so.0 => /usr/lib/x86_64-linux-gnu/libmythes-1.2.so.0 
(0x7f38f26f)
libenchant-2.so.2 => /usr/lib/x86_64-linux-gnu/libenchant-2.so.2 
(0x7f38f26e2000)
libmagic.so.1 => /usr/lib/x86_64-linux-gnu/libmagic.so.1 
(0x7f38f26b7000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f38f269a000)
libQt5Svg.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Svg.so.5 
(0x7f38f2643000)
libQt5Widgets.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 
(0x7f38f1fb9000)
libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 
(0x7f38f18f5000)
libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 
(0x7f38f13aa000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f38f11dd000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f38f1099000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f38f107f000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f38f0eba000)
/lib64/ld-linux-x86-64.so.2 (0x7f38f366a000)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7f38f0eb2000)
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7f38f0d83000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f38f0d7)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f38f0d4e000)
libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x7f38f0cc7000)
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 
(0x7f38f0c8b000)
libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 
(0x7f38f0ba3000)
libmd4c.so.0 => /usr/lib/x86_64-linux-gnu/libmd4c.so.0 
(0x7f38f0b91000)
libdouble-conversion.so.3 => 
/usr/lib/x86_64-linux-gnu/libdouble-conversion.so.3 (0x7f38f0b7a000)
libicui18n.so.67 => /usr/lib/x86_64-linux-gnu/libicui18n.so.67 
(0x7f38f0874000)
libicuuc.so.67 => /usr/lib/x86_64-linux-gnu/libicuuc.so.67 
(0x7f38f068b000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f38f0685000)
libpcre2-16.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-16.so.0 
(0x7f38f05f9000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f38f051e000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f38f04ab000)
libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 
(0x7f38f03f3000)
libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0 
(0x7f38f03bf000)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 
(0x7f38f02fa000)
libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 
(0x7f38f02ce000)
libicudata.so.67 => /usr/lib/x86_64-linux-gnu/libicudata.so.67 
(0x7f38ee7b5000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 
(0x7f38ee672000)
libbrotlidec.so.1 => /usr/lib/x86_64-linux-gnu/libbrotlidec.so.1 
(0x7f38ee664000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 
(0x7f38ee637000)
libbrotlicommon.so.1 => /usr/lib/x86_64-linux-gnu/libbrotlicommon.so.1 
(0x7f38ee614000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 
(0x7f38ee60f000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 
(0x7f38ee409000)
libbsd.so.0 => /usr/lib/x86_64-linux-gnu/libbsd.so.0 
(0x7f38ee3f2000)
libmd.so.0 => /usr/lib/x86_64-linux-gnu/libmd.so.0 (0x7f38ee3e5000)
linux-vdso.so.1 (0x792c7000)
libmythes-1.2.so.0 => /usr/lib/x86_64-linux-gnu/libmythes-1.2.so.0 
(0x7fddd895a000)
libenchant-2.so.2 => /usr/lib/x86_64-linux-gnu/libenchant-2.so.2 
(0x7fddd894c000)
libmagic.so.1 => /usr/lib/x86_64-linux-gnu/libmagic.so.1 
(0x7fddd8921000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fddd8904000)
libQt5Svg.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Svg.so.5 
(0x7fddd88ad000)
libQt5Widgets.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 
(0x7fddd8223000)
libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 
(0x7fddd7b5f000)
libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 
(0x7fddd7614000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fddd7447000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fddd7303000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fddd72e9000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fddd7124000)
/lib64/ld-linux-x86-64.so.2 (0x7fddd9be9000)
libgmodule-2.0.so.0 =>

Re: lyx 2.4.0dev crashes

2022-01-29 Thread Scott Kostyshak via lyx-users 
On Sat, Jan 29, 2022 at 09:34:37AM +0100, Wolfgang Engelmann via lyx-users 
wrote:
> 
> 
> Am 28.01.22 um 19:30 schrieb Scott Kostyshak via lyx-users:
> > On Fri, Jan 28, 2022 at 05:33:05PM +0100, Jean-Marc Lasgouttes via 
> > lyx-users wrote:
> > > Le 28/01/2022 à 16:47, Wolfgang Engelmann via lyx-users a écrit :
> > > > <
> > > > 
> > > > Am 28.01.22 um 16:36 schrieb Jean-Marc Lasgouttes via lyx-users:
> > > > > Le 28/01/2022 à 16:34, Wolfgang Engelmann via lyx-users a écrit :
> > > > > > Neither do I.
> > > > > > But usually it is due to me, doing something wrong
> > > > > 
> > > > > I have seen total hangs with thunderbird, until I disabled hardware
> > > > > acceleration.
> > > > > 
> > > > > JMarc
> > > > 
> > > > Can't recall, that I enabled hardware acceleration.
> > > 
> > > It is on by default these days.
> > > 
> > > > I can start lyx again, the document where it hung, has .lyx#
> > > > 
> > > > I tried to use
> > > > view other formats
> > > >    view PDF(LuaTeX)
> > > > for a pdf output of the lyx file
> > > > 
> > > > when the trouble started. It might have to do with this?
> > > 
> > > I don't know... And I do not like the XCB errors tht are shown, either.
> > > Sorry.
> > 
> > I wonder if doing 'ldd' on the 'lyx' binary could give helpful errors on a 
> > potential problem.
> > 
> > Scott
> > 
> > 
> where does one find the lyx binary?

Type "which -a lyx"

Scott


signature.asc
Description: PGP signature
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx 2.4.0dev crashes

2022-01-29 Thread Wolfgang Engelmann via lyx-users 



Am 28.01.22 um 19:30 schrieb Scott Kostyshak via lyx-users:

On Fri, Jan 28, 2022 at 05:33:05PM +0100, Jean-Marc Lasgouttes via lyx-users 
wrote:

Le 28/01/2022 à 16:47, Wolfgang Engelmann via lyx-users a écrit :

<

Am 28.01.22 um 16:36 schrieb Jean-Marc Lasgouttes via lyx-users:

Le 28/01/2022 à 16:34, Wolfgang Engelmann via lyx-users a écrit :

Neither do I.
But usually it is due to me, doing something wrong


I have seen total hangs with thunderbird, until I disabled hardware
acceleration.

JMarc


Can't recall, that I enabled hardware acceleration.


It is on by default these days.


I can start lyx again, the document where it hung, has .lyx#

I tried to use
view other formats
   view PDF(LuaTeX)
for a pdf output of the lyx file

when the trouble started. It might have to do with this?


I don't know... And I do not like the XCB errors tht are shown, either.
Sorry.


I wonder if doing 'ldd' on the 'lyx' binary could give helpful errors on a 
potential problem.

Scott



where does one find the lyx binary?
Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Scott Kostyshak via lyx-users 
On Fri, Jan 28, 2022 at 05:33:05PM +0100, Jean-Marc Lasgouttes via lyx-users 
wrote:
> Le 28/01/2022 à 16:47, Wolfgang Engelmann via lyx-users a écrit :
> > <
> > 
> > Am 28.01.22 um 16:36 schrieb Jean-Marc Lasgouttes via lyx-users:
> > > Le 28/01/2022 à 16:34, Wolfgang Engelmann via lyx-users a écrit :
> > > > Neither do I.
> > > > But usually it is due to me, doing something wrong
> > > 
> > > I have seen total hangs with thunderbird, until I disabled hardware
> > > acceleration.
> > > 
> > > JMarc
> > 
> > Can't recall, that I enabled hardware acceleration.
> 
> It is on by default these days.
> 
> > I can start lyx again, the document where it hung, has .lyx#
> > 
> > I tried to use
> > view other formats
> >   view PDF(LuaTeX)
> > for a pdf output of the lyx file
> > 
> > when the trouble started. It might have to do with this?
> 
> I don't know... And I do not like the XCB errors tht are shown, either.
> Sorry.

I wonder if doing 'ldd' on the 'lyx' binary could give helpful errors on a 
potential problem.

Scott


signature.asc
Description: PGP signature
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Jean-Marc Lasgouttes via lyx-users 

Le 28/01/2022 à 16:47, Wolfgang Engelmann via lyx-users a écrit :

<

Am 28.01.22 um 16:36 schrieb Jean-Marc Lasgouttes via lyx-users:

Le 28/01/2022 à 16:34, Wolfgang Engelmann via lyx-users a écrit :

Neither do I.
But usually it is due to me, doing something wrong


I have seen total hangs with thunderbird, until I disabled hardware 
acceleration.


JMarc


Can't recall, that I enabled hardware acceleration.


It is on by default these days.


I can start lyx again, the document where it hung, has .lyx#

I tried to use
view other formats
  view PDF(LuaTeX)
for a pdf output of the lyx file

when the trouble started. It might have to do with this?


I don't know... And I do not like the XCB errors tht are shown, either. 
Sorry.


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

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Wolfgang Engelmann via lyx-users 

<

Am 28.01.22 um 16:36 schrieb Jean-Marc Lasgouttes via lyx-users:

Le 28/01/2022 à 16:34, Wolfgang Engelmann via lyx-users a écrit :

Neither do I.
But usually it is due to me, doing something wrong


I have seen total hangs with thunderbird, until I disabled hardware 
acceleration.


JMarc


Can't recall, that I enabled hardware acceleration.

I can start lyx again, the document where it hung, has .lyx#

I tried to use
view other formats
 view PDF(LuaTeX)
for a pdf output of the lyx file

when the trouble started. It might have to do with this?

Wolfgang

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

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Jean-Marc Lasgouttes via lyx-users 

Le 28/01/2022 à 16:34, Wolfgang Engelmann via lyx-users a écrit :

Neither do I.
But usually it is due to me, doing something wrong


I have seen total hangs with thunderbird, until I disabled hardware 
acceleration.


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

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Wolfgang Engelmann via lyx-users 



Am 28.01.22 um 16:31 schrieb Jean-Marc Lasgouttes via lyx-users:

Le 28/01/2022 à 16:15, Wolfgang Engelmann via lyx-users a écrit :



[New Thread 0x7fffc1ffb700 (LWP 3207)]
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 598, 
resource id: 0, major code: 20 (GetProperty), minor code: 0


No crash?

JMarc


Got stuck, as described at 16:12o'clock


I don't like that...

JMarc


Neither do I.
But usually it is due to me, doing something wrong
Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Jean-Marc Lasgouttes via lyx-users 

Le 28/01/2022 à 16:15, Wolfgang Engelmann via lyx-users a écrit :



[New Thread 0x7fffc1ffb700 (LWP 3207)]
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 598, 
resource id: 0, major code: 20 (GetProperty), minor code: 0


No crash?

JMarc


Got stuck, as described at 16:12o'clock


I don't like that...

JMarc

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

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Wolfgang Engelmann via lyx-users 



Am 28.01.22 um 16:10 schrieb Jean-Marc Lasgouttes via lyx-users:

Le 28/01/2022 à 16:01, Wolfgang Engelmann via lyx-users a écrit :

After you see that prompt "(gdb)", then type "run" and press .

Scott



Here is the output:

Starting program: /usr/local/bin/lyx
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/x86_64-linux-gnu/libthread_db.so.1".

[New Thread 0x72aad700 (LWP 3194)]

...

[New Thread 0x7fffc1ffb700 (LWP 3207)]
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 598, 
resource id: 0, major code: 20 (GetProperty), minor code: 0


No crash?

JMarc


Got stuck, as described at 16:12o'clock
Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Wolfgang Engelmann via lyx-users 



Am 28.01.22 um 16:01 schrieb Wolfgang Engelmann via lyx-users:



Am 28.01.22 um 15:59 schrieb Scott Kostyshak via lyx-users:
On Fri, Jan 28, 2022 at 03:57:38PM +0100, Wolfgang Engelmann via 
lyx-users wrote:



Am 28.01.22 um 11:38 schrieb Jean-Marc Lasgouttes via lyx-users:

Le 28/01/2022 à 11:23, Wolfgang Engelmann via lyx-users a écrit :

on a terminal

$ lyx

but it crashes with this output on the terminal:

qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 598,
resource id: 0, major code: 20 (GetProperty), minor code: 0
/usr/include/c++/10/bits/stl_stack.h:274: void std::stack<_Tp,
_Sequence>::pop() [with _Tp = int; _Sequence =
std::__debug::deque >]: Assertion
'__builtin_expect(!this->empty(), true)' failed.
Abgebrochen

what should I do?


Can you run it under gdb?

gdb lyx
run
[crash]
bt

JMarc


Thanks, Jean-Marc .
This is what I got after waiting for quite some time:

$ gdb lyx
GNU gdb (Debian 10.1-2) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
 .

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from lyx...
(gdb)


After you see that prompt "(gdb)", then type "run" and press .

Scott



Here is the output:

Starting program: /usr/local/bin/lyx
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x72aad700 (LWP 3194)]
[New Thread 0x7fffebfff700 (LWP 3195)]
[New Thread 0x7fffe8541700 (LWP 3196)]
[New Thread 0x7fffe8340700 (LWP 3197)]
[New Thread 0x7fffe3601700 (LWP 3198)]
[New Thread 0x7fffe3400700 (LWP 3199)]
[New Thread 0x7fffe1f0d700 (LWP 3200)]
[New Thread 0x7fffe170c700 (LWP 3201)]
[New Thread 0x7fffe0f0b700 (LWP 3202)]
[New Thread 0x7fffc3fff700 (LWP 3203)]
[New Thread 0x7fffc37fe700 (LWP 3204)]
[New Thread 0x7fffc2ffd700 (LWP 3205)]
[New Thread 0x7fffc27fc700 (LWP 3206)]
[New Thread 0x7fffc1ffb700 (LWP 3207)]
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 598, 
resource id: 0, major code: 20 (GetProperty), minor code: 0


Wolfgang

and after some time:

Thread 1 "lyx" received signal SIGINT, Interrupt.
0x768573ff in poll () from /lib/x86_64-linux-gnu/libc.so.6

lyx appeared, but got stuck with thunderbird window

I inserted run again, but
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) n
Program not restarted.
(gdb)

should I wait longer for a further response of gdb?

Wolfgang

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

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Jean-Marc Lasgouttes via lyx-users 

Le 28/01/2022 à 16:01, Wolfgang Engelmann via lyx-users a écrit :

After you see that prompt "(gdb)", then type "run" and press .

Scott



Here is the output:

Starting program: /usr/local/bin/lyx
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x72aad700 (LWP 3194)]

...

[New Thread 0x7fffc1ffb700 (LWP 3207)]
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 598, 
resource id: 0, major code: 20 (GetProperty), minor code: 0


No crash?

JMarc

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

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Wolfgang Engelmann via lyx-users 



Am 28.01.22 um 15:59 schrieb Scott Kostyshak via lyx-users:

On Fri, Jan 28, 2022 at 03:57:38PM +0100, Wolfgang Engelmann via lyx-users 
wrote:



Am 28.01.22 um 11:38 schrieb Jean-Marc Lasgouttes via lyx-users:

Le 28/01/2022 à 11:23, Wolfgang Engelmann via lyx-users a écrit :

on a terminal

$ lyx

but it crashes with this output on the terminal:

qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 598,
resource id: 0, major code: 20 (GetProperty), minor code: 0
/usr/include/c++/10/bits/stl_stack.h:274: void std::stack<_Tp,
_Sequence>::pop() [with _Tp = int; _Sequence =
std::__debug::deque >]: Assertion
'__builtin_expect(!this->empty(), true)' failed.
Abgebrochen

what should I do?


Can you run it under gdb?

gdb lyx
run
[crash]
bt

JMarc


Thanks, Jean-Marc .
This is what I got after waiting for quite some time:

$ gdb lyx
GNU gdb (Debian 10.1-2) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
 .

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from lyx...
(gdb)


After you see that prompt "(gdb)", then type "run" and press .

Scott



Here is the output:

Starting program: /usr/local/bin/lyx
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x72aad700 (LWP 3194)]
[New Thread 0x7fffebfff700 (LWP 3195)]
[New Thread 0x7fffe8541700 (LWP 3196)]
[New Thread 0x7fffe8340700 (LWP 3197)]
[New Thread 0x7fffe3601700 (LWP 3198)]
[New Thread 0x7fffe3400700 (LWP 3199)]
[New Thread 0x7fffe1f0d700 (LWP 3200)]
[New Thread 0x7fffe170c700 (LWP 3201)]
[New Thread 0x7fffe0f0b700 (LWP 3202)]
[New Thread 0x7fffc3fff700 (LWP 3203)]
[New Thread 0x7fffc37fe700 (LWP 3204)]
[New Thread 0x7fffc2ffd700 (LWP 3205)]
[New Thread 0x7fffc27fc700 (LWP 3206)]
[New Thread 0x7fffc1ffb700 (LWP 3207)]
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 598, 
resource id: 0, major code: 20 (GetProperty), minor code: 0


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

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Scott Kostyshak via lyx-users 
On Fri, Jan 28, 2022 at 03:57:38PM +0100, Wolfgang Engelmann via lyx-users 
wrote:
> 
> 
> Am 28.01.22 um 11:38 schrieb Jean-Marc Lasgouttes via lyx-users:
> > Le 28/01/2022 à 11:23, Wolfgang Engelmann via lyx-users a écrit :
> > > on a terminal
> > > 
> > > $ lyx
> > > 
> > > but it crashes with this output on the terminal:
> > > 
> > > qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 598,
> > > resource id: 0, major code: 20 (GetProperty), minor code: 0
> > > /usr/include/c++/10/bits/stl_stack.h:274: void std::stack<_Tp,
> > > _Sequence>::pop() [with _Tp = int; _Sequence =
> > > std::__debug::deque >]: Assertion
> > > '__builtin_expect(!this->empty(), true)' failed.
> > > Abgebrochen
> > > 
> > > what should I do?
> > 
> > Can you run it under gdb?
> > 
> > gdb lyx
> > run
> > [crash]
> > bt
> > 
> > JMarc
> > 
> Thanks, Jean-Marc .
> This is what I got after waiting for quite some time:
> 
> $ gdb lyx
> GNU gdb (Debian 10.1-2) 10.1.90.20210103-git
> Copyright (C) 2021 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> 
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from lyx...
> (gdb)

After you see that prompt "(gdb)", then type "run" and press .

Scott


signature.asc
Description: PGP signature
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Wolfgang Engelmann via lyx-users 



Am 28.01.22 um 11:38 schrieb Jean-Marc Lasgouttes via lyx-users:

Le 28/01/2022 à 11:23, Wolfgang Engelmann via lyx-users a écrit :

on a terminal

$ lyx

but it crashes with this output on the terminal:

qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 598, 
resource id: 0, major code: 20 (GetProperty), minor code: 0
/usr/include/c++/10/bits/stl_stack.h:274: void std::stack<_Tp, 
_Sequence>::pop() [with _Tp = int; _Sequence = 
std::__debug::deque >]: Assertion 
'__builtin_expect(!this->empty(), true)' failed.

Abgebrochen

what should I do?


Can you run it under gdb?

gdb lyx
run
[crash]
bt

JMarc


Thanks, Jean-Marc .
This is what I got after waiting for quite some time:

$ gdb lyx
GNU gdb (Debian 10.1-2) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from lyx...
(gdb)

What would you have expected?

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

Re: lyx 2.4.0dev crashes

2022-01-28 Thread Jean-Marc Lasgouttes via lyx-users 

Le 28/01/2022 à 11:23, Wolfgang Engelmann via lyx-users a écrit :

on a terminal

$ lyx

but it crashes with this output on the terminal:

qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 598, 
resource id: 0, major code: 20 (GetProperty), minor code: 0
/usr/include/c++/10/bits/stl_stack.h:274: void std::stack<_Tp, 
_Sequence>::pop() [with _Tp = int; _Sequence = std::__debug::dequestd::allocator >]: Assertion '__builtin_expect(!this->empty(), 
true)' failed.

Abgebrochen

what should I do?


Can you run it under gdb?

gdb lyx
run
[crash]
bt

JMarc

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