Re: Crash in File-Open

[Scott Kostyshak]

On Wed, Mar 22, 2017 at 08:09:11AM +0100, Kornel Benko wrote:

> It succeeds though with 'sudo dpkg -i 
> --ignore-depends=libstdc++6,libhunspell-1.3-0 lyx23.scott.deb'
> But then
> # /usr/local/bin/lyx
> /usr/local/bin/lyx: relocation error: /usr/local/bin/lyx: symbol _ZdlPvm, 
> version Qt_5 not defined in file libQt5Core.so.5 with link time reference

Dang. Well it was worth a try.

Scott


signature.asc
Description: PGP signature

Re: Crash in File-Open

[Kornel Benko]

Am Mittwoch, 22. März 2017 um 01:43:58, schrieb Scott Kostyshak 

> On Tue, Mar 21, 2017 at 11:54:56PM +0100, Kornel Benko wrote:
> > Am Dienstag, 21. März 2017 um 18:33:07, schrieb Scott Kostyshak 
> > 
> > > On Tue, Mar 21, 2017 at 05:14:59PM +0100, Kornel Benko wrote:
> > > 
> > > > I could send you my lyx-executable.
> > > 
> > > That could give some clues. Should we build .deb packages and trade?
> > > 
> > > Scott
> > 
> > I always build a deb package. 27MB. I would upload if I would know to where.
> 
> I put mine on Dropbox:
> 
> https://www.dropbox.com/s/vepdw4pai0ohlxt/lyx23-2.3.0-49141git-Linux.deb?dl=0

Looks like I cannot use this package. Your system is more advanced.

# sudo dpkg -i lyx23.scott.deb
(Reading database ... 383716 files and directories currently installed.)
Preparing to unpack lyx23.scott.deb ...
Unpacking lyx23 (2.3.0-49141git) over (2.3.0-49141git) ...
dpkg: dependency problems prevent configuration of lyx23:
 lyx23 depends on libhunspell-1.3-0 (>= 1.3.3); however:
  Version of libhunspell-1.3-0:amd64 on system is 1.3.2-6ubuntu2.1.
 lyx23 depends on libstdc++6 (>= 5.2); however:
  Version of libstdc++6:amd64 on system is 4.8.4-2ubuntu1~14.04.3.

dpkg: error processing package lyx23 (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Errors were encountered while processing:
 lyx23

It succeeds though with 'sudo dpkg -i 
--ignore-depends=libstdc++6,libhunspell-1.3-0 lyx23.scott.deb'
But then
# /usr/local/bin/lyx
/usr/local/bin/lyx: relocation error: /usr/local/bin/lyx: symbol _ZdlPvm, 
version Qt_5 not defined in file libQt5Core.so.5 with link time reference

> The sig is attached.
> 
> SHA256 is:
> 6700eab25a24f9a82445678ccf855f91716f08906743ecb7bad4808124601d35
> 
> Scott

Thanks.

Kornel

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

Re: Crash in File-Open

[Scott Kostyshak]

On Tue, Mar 21, 2017 at 11:54:56PM +0100, Kornel Benko wrote:
> Am Dienstag, 21. März 2017 um 18:33:07, schrieb Scott Kostyshak 
> 
> > On Tue, Mar 21, 2017 at 05:14:59PM +0100, Kornel Benko wrote:
> > 
> > > I could send you my lyx-executable.
> > 
> > That could give some clues. Should we build .deb packages and trade?
> > 
> > Scott
> 
> I always build a deb package. 27MB. I would upload if I would know to where.

I put mine on Dropbox:

https://www.dropbox.com/s/vepdw4pai0ohlxt/lyx23-2.3.0-49141git-Linux.deb?dl=0

The sig is attached.

SHA256 is:
6700eab25a24f9a82445678ccf855f91716f08906743ecb7bad4808124601d35

Scott


lyx23-2.3.0-49141git-Linux.deb.sig
Description: Binary data


signature.asc
Description: PGP signature

Re: Crash in File-Open

[Kornel Benko]

Am Dienstag, 21. März 2017 um 18:33:07, schrieb Scott Kostyshak 

> On Tue, Mar 21, 2017 at 05:14:59PM +0100, Kornel Benko wrote:
> 
> > I could send you my lyx-executable.
> 
> That could give some clues. Should we build .deb packages and trade?
> 
> Scott

I always build a deb package. 27MB. I would upload if I would know to where.

Kornel

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

Re: Crash in File-Open

[Scott Kostyshak]

On Tue, Mar 21, 2017 at 05:14:59PM +0100, Kornel Benko wrote:

> I could send you my lyx-executable.

That could give some clues. Should we build .deb packages and trade?

Scott


signature.asc
Description: PGP signature

Re: Crash in File-Open

[Kornel Benko]

Am Dienstag, 21. März 2017 um 10:46:41, schrieb Scott Kostyshak 

> On Sat, Mar 18, 2017 at 12:23:10AM -0400, Scott Kostyshak wrote:
> > On Wed, Mar 15, 2017 at 03:47:31PM +0100, Kornel Benko wrote:
> 
> > > Scott, could you try to check if the binary-provided qt5.8 crashes on 
> > > your system?
> > 
> > Yes I will try this when I'm back to my testing computer (I'm currently
> > traveling).
> 
> I cannot reproduce with the pre-compiled binary for 5.8.
> 
> Attached is output from ldd after compiling with the pre-compiled
> binaries. Note that the path to the pre-compiled binaries for me is (the
> default): /home/scott/Qt/5.8. From what I understand, the output from
> ldd does show that LyX is using the pre-compiled binaries in ~/Qt and
> not my custom-compiled binaries.

