Am 20.03.2019 um 02:21 schrieb Richard Kimberly Heck:
> On 3/19/19 4:32 PM, Jürgen Womser-Schütz wrote:
>> Am 19.03.2019 um 20:05 schrieb Scott Kostyshak:
>>> On Tue, Mar 19, 2019 at 01:57:03PM -0400, Richard Kimberly Heck wrote:
>>>> We're about three months past 2.3.2, so time to start thinking about the
>>>> next release. We have collected a decent number of fixes since then
>>>> (though it seems a lot of us have been pretty busy). Are there any
>>>> must-haves for 2.3.3?
>>> Not a must-have (e.g., not a regression), but I wonder if we should
>>> consider putting in the patch that you proposed for
>>>
>>> https://www.lyx.org/trac/ticket/10091
>>>
>>> That ticket seems to affect a lot of people. From what I understand, no
>>> one has tested the patch. We could include it and make a test Windows
>>> installer and ask for testers. I think I remember you saying that you
>>> wanted to make a test installer anyways (but this is a very vague memory
>>> so perhaps I just made that up). In any case, this would be even more
>>> work for you, Riki, so if your plate is full then I'm fine with just
>>> skipping this.
>>>
>>> Scott
>> I am using Lyx 2.3.2-2/Win10 but I am not using Dropbox at the moment.
>> If it is helpful I could try to reproduce this error with a Dropbox
>> Basic account.
>> And supposed I am successful with this I could also try a LyX
>> test-version with your patch.
> Yes, that would be very, very helpful.
>
> I do have access to a Windows installation and so could test to confirm
> if it works, but I don't know enough to be confident doing this on my own.
>
> Riki
Hi,
this is the 2. try to send this Mail. The 1. seemed not to be transmitted.
Now I drop the attachements (1.3MB screenshots). May be it is working now.
Jürgen (JWS)
Hi all,
I tried out saving a large LyX-file (UsersGuide.lyx) in my just created
Dropbox folder but I could not reproduce the issues from ticket 10091.
Instead I got 3 different kind of reproduceable issues:
1. A segment violation (see attached LyX-Dropbox-Save-Error-2.JPG).
2. An software assertion "Buffer-error" (see
LyX-Dropbox-Save-Error-3.JPG).
The assertion seems to be thrown in the following function (in
Line 3606):
Inset const & Paragraph::inInset() const
{
LBUFERR(d->inset_owner_); // Line 3606
return *d->inset_owner_;
}
3. Furthermore I got a reproduceable segment violation by saving the
file onto my fixed disk (see LyX-Dropbox-Save-Error-4.JPG).
In this case the temporarily file "UserGuide-xxxxx.lyx" was
successful written as you can see in the bottom LyX status line.
As mentioned I use a LyX 2.3.2-2/Win10-64Bit system.
What is the next step for solving the issue(s)above?
I see 2 possibilities:
1. I try to build LyX on my system and hopefully I can debug and fix it.
2. I can try a Test-Installer for Windows with Rikis
"0001-Fix-bug-10091.patch" includet.
Disadvantage for point 1: It would take a very long time because I am
not familiar with the LyX buildsystem (neither Win nor Linux).
Disadvantage for point 2: Someone (Riki?) has to build an Windows
installer and maybe the problem still stayed.
What do you think? I am happy with both possibilities.
Another problem for me is: for testing on my Linux-system I did the
following steps:
checkout 2.3.2
make clean
sh autogen.sh
./configure
But the ./configure-step stopped with
"configure: error: cannot compile a simple Qt executable. Check you
have the right $QTDIR."
Maybe I forgot a step? Do you have any suggestion for me?
Jürgen (JWS)
