Andre Poenitz <[EMAIL PROTECTED]> writes:
>> > Which reminds me: I'd like to have 1.6.0 shipped with 'non-fatal
>> > asserts'.
>>
>> You mean instead of 'no asserts' as it is now?
>
> Yes.
Why not...
JMarc
On Fri, Mar 21, 2008 at 11:36:57PM +0100, Jean-Marc Lasgouttes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> > Which reminds me: I'd like to have 1.6.0 shipped with 'non-fatal
> > asserts'.
>
> You mean instead of 'no asserts' as it is now?
Yes.
Andre'
Andre Poenitz <[EMAIL PROTECTED]> writes:
> Which reminds me: I'd like to have 1.6.0 shipped with 'non-fatal
> asserts'.
You mean instead of 'no asserts' as it is now?
JMarc
On Fri, Mar 21, 2008 at 06:03:45PM +0100, Pavel Sanda wrote:
> errrm, crash in branch.
>
> > 1. insert figure float
> > 2. click on its label via middle mouse button.
> > 3. kaboom
> >
> > Program received signal SIGABRT, Aborted.
> > 0xe410 in __kernel_vsyscall ()
> > (gdb) bt
> > #0 0x
Pavel Sanda wrote:
> is the inset in uncollapsed state, yes?
yes.
What happens is that the Clipboard text is pasted before the inset (which is
what I'd expect).
Jürgen
> Pavel Sanda wrote:
> > errrm, crash in branch.
>
> cannot reproduce.
is the inset in uncollapsed state, yes?
pavel
Pavel Sanda wrote:
> errrm, crash in branch.
cannot reproduce.
Jürgen
errrm, crash in branch.
> 1. insert figure float
> 2. click on its label via middle mouse button.
> 3. kaboom
>
> Program received signal SIGABRT, Aborted.
> 0xe410 in __kernel_vsyscall ()
> (gdb) bt
> #0 0xe410 in __kernel_vsyscall ()
> #1 0xb705d101 in raise () from /lib/libc.so.6
> #
>> more observations:
>> -its under 1.5.5svn, cant reprudoce under 1.5.4.
>>
> fortunately its not under 1.6svn. there is one litte
> strange thing still - when you open such kind of file twice
> it creates two new files of the same name.
>
Please f
rgheck wrote:
rgheck wrote:
Juergen Spitzmueller wrote:
Pavel Sanda wrote:
more observations:
-its under 1.5.5svn, cant reprudoce under 1.5.4.
fortunately its not under 1.6svn. there is one litte
strange thing still - when you open such kind of file twice
it creates two new files of
rgheck wrote:
Juergen Spitzmueller wrote:
Pavel Sanda wrote:
more observations:
-its under 1.5.5svn, cant reprudoce under 1.5.4.
fortunately its not under 1.6svn. there is one litte
strange thing still - when you open such kind of file twice
it creates two new files of the same name.
rgheck wrote:
> I can also get it this way: Open a file; open the outliner; now
> File>Open "nonexistent.lyx":
can you try if reverting the following commit fixes the issue?
http://www.lyx.org/trac/changeset/23444
Jürgen
Juergen Spitzmueller wrote:
Pavel Sanda wrote:
more observations:
-its under 1.5.5svn, cant reprudoce under 1.5.4.
fortunately its not under 1.6svn. there is one litte
strange thing still - when you open such kind of file twice
it creates two new files of the same name.
Please
Pavel Sanda wrote:
>> more observations:
>> -its under 1.5.5svn, cant reprudoce under 1.5.4.
>
> fortunately its not under 1.6svn. there is one litte
> strange thing still - when you open such kind of file twice
> it creates two new files of the same name.
Please file a report with target 1.5.5.
> more observations:
> -its under 1.5.5svn, cant reprudoce under 1.5.4.
fortunately its not under 1.6svn. there is one litte
strange thing still - when you open such kind of file twice
it creates two new files of the same name.
pavel
> > 1. launch lyx, save file x, close lyx
> > 2. launch lyx, open file y, open outliner
> > 3. remove file x from disk
> > 4. try to open file x from file recent menu
> > 5. crash
> >
> > can anybody confirm?
>
> No (I get an empty file x).
> Do you have a backtrace?
that is the strange thing -
Pavel Sanda wrote:
> 1. launch lyx, save file x, close lyx
> 2. launch lyx, open file y, open outliner
> 3. remove file x from disk
> 4. try to open file x from file recent menu
> 5. crash
>
> can anybody confirm?
No (I get an empty file x).
Do you have a backtrace?
Jürgen
17 matches
Mail list logo