My ldd output is lacking some of the libraries.
libexpat.so.1
libxcb-present.so.0
libxcb-sync.so.1
libxshmfence.so.1
libglapi.so.0
libXdamage.so.1
libXfixes.so.3
libX11-xcb.so.1
libxcb-glx.so.0
libxcb-dri2.so.0
libXxf86vm.so.1
libdrm.so.2

But all of them _are_ installed on my pc.

> I used qt-unified-linux-x64-online.run to install, and I selected all of
> the Qt 5.8 components (see attached), and left the default tools
> selected (I think Qt Creator).

Same here.

> I don't have many ideas with how to proceed. I was going to suggest you
> try 5.9.0alpha but there are no binaries for Qt's alphas.

I could send you my lyx-executable.

> You could install Ubuntu on a virtual box and then run the lyx-tester
> script that I use on it. And then instead of using system from the
> repositories (which is what lyx-tester does by default) you can just use
> the pre-compiled binary. I think it would not crash for you (since my
> system is very similar to the one created when running lyx-tester), and
> you could try to see what the difference is between your system and the
> virtual box.
> 
> Scott

Will see.

Kornel

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

Re: Crash in File-Open

[Scott Kostyshak]

On Sat, Mar 18, 2017 at 12:23:10AM -0400, Scott Kostyshak wrote:
> On Wed, Mar 15, 2017 at 03:47:31PM +0100, Kornel Benko wrote:

> > Scott, could you try to check if the binary-provided qt5.8 crashes on your 
> > system?
> 
> Yes I will try this when I'm back to my testing computer (I'm currently
> traveling).

I cannot reproduce with the pre-compiled binary for 5.8.

Attached is output from ldd after compiling with the pre-compiled
binaries. Note that the path to the pre-compiled binaries for me is (the
default): /home/scott/Qt/5.8. From what I understand, the output from
ldd does show that LyX is using the pre-compiled binaries in ~/Qt and
not my custom-compiled binaries.

I used qt-unified-linux-x64-online.run to install, and I selected all of
the Qt 5.8 components (see attached), and left the default tools
selected (I think Qt Creator).

I don't have many ideas with how to proceed. I was going to suggest you
try 5.9.0alpha but there are no binaries for Qt's alphas.

You could install Ubuntu on a virtual box and then run the lyx-tester
script that I use on it. And then instead of using system from the
repositories (which is what lyx-tester does by default) you can just use
the pre-compiled binary. I think it would not crash for you (since my
system is very similar to the one created when running lyx-tester), and
you could try to see what the difference is between your system and the
virtual box.

Scott
scott@kd:~/lyxbuilds/masterQt58/CMakeBuild/bin$ ldd lyx
linux-vdso.so.1 =>  (0x7fff483f4000)
libQt5X11Extras.so.5 => 
/home/scott/Qt/5.8/gcc_64/lib/libQt5X11Extras.so.5 (0x7f741ac3)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 
(0x7f741a9df000)
libhunspell-1.3.so.0 => /usr/lib/x86_64-linux-gnu/libhunspell-1.3.so.0 
(0x7f741a78c000)
libenchant.so.1 => /usr/lib/x86_64-linux-gnu/libenchant.so.1 
(0x7f741a58)
libmagic.so.1 => /usr/lib/x86_64-linux-gnu/libmagic.so.1 
(0x7f741a36)
libQt5Concurrent.so.5 => 
/home/scott/Qt/5.8/gcc_64/lib/libQt5Concurrent.so.5 (0x7f741a158000)
libQt5Svg.so.5 => /home/scott/Qt/5.8/gcc_64/lib/libQt5Svg.so.5 
(0x7f7419f05000)
libQt5Widgets.so.5 => /home/scott/Qt/5.8/gcc_64/lib/libQt5Widgets.so.5 
(0x7f74196d4000)
libQt5Gui.so.5 => /home/scott/Qt/5.8/gcc_64/lib/libQt5Gui.so.5 
(0x7f7418f38000)
libQt5Core.so.5 => /home/scott/Qt/5.8/gcc_64/lib/libQt5Core.so.5 
(0x7f7418818000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f74185fe000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f741827b000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f7417f72000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f7417d5c000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f7417992000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f7417775000)
libGL.so.1 => /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 
(0x7f7417501000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 
(0x7f74172fc000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 
(0x7f74170f6000)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7f7416ef2000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7f7416be)
libicui18n.so.56 => /home/scott/Qt/5.8/gcc_64/lib/libicui18n.so.56 
(0x7f7416747000)
libicuuc.so.56 => /home/scott/Qt/5.8/gcc_64/lib/libicuuc.so.56 
(0x7f741638e000)
libicudata.so.56 => /home/scott/Qt/5.8/gcc_64/lib/libicudata.so.56 
(0x7f74149ab000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f74147a7000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f741459e000)
libgthread-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0 
(0x7f741439c000)
/lib64/ld-linux-x86-64.so.2 (0x561bb1aa4000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 
(0x7f7414172000)
libxcb-dri3.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 
(0x7f7413f6f000)
libxcb-present.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-present.so.0 
(0x7f7413d6c000)
libxcb-sync.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-sync.so.1 
(0x7f7413b64000)
libxshmfence.so.1 => /usr/lib/x86_64-linux-gnu/libxshmfence.so.1 
(0x7f7413961000)
libglapi.so.0 => /usr/lib/x86_64-linux-gnu/libglapi.so.0 
(0x7f7413732000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 
(0x7f741351f000)
libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 
(0x7f741331c000)
libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 
(0x7f7413116000)
libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 
(0x7f7412f13000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 

Re: Crash in File-Open

[Scott Kostyshak]

On Sat, Mar 18, 2017 at 06:09:32PM +0100, Enrico Forestieri wrote:
> On Sat, Mar 18, 2017 at 12:54:44PM -0400, Scott Kostyshak wrote:
> > 
> > What is the difference between the following two (the second removes the
> > prepended "env")?
> > 
> >   env LD_LIBRARY_PATH=/path/to/mylibs prog
> 
> This works whatever your shell.
> 
> > and
> > 
> >   LD_LIBRARY_PATH=/path/to/mylibs prog
> 
> This will not work with tcsh, for example.

Ah good to know.

Scott


signature.asc
Description: PGP signature

Re: Crash in File-Open

[Enrico Forestieri]

On Sat, Mar 18, 2017 at 12:54:44PM -0400, Scott Kostyshak wrote:
> 
> What is the difference between the following two (the second removes the
> prepended "env")?
> 
>   env LD_LIBRARY_PATH=/path/to/mylibs prog

This works whatever your shell.

> and
> 
>   LD_LIBRARY_PATH=/path/to/mylibs prog

This will not work with tcsh, for example.

-- 
Enrico

Re: Crash in File-Open

[Scott Kostyshak]

On Sat, Mar 18, 2017 at 05:43:10PM +0100, Enrico Forestieri wrote:
> On Sat, Mar 18, 2017 at 11:56:25AM -0400, Scott Kostyshak wrote:
> 
> > On Sat, Mar 18, 2017 at 08:26:05AM +0100, Kornel Benko wrote:
> > 
> > > Yes, this is sufficient.
> > > If you want to switch more often, you should create a script.
> > > I have a symbolic link, /usr/BUILD/BuildQt, pointing to the correct QT.
> > > And in /etc/ld.so.conf.d/qt5.conf the first line reads
> > >   /usr/BUILD/BuildQtRoot/lib
> > > 
> > > Also the env PATH contains /usr/BUILD/BuildQtRoot/bin.
> > > 
> > > In case of using built-in qt, /usr/BUILD/BuildQtRoot is removed.
> > > 
> > > But to be sure, I always also use 'sudo ldconfig' too.
> > 
> > OK thanks for the info.
> 
> You can always launch a program "prog" by
> 
> env LD_LIBRARY_PATH=/path/to/mylibs prog
> 
> to force using the libraries in /path/to/mylibs without tinkering
> with ld configuration.

Good idea, and since Kornel said the problem shows only when the
libraries are used at run time (and doesn't matter for compile time),
that seems like the easiest way to test.

What is the difference between the following two (the second removes the
prepended "env")?

  env LD_LIBRARY_PATH=/path/to/mylibs prog

and

  LD_LIBRARY_PATH=/path/to/mylibs prog

Scott


signature.asc
Description: PGP signature

Re: Crash in File-Open

[Enrico Forestieri]

On Sat, Mar 18, 2017 at 11:56:25AM -0400, Scott Kostyshak wrote:

> On Sat, Mar 18, 2017 at 08:26:05AM +0100, Kornel Benko wrote:
> 
> > Yes, this is sufficient.
> > If you want to switch more often, you should create a script.
> > I have a symbolic link, /usr/BUILD/BuildQt, pointing to the correct QT.
> > And in /etc/ld.so.conf.d/qt5.conf the first line reads
> > /usr/BUILD/BuildQtRoot/lib
> > 
> > Also the env PATH contains /usr/BUILD/BuildQtRoot/bin.
> > 
> > In case of using built-in qt, /usr/BUILD/BuildQtRoot is removed.
> > 
> > But to be sure, I always also use 'sudo ldconfig' too.
> 
> OK thanks for the info.

You can always launch a program "prog" by

env LD_LIBRARY_PATH=/path/to/mylibs prog

to force using the libraries in /path/to/mylibs without tinkering
with ld configuration.

-- 
Enrico

Re: Crash in File-Open

[Scott Kostyshak]

On Sat, Mar 18, 2017 at 08:26:05AM +0100, Kornel Benko wrote:

> Yes, this is sufficient.
> If you want to switch more often, you should create a script.
> I have a symbolic link, /usr/BUILD/BuildQt, pointing to the correct QT.
> And in /etc/ld.so.conf.d/qt5.conf the first line reads
>   /usr/BUILD/BuildQtRoot/lib
> 
> Also the env PATH contains /usr/BUILD/BuildQtRoot/bin.
> 
> In case of using built-in qt, /usr/BUILD/BuildQtRoot is removed.
> 
> But to be sure, I always also use 'sudo ldconfig' too.

OK thanks for the info.

Scott


signature.asc
Description: PGP signature

Re: Crash in File-Open

[Kornel Benko]

Am Samstag, 18. März 2017 um 00:23:10, schrieb Scott Kostyshak 

> On Wed, Mar 15, 2017 at 03:47:31PM +0100, Kornel Benko wrote:
> > Am Samstag, 11. März 2017 um 22:29:58, schrieb Kornel Benko 
> > > Am Samstag, 11. März 2017 um 14:47:37, schrieb Scott Kostyshak 
> > > 
> > > > On Mon, Mar 06, 2017 at 07:09:16PM -0500, Scott Kostyshak wrote:
> > > > > On Mon, Mar 06, 2017 at 12:19:48PM +0100, Kornel Benko wrote:
> > > > > 
> > > > > > Looks like nobody seems to to be interested.
> > > > > 
> > > > > I'm interested and will test in a week when I'm home and have access 
> > > > > to
> > > > > the computer where I have Qt 5.8 installed.
> > > > 
> > > > I can't reproduce with Qt 5.8.1dev (compiled a few weeks ago).
> > > > 
> > > > Scott
> > > 
> > > I tried to compile Qt 5.9.0-alpha, but unfortunately I was unable to do 
> > > it.
> > > Did not even come trough the configuration phase
> > > (You cannot configure qt separately within a top-level build)
> > > 
> > > Should probably try with Qt 5.8.
> > > 
> > >   Kornel
> > 
> > Next try was to compile QT5.8 from source. Now lyx does not crash.
> > 
> > Scott, could you try to check if the binary-provided qt5.8 crashes on your 
> > system?
> 
> Yes I will try this when I'm back to my testing computer (I'm currently
> traveling). I will have to make sure that my custom compiled Qt does not
> interfere. Do I just need to edit
> 
>   /etc/ld.so.conf.d/qt5.conf
> 
> and run
> 
>   sudo ldconfig
> 
> ?
> 
> Scott

Yes, this is sufficient.
If you want to switch more often, you should create a script.
I have a symbolic link, /usr/BUILD/BuildQt, pointing to the correct QT.
And in /etc/ld.so.conf.d/qt5.conf the first line reads
/usr/BUILD/BuildQtRoot/lib

Also the env PATH contains /usr/BUILD/BuildQtRoot/bin.

In case of using built-in qt, /usr/BUILD/BuildQtRoot is removed.

But to be sure, I always also use 'sudo ldconfig' too.

Kornel



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

Re: Crash in File-Open

[Scott Kostyshak]

On Wed, Mar 15, 2017 at 03:47:31PM +0100, Kornel Benko wrote:
> Am Samstag, 11. März 2017 um 22:29:58, schrieb Kornel Benko 
> > Am Samstag, 11. März 2017 um 14:47:37, schrieb Scott Kostyshak 
> > 
> > > On Mon, Mar 06, 2017 at 07:09:16PM -0500, Scott Kostyshak wrote:
> > > > On Mon, Mar 06, 2017 at 12:19:48PM +0100, Kornel Benko wrote:
> > > > 
> > > > > Looks like nobody seems to to be interested.
> > > > 
> > > > I'm interested and will test in a week when I'm home and have access to
> > > > the computer where I have Qt 5.8 installed.
> > > 
> > > I can't reproduce with Qt 5.8.1dev (compiled a few weeks ago).
> > > 
> > > Scott
> > 
> > I tried to compile Qt 5.9.0-alpha, but unfortunately I was unable to do it.
> > Did not even come trough the configuration phase
> > (You cannot configure qt separately within a top-level build)
> > 
> > Should probably try with Qt 5.8.
> > 
> > Kornel
> 
> Next try was to compile QT5.8 from source. Now lyx does not crash.
> 
> Scott, could you try to check if the binary-provided qt5.8 crashes on your 
> system?

Yes I will try this when I'm back to my testing computer (I'm currently
traveling). I will have to make sure that my custom compiled Qt does not
interfere. Do I just need to edit

  /etc/ld.so.conf.d/qt5.conf

and run

  sudo ldconfig

?

Scott


signature.asc
Description: PGP signature

Re: Crash in File-Open

[Kornel Benko]

Am Samstag, 11. März 2017 um 22:29:58, schrieb Kornel Benko 
> Am Samstag, 11. März 2017 um 14:47:37, schrieb Scott Kostyshak 
> 
> > On Mon, Mar 06, 2017 at 07:09:16PM -0500, Scott Kostyshak wrote:
> > > On Mon, Mar 06, 2017 at 12:19:48PM +0100, Kornel Benko wrote:
> > > 
> > > > Looks like nobody seems to to be interested.
> > > 
> > > I'm interested and will test in a week when I'm home and have access to
> > > the computer where I have Qt 5.8 installed.
> > 
> > I can't reproduce with Qt 5.8.1dev (compiled a few weeks ago).
> > 
> > Scott
> 
> I tried to compile Qt 5.9.0-alpha, but unfortunately I was unable to do it.
> Did not even come trough the configuration phase
> (You cannot configure qt separately within a top-level build)
> 
> Should probably try with Qt 5.8.
> 
>   Kornel

Next try was to compile QT5.8 from source. Now lyx does not crash.

Scott, could you try to check if the binary-provided qt5.8 crashes on your 
system?

Kornel

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

Re: Crash in File-Open

[Kornel Benko]

Am Samstag, 11. März 2017 um 14:47:37, schrieb Scott Kostyshak 

> On Mon, Mar 06, 2017 at 07:09:16PM -0500, Scott Kostyshak wrote:
> > On Mon, Mar 06, 2017 at 12:19:48PM +0100, Kornel Benko wrote:
> > 
> > > Looks like nobody seems to to be interested.
> > 
> > I'm interested and will test in a week when I'm home and have access to
> > the computer where I have Qt 5.8 installed.
> 
> I can't reproduce with Qt 5.8.1dev (compiled a few weeks ago).
> 
> Scott

I tried to compile Qt 5.9.0-alpha, but unfortunately I was unable to do it.
Did not even come trough the configuration phase
(You cannot configure qt separately within a top-level build)

Should probably try with Qt 5.8.

Kornel

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

Re: Crash in File-Open

[Scott Kostyshak]

On Mon, Mar 06, 2017 at 07:09:16PM -0500, Scott Kostyshak wrote:
> On Mon, Mar 06, 2017 at 12:19:48PM +0100, Kornel Benko wrote:
> 
> > Looks like nobody seems to to be interested.
> 
> I'm interested and will test in a week when I'm home and have access to
> the computer where I have Qt 5.8 installed.

I can't reproduce with Qt 5.8.1dev (compiled a few weeks ago).

Scott


signature.asc
Description: PGP signature

Re: Crash in File-Open

[Scott Kostyshak]

On Mon, Mar 06, 2017 at 12:19:48PM +0100, Kornel Benko wrote:

> Looks like nobody seems to to be interested.

I'm interested and will test in a week when I'm home and have access to
the computer where I have Qt 5.8 installed.

Scott


signature.asc
Description: PGP signature

Re: Crash in File-Open

[Kornel Benko]

Am Montag, 6. März 2017 um 23:14:34, schrieb Kornel Benko 
> Am Montag, 6. März 2017 um 22:02:11, schrieb Enrico Forestieri 
> 
> > On Mon, Mar 06, 2017 at 09:11:08PM +0100, Kornel Benko wrote:
> > > 
> > > Nice, what is the version of your debian? Which desktop?
> > 
> > Debian jessie, gnome.
> > 
> > > Googling implies that this may be important.
> > > But nothing I tried helped here.
> > 
> > I only found this:
> > https://www.qcad.org/bugtracker/index.php?do=details_id=1545
> > but they actually state that Qt 5.8 fixes it...
> > 
> 
> Apparently not completely. The article is about Mint18.1, my machine is Mint 
> 17.3.
> But one point may be important. Switching to QT5.8, I never restarted the 
> session.
> 
> Will try.
> 

OK, it does not help. Maybe with the mentioned new snapshot in this bugtracker 
for QT5.8 things will
improve.

Kornel

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

Re: Crash in File-Open

[Kornel Benko]

Am Montag, 6. März 2017 um 22:02:11, schrieb Enrico Forestieri 
> On Mon, Mar 06, 2017 at 09:11:08PM +0100, Kornel Benko wrote:
> > 
> > Nice, what is the version of your debian? Which desktop?
> 
> Debian jessie, gnome.
> 
> > Googling implies that this may be important.
> > But nothing I tried helped here.
> 
> I only found this:
> https://www.qcad.org/bugtracker/index.php?do=details_id=1545
> but they actually state that Qt 5.8 fixes it...
> 

Apparently not completely. The article is about Mint18.1, my machine is Mint 
17.3.
But one point may be important. Switching to QT5.8, I never restarted the 
session.

Will try.

Kornel

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

Re: Crash in File-Open

[Enrico Forestieri]

On Mon, Mar 06, 2017 at 09:11:08PM +0100, Kornel Benko wrote:
> 
> Nice, what is the version of your debian? Which desktop?

Debian jessie, gnome.

> Googling implies that this may be important.
> But nothing I tried helped here.

I only found this:
https://www.qcad.org/bugtracker/index.php?do=details_id=1545
but they actually state that Qt 5.8 fixes it...

-- 
Enrico

Re: Crash in File-Open

[Kornel Benko]

Am Montag, 6. März 2017 um 18:27:36, schrieb Enrico Forestieri 
> On Mon, Mar 06, 2017 at 11:45:00AM -0500, Richard Heck wrote:
> > On 03/06/2017 06:19 AM, Kornel Benko wrote:
> > > Ping ...
> > >
> > > Am Donnerstag, 23. Februar 2017 um 13:52:41, schrieb Kornel Benko 
> > > 
> > >> OS: Linux =~ ubuntu 14.04, 64bit
> > >>
> > >> I gave a try to QT5.8. But now I am getting crashes any time I try to 
> > >> open a file with File->Open.
> > >> This does not happen with 'open recent' or if lyx is called with a file 
> > >> parameter.
> > >>
> > >> The backtrace shows that the crash in call to dmg.exec() 
> > >> src/frontends/qt4/FileDialog.cpp:161
> > >>
> > >> The enclosing routine, FileDialog::open(path, filters suggested)
> > >>  path = toqstr(".")
> > >>  filters = filter(qt_("LyX Documents (*.lyx)")
> > >> so nothing special.
> > >>
> > >> If I try to use lyx compiled with QT5.7, so the crash is there too as 
> > >> long as QT5.8 is selected by ldconfig.
> > >> If I try to use lyx compiled with QT5.8 ans select QT5.7 with ldconfig, 
> > >> lyx does not start because
> > >> `Qt_5.8' is not found.
> > >>
> > >> Someone interested in backtrace?
> > >>
> > >> I try to compile with automake ...
> > >> Compilation went smoothly.
> > >> But I have the same effect. So at least it does not depend on 
> > >> build-system.
> > >>
> > > Looks like nobody seems to to be interested.
> > > For me, the only workaround is to use USE_NATIVE_FILEDIALOG=1.
> > > I don't like it because the native dialog is not so nice as that from LyX,
> > > but at least the so compiled lyx is usable.
> > >
> > > Attached patch is for cmake build.
> > >
> > > The same change is needed here for branch2.2.
> > 
> > OK for stable.
> 
> I think that this needs some investigation. I cannot reproduce the
> behavior on debian with Qt 5.8.
> 

Nice, what is the version of your debian? Which desktop? Googling implies that 
this may be important.
But nothing I tried helped here.

Kornel

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

Re: Crash in File-Open

[Enrico Forestieri]

On Mon, Mar 06, 2017 at 11:45:00AM -0500, Richard Heck wrote:
> On 03/06/2017 06:19 AM, Kornel Benko wrote:
> > Ping ...
> >
> > Am Donnerstag, 23. Februar 2017 um 13:52:41, schrieb Kornel Benko 
> > 
> >> OS: Linux =~ ubuntu 14.04, 64bit
> >>
> >> I gave a try to QT5.8. But now I am getting crashes any time I try to open 
> >> a file with File->Open.
> >> This does not happen with 'open recent' or if lyx is called with a file 
> >> parameter.
> >>
> >> The backtrace shows that the crash in call to dmg.exec() 
> >> src/frontends/qt4/FileDialog.cpp:161
> >>
> >> The enclosing routine, FileDialog::open(path, filters suggested)
> >>path = toqstr(".")
> >>filters = filter(qt_("LyX Documents (*.lyx)")
> >> so nothing special.
> >>
> >> If I try to use lyx compiled with QT5.7, so the crash is there too as long 
> >> as QT5.8 is selected by ldconfig.
> >> If I try to use lyx compiled with QT5.8 ans select QT5.7 with ldconfig, 
> >> lyx does not start because
> >> `Qt_5.8' is not found.
> >>
> >> Someone interested in backtrace?
> >>
> >> I try to compile with automake ...
> >> Compilation went smoothly.
> >> But I have the same effect. So at least it does not depend on build-system.
> >>
> > Looks like nobody seems to to be interested.
> > For me, the only workaround is to use USE_NATIVE_FILEDIALOG=1.
> > I don't like it because the native dialog is not so nice as that from LyX,
> > but at least the so compiled lyx is usable.
> >
> > Attached patch is for cmake build.
> >
> > The same change is needed here for branch2.2.
> 
> OK for stable.

I think that this needs some investigation. I cannot reproduce the
behavior on debian with Qt 5.8.

-- 
Enrico

Re: Crash in File-Open

[Richard Heck]

On 03/06/2017 06:19 AM, Kornel Benko wrote:
> Ping ...
>
> Am Donnerstag, 23. Februar 2017 um 13:52:41, schrieb Kornel Benko 
> 
>> OS: Linux =~ ubuntu 14.04, 64bit
>>
>> I gave a try to QT5.8. But now I am getting crashes any time I try to open a 
>> file with File->Open.
>> This does not happen with 'open recent' or if lyx is called with a file 
>> parameter.
>>
>> The backtrace shows that the crash in call to dmg.exec() 
>> src/frontends/qt4/FileDialog.cpp:161
>>
>> The enclosing routine, FileDialog::open(path, filters suggested)
>>  path = toqstr(".")
>>  filters = filter(qt_("LyX Documents (*.lyx)")
>> so nothing special.
>>
>> If I try to use lyx compiled with QT5.7, so the crash is there too as long 
>> as QT5.8 is selected by ldconfig.
>> If I try to use lyx compiled with QT5.8 ans select QT5.7 with ldconfig, lyx 
>> does not start because
>> `Qt_5.8' is not found.
>>
>> Someone interested in backtrace?
>>
>> I try to compile with automake ...
>> Compilation went smoothly.
>> But I have the same effect. So at least it does not depend on build-system.
>>
> Looks like nobody seems to to be interested.
> For me, the only workaround is to use USE_NATIVE_FILEDIALOG=1.
> I don't like it because the native dialog is not so nice as that from LyX,
> but at least the so compiled lyx is usable.
>
> Attached patch is for cmake build.
>
> The same change is needed here for branch2.2.

OK for stable.

rh

Re: Crash in File-Open

[Kornel Benko]

Ping ...

Am Donnerstag, 23. Februar 2017 um 13:52:41, schrieb Kornel Benko 

> OS: Linux =~ ubuntu 14.04, 64bit
>
> I gave a try to QT5.8. But now I am getting crashes any time I try to open a 
> file with File->Open.
> This does not happen with 'open recent' or if lyx is called with a file 
> parameter.
>
> The backtrace shows that the crash in call to dmg.exec() 
> src/frontends/qt4/FileDialog.cpp:161
>
> The enclosing routine, FileDialog::open(path, filters suggested)
>   path = toqstr(".")
>   filters = filter(qt_("LyX Documents (*.lyx)")
> so nothing special.
>
> If I try to use lyx compiled with QT5.7, so the crash is there too as long as 
> QT5.8 is selected by ldconfig.
> If I try to use lyx compiled with QT5.8 ans select QT5.7 with ldconfig, lyx 
> does not start because
> `Qt_5.8' is not found.
>
> Someone interested in backtrace?
>
> I try to compile with automake ...
> Compilation went smoothly.
> But I have the same effect. So at least it does not depend on build-system.
>

Looks like nobody seems to to be interested.
For me, the only workaround is to use USE_NATIVE_FILEDIALOG=1.
I don't like it because the native dialog is not so nice as that from LyX,
but at least the so compiled lyx is usable.

Attached patch is for cmake build.

The same change is needed here for branch2.2.

Korneldiff --git a/src/frontends/qt4/CMakeLists.txt b/src/frontends/qt4/CMakeLists.txt
index 833e92a..4a3331d 100644
--- a/src/frontends/qt4/CMakeLists.txt
+++ b/src/frontends/qt4/CMakeLists.txt
@@ -7,6 +7,9 @@
 project(frontend_qt)

 file(GLOB frontends_qt_sources ${TOP_SRC_DIR}/src/frontends/qt4/${LYX_CPP_FILES})
+if (QTVERSION VERSION_GREATER_EQUAL "5.8.0")
+  set_property(SOURCE "${TOP_SRC_DIR}/src/frontends/qt4/FileDialog.cpp" PROPERTY COMPILE_FLAGS -DUSE_NATIVE_FILEDIALOG=1)
+endif()
 file(GLOB moc_files ${TOP_SRC_DIR}/src/frontends/qt4/${LYX_MOC_FILES})

 list(REMOVE_ITEM frontends_qt_sources ${moc_files} .)


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

Crash in File-Open

[Kornel Benko]

OS: Linux =~ ubuntu 14.04, 64bit

I gave a try to QT5.8. But now I am getting crashes any time I try to open a 
file with File->Open.
This does not happen with 'open recent' or if lyx is called with a file 
parameter.

The backtrace shows that the crash in call to dmg.exec() 
src/frontends/qt4/FileDialog.cpp:161

The enclosing routine, FileDialog::open(path, filters suggested)
path = toqstr(".")
filters = filter(qt_("LyX Documents (*.lyx)")
so nothing special.

If I try to use lyx compiled with QT5.7, so the crash is there too as long as 
QT5.8 is selected by ldconfig.
If I try to use lyx compiled with QT5.8 ans select QT5.7 with ldconfig, lyx 
does not start because
`Qt_5.8' is not found.

Someone interested in backtrace?

I try to compile with automake ...
Compilation went smoothly.
But I have the same effect. So at least it does not depend on build-system.

Kornel



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

1.6svn repeatable crash in file-open dialog

[Helge Hafting]

Compile, run without installing.
file-open
When I type /www/www.aitel.hist.no/
then lyx dies with this message:

ASSERT failure in QListT::at: index out of range, file 
../../include/QtCore/../../src/corelib/tools/qlist.h, line 386


as soon as I type the last slash. I can paste in the full
path I want, but typing this kills LyX everytime.

Backtrace:
#0  0xa7f62410 in __kernel_vsyscall ()
#1  0xa6f1a7f5 in raise () from /lib/i686/cmov/libc.so.6
#2  0xa6f1c181 in abort () from /lib/i686/cmov/libc.so.6
#3  0xa74f2fdd in qt_message_output (msgType=QtFatalMsg,
   buf=0xafc8b2d0 ASSERT failure in QListT::at: \index out of 
range\, file ../../include/QtCore/../../src/corelib/tools/qlist.h, line 
386) at global/qglobal.cpp:2160
#4  0xa74f3041 in qFatal (msg=0xa75e8f3c ASSERT failure in %s: \%s\, 
file %s, line %d) at global/qglobal.cpp:2391
#5  0xa74f3086 in qt_assert_x (where=0xa7dbf7f9 QListT::at, 
what=0xa7dbf79f index out of range,
   file=0xa7dbf7c4 
../../include/QtCore/../../src/corelib/tools/qlist.h, line=386) at 
global/qglobal.cpp:1927
#6  0xa78447d8 in QListint::at (this=0x8b5cd3c, i=-1) at 
../../include/QtCore/../../src/corelib/tools/qlist.h:386
#7  0xa7c9faab in QFileSystemModelPrivate::_q_fileSystemChanged 
(this=0x8b47498, [EMAIL PROTECTED], [EMAIL PROTECTED])

   at dialogs/qfilesystemmodel.cpp:1491
#8  0xa7db8aac in QFileSystemModel::qt_metacall (this=0x8a40498, 
_c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x8afae30)

   at .moc/debug-shared/moc_qfilesystemmodel_p.cpp:86
#9  0xa75bd810 in QMetaCallEvent::placeMetaCall (this=0x8b8aa30, 
object=0x8a40498) at kernel/qobject.cpp:538
#10 0xa75c29fb in QObject::event (this=0x8a40498, e=0x8b8aa30) at 
kernel/qobject.cpp:1130
#11 0xa7814af1 in QApplicationPrivate::notify_helper (this=0x87de0f0, 
receiver=0x8a40498, e=0x8b8aa30)

   at kernel/qapplication.cpp:3558
#12 0xa7814e0a in QApplication::notify (this=0x87d99f8, 
receiver=0x8a40498, e=0x8b8aa30) at kernel/qapplication.cpp:3117
#13 0x084226c0 in lyx::frontend::GuiApplication::notify (this=0x87d99f8, 
receiver=0x8a40498, event=0x8b8aa30)

   at ../../../../lyx-devel/src/frontends/qt4/GuiApplication.cpp:254
#14 0xa75b088e in QCoreApplication::notifyInternal (this=0x87d99f8, 
receiver=0x8a40498, event=0x8b8aa30)

   at kernel/qcoreapplication.cpp:532
#15 0xa75b3c57 in QCoreApplication::sendEvent (receiver=0x8a40498, 
event=0x8b8aa30)

   at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:202
#16 0xa75b0d65 in QCoreApplicationPrivate::sendPostedEvents 
(receiver=0x0, event_type=0, data=0x87b3d98)

   at kernel/qcoreapplication.cpp:1106
#17 0xa75b0ebb in QCoreApplication::sendPostedEvents (receiver=0x0, 
event_type=-1) at kernel/qcoreapplication.cpp:994
#18 0xa75d9ff4 in postEventSourceDispatch (s=0x87db148) at 
kernel/qeventdispatcher_glib.cpp:209

#19 0xa741ed6c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xa742219f in ?? () from /usr/lib/libglib-2.0.so.0
#21 0x087db0c8 in ?? ()
#22 0x in ?? ()


A qt4 problem, or LyX?

Helge Hafting

1.6svn repeatable crash in file->open dialog

[Helge Hafting]

Compile, run without installing.
file->open
When I type "/www/www.aitel.hist.no/"
then lyx dies with this message:

ASSERT failure in QList::at: "index out of range", file 
../../include/QtCore/../../src/corelib/tools/qlist.h, line 386


as soon as I type the last slash. I can paste in the full
path I want, but typing this kills LyX everytime.

Backtrace:
#0  0xa7f62410 in __kernel_vsyscall ()
#1  0xa6f1a7f5 in raise () from /lib/i686/cmov/libc.so.6
#2  0xa6f1c181 in abort () from /lib/i686/cmov/libc.so.6
#3  0xa74f2fdd in qt_message_output (msgType=QtFatalMsg,
   buf=0xafc8b2d0 "ASSERT failure in QList::at: \"index out of 
range\", file ../../include/QtCore/../../src/corelib/tools/qlist.h, line 
386") at global/qglobal.cpp:2160
#4  0xa74f3041 in qFatal (msg=0xa75e8f3c "ASSERT failure in %s: \"%s\", 
file %s, line %d") at global/qglobal.cpp:2391
#5  0xa74f3086 in qt_assert_x (where=0xa7dbf7f9 "QList::at", 
what=0xa7dbf79f "index out of range",
   file=0xa7dbf7c4 
"../../include/QtCore/../../src/corelib/tools/qlist.h", line=386) at 
global/qglobal.cpp:1927
#6  0xa78447d8 in QList::at (this=0x8b5cd3c, i=-1) at 
../../include/QtCore/../../src/corelib/tools/qlist.h:386
#7  0xa7c9faab in QFileSystemModelPrivate::_q_fileSystemChanged 
(this=0x8b47498, [EMAIL PROTECTED], [EMAIL PROTECTED])

   at dialogs/qfilesystemmodel.cpp:1491
#8  0xa7db8aac in QFileSystemModel::qt_metacall (this=0x8a40498, 
_c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x8afae30)

   at .moc/debug-shared/moc_qfilesystemmodel_p.cpp:86
#9  0xa75bd810 in QMetaCallEvent::placeMetaCall (this=0x8b8aa30, 
object=0x8a40498) at kernel/qobject.cpp:538
#10 0xa75c29fb in QObject::event (this=0x8a40498, e=0x8b8aa30) at 
kernel/qobject.cpp:1130
#11 0xa7814af1 in QApplicationPrivate::notify_helper (this=0x87de0f0, 
receiver=0x8a40498, e=0x8b8aa30)

   at kernel/qapplication.cpp:3558
#12 0xa7814e0a in QApplication::notify (this=0x87d99f8, 
receiver=0x8a40498, e=0x8b8aa30) at kernel/qapplication.cpp:3117
#13 0x084226c0 in lyx::frontend::GuiApplication::notify (this=0x87d99f8, 
receiver=0x8a40498, event=0x8b8aa30)

   at ../../../../lyx-devel/src/frontends/qt4/GuiApplication.cpp:254
#14 0xa75b088e in QCoreApplication::notifyInternal (this=0x87d99f8, 
receiver=0x8a40498, event=0x8b8aa30)

   at kernel/qcoreapplication.cpp:532
#15 0xa75b3c57 in QCoreApplication::sendEvent (receiver=0x8a40498, 
event=0x8b8aa30)

   at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:202
#16 0xa75b0d65 in QCoreApplicationPrivate::sendPostedEvents 
(receiver=0x0, event_type=0, data=0x87b3d98)

   at kernel/qcoreapplication.cpp:1106
#17 0xa75b0ebb in QCoreApplication::sendPostedEvents (receiver=0x0, 
event_type=-1) at kernel/qcoreapplication.cpp:994
#18 0xa75d9ff4 in postEventSourceDispatch (s=0x87db148) at 
kernel/qeventdispatcher_glib.cpp:209

#19 0xa741ed6c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xa742219f in ?? () from /usr/lib/libglib-2.0.so.0
#21 0x087db0c8 in ?? ()
#22 0x in ?? ()


A qt4 problem, or LyX?

Helge Hafting