Re: Bug in Lyx 1.3.4 ?

[Stephan Witt]

> Am 05.02.2020 um 23:33 schrieb emile lunardon :
> 
> I have installed LyX 2.3.4 on Windows10 and the same crash already seen on 
> LyX for Linux occurs when trying to enter the two Math Symbols : 
> $\textrm{Ø}\textrm{Å}$
> 
> Le mer. 5 févr. 2020 à 08:32, emile lunardon  a 
> écrit :
> When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols 
> shown in the attached file (written with LyX 1.3.3), there is a crash of LyX 
> 1.3.4 with the attached messages.
> 
> Can someone confirm this strange phenomena ?

I can confirm your bug with Qt5 on macOS with LyX 2.3.4. I think this is the 
version you’re talking about all the time.

One has to use the math toolbar and there choose the symbol Å from the 
miscellaneous pane.

The backtrace is:

(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS 
(code=1, address=0x18)
frame #0: 0x0001000699dc 
LyX`lyx::Buffer::params(this=0x) at Buffer.cpp:719:9
frame #1: 0x00010079fa18 LyX`lyx::(anonymous 
namespace)::Parser::parse1(this=0x7ffeefbf5b20, grid=0x7ffeefbf23e0, 
flags=128, mode=TEXT_MODE, numbered=false) at MathParser.cpp:2080:20
  * frame #2: 0x000100790987 LyX`lyx::(anonymous 
namespace)::Parser::parse(this=0x7ffeefbf5b20, array=0x000113353690, 
flags=64, mode=TEXT_MODE) at MathParser.cpp:782:2
frame #3: 0x00010079f18c LyX`lyx::(anonymous 
namespace)::Parser::parse1(this=0x7ffeefbf5b20, grid=0x7ffeefbf5a30, 
flags=0, mode=MATH_MODE, numbered=false) at MathParser.cpp:2013:6
frame #4: 0x000100790987 LyX`lyx::(anonymous 
namespace)::Parser::parse(this=0x7ffeefbf5b20, array=0x7ffeefbf6530, 
flags=0, mode=MATH_MODE) at MathParser.cpp:782:2
frame #5: 0x000100790874 
LyX`lyx::mathed_parse_cell(ar=0x7ffeefbf6530, str=L"\\textrm \\AA", 
f=NORMAL) at MathParser.cpp:2156:37
frame #6: 0x0001007c28d2 LyX`lyx::asArray(str=L"\\textrm \\AA", 
ar=0x7ffeefbf6530, pf=NORMAL) at MathSupport.cpp:990:38
frame #7: 0x0001006deba4 
LyX`lyx::InsetMathNest::doDispatch(this=0x0001112cde10, 
cur=0x000106149098, cmd=0x7ffeefbf9068) at InsetMathNest.cpp:1237:4
frame #8: 0x00010065baa2 
LyX`lyx::InsetMathGrid::doDispatch(this=0x0001112cde10, 
cur=0x000106149098, cmd=0x7ffeefbf9068) at InsetMathGrid.cpp:1733:18
frame #9: 0x00010067e615 
LyX`lyx::InsetMathHull::doDispatch(this=0x0001112cde10, 
cur=0x000106149098, cmd=0x7ffeefbf9068) at InsetMathHull.cpp:2024:18
frame #10: 0x000100811520 
LyX`lyx::Inset::dispatch(this=0x0001112cde10, cur=0x000106149098, 
cmd=0x7ffeefbf9068) at Inset.cpp:325:2
frame #11: 0x0001001e018b 
LyX`lyx::Cursor::dispatch(this=0x000106149098, cmd0=0x00011123dd68) at 
Cursor.cpp:337:11
frame #12: 0x000100d876b4 
LyX`lyx::frontend::GuiView::dispatchToBufferView(this=0x00011159b6f0, 
cmd=0x00011123dd68, dr=0x7ffeefbfc7a0) at GuiView.cpp:3687:15
frame #13: 0x000100d80df6 
LyX`lyx::frontend::GuiView::dispatch(this=0x00011159b6f0, 
cmd=0x00011123dd68, dr=0x7ffeefbfc7a0) at GuiView.cpp:4343:4
frame #14: 0x000100a96008 
LyX`lyx::frontend::GuiApplication::dispatch(this=0x000105d0a1d0, 
cmd=0x00011123dd68, dr=0x7ffeefbfc7a0) at GuiApplication.cpp:2076:19
frame #15: 0x000100a8ff88 
LyX`lyx::frontend::GuiApplication::dispatch(this=0x000105d0a1d0, 
cmd=0x00011123dd68) at GuiApplication.cpp:1405:3
frame #16: 0x00010037a4ea LyX`lyx::dispatch(action=0x00011123dd68) 
at LyX.cpp:1462:19
frame #17: 0x000100a41c4b 
LyX`lyx::frontend::Action::action(this=0x00011334a560) at Action.cpp:87:2
frame #18: 0x000100a41d51 
LyX`lyx::frontend::Action::qt_static_metacall(_o=0x00011334a560, 
_c=InvokeMetaMethod, _id=1, _a=0x7ffeefbfc970) at moc_Action.cpp:81:21
frame #19: 0x00010554d63a QtCore`QMetaObject::activate(QObject*, int, 
int, void**) + 2298
frame #20: 0x00010474e185 
QtWidgets`QAction::activate(QAction::ActionEvent) + 309
frame #21: 0x000104841be3 QtWidgets`QAbstractButtonPrivate::click() + 
147
frame #22: 0x000104842d6c 
QtWidgets`QAbstractButton::mouseReleaseEvent(QMouseEvent*) + 268
frame #23: 0x000104939bbf 
QtWidgets`QToolButton::mouseReleaseEvent(QMouseEvent*) + 15
frame #24: 0x0001047931d2 QtWidgets`QWidget::event(QEvent*) + 450
frame #25: 0x00010493a14f QtWidgets`QToolButton::event(QEvent*) + 319
frame #26: 0x0001047576ff 
QtWidgets`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 271
frame #27: 0x00010475a59d QtWidgets`QApplication::notify(QObject*, 
QEvent*) + 7373
frame #28: 0x000100a9d033 
LyX`lyx::frontend::GuiApplication::notify(this=0x000105d0a1d0, 
receiver=0x0001114debf0, event=0x7ffeefbfd060) at 
GuiApplication.cpp:2712:24
frame #29: 0x00010551c684 
QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 

Re: Bug in Lyx 1.3.4 ?

[emile lunardon]

I have installed LyX 2.3.4 on Windows10 and the same crash already seen on
LyX for Linux occurs when trying to enter the two Math Symbols :
$\textrm{Ø}\textrm{Å}$

Le mer. 5 févr. 2020 à 08:32, emile lunardon  a
écrit :

> When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols
> shown in the attached file (written with LyX 1.3.3), there is a crash of
> LyX 1.3.4 with the attached messages.
>
> Can someone confirm this strange phenomena ?
>
> --
>
> (  1) ./lyx: ./lyx() [0x906d2a]
> (  2) ./lyx: ./lyx() [0x9062e6]
> (  3) ./lyx: ./lyx() [0x63e005]
> (  4) /lib/x86_64-linux-gnu/libc.so.6:
> /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbd1b80ef20]
> (  5) ./lyx: ./lyx() [0x5553f0]
> (  6) ./lyx: ./lyx() [0x7bcbcd]
> (  7) ./lyx: ./lyx() [0x7b6231]
> (  8) ./lyx: ./lyx() [0x7bcf6a]
> (  9) ./lyx: ./lyx() [0x7b6231]
> ( 10) ./lyx: ./lyx() [0x7b6381]
> ( 11) ./lyx: ./lyx() [0x7c4f15]
> ( 12) ./lyx: ./lyx() [0x791b67]
> ( 13) ./lyx: ./lyx() [0x7e87a8]
> ( 14) ./lyx: ./lyx() [0x77274b]
> ( 15) ./lyx: ./lyx() [0x812b46]
> ( 16) ./lyx: ./lyx() [0x5d41dd]
> ( 17) ./lyx: ./lyx() [0x9321bb]
> ( 18) ./lyx: ./lyx() [0x9429f6]
> ( 19) ./lyx: ./lyx() [0x911f0e]
> ( 20) ./lyx: ./lyx() [0x90c5e9]
> ( 21) ./lyx: ./lyx() [0x98abf1]
> ( 22) ./lyx: ./lyx() [0x98ac78]
> ( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QMetaObject::activate(QObject*, QMetaObject const*, int, void**)
> ( 24) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::triggered(bool)
> ( 25) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QAction::activate(QAction::ActionEvent)
> ( 26) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7fbd1d2cafa3]
> ( 27) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QAbstractButton::mouseReleaseEvent(QMouseEvent*)
> ( 28) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QToolButton::mouseReleaseEvent(QMouseEvent*)
> ( 29) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QWidget::event(QEvent*)
> ( 30) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplicationPrivate::notify_helper(QObject*, QEvent*)
> ( 31) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplication::notify(QObject*, QEvent*)
> ( 32) ./lyx: ./lyx() [0x916195]
> ( 33) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QCoreApplication::notifyInternal(QObject*, QEvent*)
> ( 34) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*,
> QWidget*, QWidget**, QPointer&, bool)
> ( 35) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249ddc) [0x7fbd1cf73ddc]
> ( 36) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplication::x11ProcessEvent(_XEvent*)
> ( 37) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7fbd1cf9c592]
> ( 38) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7)
> [0x7fbd1b301417]
> ( 39) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650) [0x7fbd1b301650]
> ( 40) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)
> [0x7fbd1b3016dc]
> ( 41) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QEventDispatcherGlib::processEvents(QFlags)
> ( 42) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7fbd1cf9c666]
> ( 43) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QEventLoop::processEvents(QFlags)
> ( 44) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QEventLoop::exec(QFlags)
> ( 45) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec()
> ( 46) ./lyx: ./lyx() [0x643306]
> ( 47) ./lyx: ./lyx() [0x50827d]
> ( 48) /lib/x86_64-linux-gnu/libc.so.6:
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbd1b7f1b97]
> ( 49) ./lyx: ./lyx() [0x512eba]
>
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug in Lyx 1.3.4 ?

[Pavel Sanda]

On Wed, Feb 05, 2020 at 08:32:21AM +0100, emile lunardon wrote:
> When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols
> shown in the attached file (written with LyX 1.3.3), there is a crash of
> LyX 1.3.4 with the attached messages.
> 
> Can someone confirm this strange phenomena ?

I can not (tried with Qt 4 as you do). (My entering was copy paste from your 
document.)
Your backtrace is not much useful, if you compile on your own we would need it 
with debug symbols...
Pavel
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug in Lyx 1.3.4 ?

[Paul A. Rubin]

On 2/5/20 2:32 AM, emile lunardon wrote:
When I try to enter, under LyX 1.3.4 (Linux), one of the two Math 
symbols shown in the attached file (written with LyX 1.3.3), there is 
a crash of LyX 1.3.4 with the attached messages.


Can someone confirm this strange phenomena ?

--

(  1) ./lyx: ./lyx() [0x906d2a]
(  2) ./lyx: ./lyx() [0x9062e6]
(  3) ./lyx: ./lyx() [0x63e005]
(  4) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbd1b80ef20]

(  5) ./lyx: ./lyx() [0x5553f0]
(  6) ./lyx: ./lyx() [0x7bcbcd]
(  7) ./lyx: ./lyx() [0x7b6231]
(  8) ./lyx: ./lyx() [0x7bcf6a]
(  9) ./lyx: ./lyx() [0x7b6231]
( 10) ./lyx: ./lyx() [0x7b6381]
( 11) ./lyx: ./lyx() [0x7c4f15]
( 12) ./lyx: ./lyx() [0x791b67]
( 13) ./lyx: ./lyx() [0x7e87a8]
( 14) ./lyx: ./lyx() [0x77274b]
( 15) ./lyx: ./lyx() [0x812b46]
( 16) ./lyx: ./lyx() [0x5d41dd]
( 17) ./lyx: ./lyx() [0x9321bb]
( 18) ./lyx: ./lyx() [0x9429f6]
( 19) ./lyx: ./lyx() [0x911f0e]
( 20) ./lyx: ./lyx() [0x90c5e9]
( 21) ./lyx: ./lyx() [0x98abf1]
( 22) ./lyx: ./lyx() [0x98ac78]
( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QMetaObject::activate(QObject*, QMetaObject const*, int, void**)

( 24) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::triggered(bool)
( 25) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QAction::activate(QAction::ActionEvent)
( 26) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7fbd1d2cafa3]
( 27) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QAbstractButton::mouseReleaseEvent(QMouseEvent*)
( 28) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QToolButton::mouseReleaseEvent(QMouseEvent*)

( 29) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QWidget::event(QEvent*)
( 30) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplicationPrivate::notify_helper(QObject*, QEvent*)
( 31) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplication::notify(QObject*, QEvent*)

( 32) ./lyx: ./lyx() [0x916195]
( 33) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QCoreApplication::notifyInternal(QObject*, QEvent*)
( 34) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, 
QWidget*, QWidget**, QPointer&, bool)
( 35) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249ddc) [0x7fbd1cf73ddc]
( 36) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplication::x11ProcessEvent(_XEvent*)
( 37) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7fbd1cf9c592]
( 38) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7) 
[0x7fbd1b301417]
( 39) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650) [0x7fbd1b301650]
( 40) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) 
[0x7fbd1b3016dc]
( 41) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventDispatcherGlib::processEvents(QFlags)
( 42) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7fbd1cf9c666]
( 43) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::processEvents(QFlags)
( 44) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::exec(QFlags)

( 45) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec()
( 46) ./lyx: ./lyx() [0x643306]
( 47) ./lyx: ./lyx() [0x50827d]
( 48) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbd1b7f1b97]

( 49) ./lyx: ./lyx() [0x512eba]

LyX 1.3.4 is rather old. Have you tried a more recent version? I cannot 
reproduce the crash, but I'm using LyX 2.3.3.


Paul

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

Re: Bug in Lyx 1.3.4 ?

[Daniel]

I seem to have no problem entering them on MacOS. Though if I use the 
keyboard to enter them I get


$\mathrm{\mathring{A}}$$\mathrm{\slashed{O}}$

instead of

$\textrm{Å}$$\textrm{Ø}$

However, if I copy and paste the symbols from the file, I get the latter 
and no crash either.


Daniel

On 2020-02-05 08:32, emile lunardon wrote:
When I try to enter, under LyX 1.3.4 (Linux), one of the two Math 
symbols shown in the attached file (written with LyX 1.3.3), there is a 
crash of LyX 1.3.4 with the attached messages.


Can someone confirm this strange phenomena ?

--

(  1) ./lyx: ./lyx() [0x906d2a]
(  2) ./lyx: ./lyx() [0x9062e6]
(  3) ./lyx: ./lyx() [0x63e005]
(  4) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbd1b80ef20]

(  5) ./lyx: ./lyx() [0x5553f0]
(  6) ./lyx: ./lyx() [0x7bcbcd]
(  7) ./lyx: ./lyx() [0x7b6231]
(  8) ./lyx: ./lyx() [0x7bcf6a]
(  9) ./lyx: ./lyx() [0x7b6231]
( 10) ./lyx: ./lyx() [0x7b6381]
( 11) ./lyx: ./lyx() [0x7c4f15]
( 12) ./lyx: ./lyx() [0x791b67]
( 13) ./lyx: ./lyx() [0x7e87a8]
( 14) ./lyx: ./lyx() [0x77274b]
( 15) ./lyx: ./lyx() [0x812b46]
( 16) ./lyx: ./lyx() [0x5d41dd]
( 17) ./lyx: ./lyx() [0x9321bb]
( 18) ./lyx: ./lyx() [0x9429f6]
( 19) ./lyx: ./lyx() [0x911f0e]
( 20) ./lyx: ./lyx() [0x90c5e9]
( 21) ./lyx: ./lyx() [0x98abf1]
( 22) ./lyx: ./lyx() [0x98ac78]
( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QMetaObject::activate(QObject*, QMetaObject const*, int, void**)

( 24) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::triggered(bool)
( 25) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QAction::activate(QAction::ActionEvent)
( 26) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7fbd1d2cafa3]
( 27) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QAbstractButton::mouseReleaseEvent(QMouseEvent*)
( 28) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QToolButton::mouseReleaseEvent(QMouseEvent*)

( 29) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QWidget::event(QEvent*)
( 30) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplicationPrivate::notify_helper(QObject*, QEvent*)
( 31) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplication::notify(QObject*, QEvent*)

( 32) ./lyx: ./lyx() [0x916195]
( 33) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QCoreApplication::notifyInternal(QObject*, QEvent*)
( 34) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, 
QWidget*, QWidget**, QPointer&, bool)
( 35) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249ddc) [0x7fbd1cf73ddc]
( 36) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplication::x11ProcessEvent(_XEvent*)
( 37) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7fbd1cf9c592]
( 38) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7) [0x7fbd1b301417]
( 39) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650) [0x7fbd1b301650]
( 40) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fbd1b3016dc]
( 41) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventDispatcherGlib::processEvents(QFlags)
( 42) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7fbd1cf9c666]
( 43) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::processEvents(QFlags)
( 44) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::exec(QFlags)

( 45) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec()
( 46) ./lyx: ./lyx() [0x643306]
( 47) ./lyx: ./lyx() [0x50827d]
( 48) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbd1b7f1b97]

( 49) ./lyx: ./lyx() [0x512eba]




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

Bug in Lyx 1.3.4 ?

[emile lunardon]

When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols
shown in the attached file (written with LyX 1.3.3), there is a crash of
LyX 1.3.4 with the attached messages.

Can someone confirm this strange phenomena ?

--

(  1) ./lyx: ./lyx() [0x906d2a]
(  2) ./lyx: ./lyx() [0x9062e6]
(  3) ./lyx: ./lyx() [0x63e005]
(  4) /lib/x86_64-linux-gnu/libc.so.6:
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbd1b80ef20]
(  5) ./lyx: ./lyx() [0x5553f0]
(  6) ./lyx: ./lyx() [0x7bcbcd]
(  7) ./lyx: ./lyx() [0x7b6231]
(  8) ./lyx: ./lyx() [0x7bcf6a]
(  9) ./lyx: ./lyx() [0x7b6231]
( 10) ./lyx: ./lyx() [0x7b6381]
( 11) ./lyx: ./lyx() [0x7c4f15]
( 12) ./lyx: ./lyx() [0x791b67]
( 13) ./lyx: ./lyx() [0x7e87a8]
( 14) ./lyx: ./lyx() [0x77274b]
( 15) ./lyx: ./lyx() [0x812b46]
( 16) ./lyx: ./lyx() [0x5d41dd]
( 17) ./lyx: ./lyx() [0x9321bb]
( 18) ./lyx: ./lyx() [0x9429f6]
( 19) ./lyx: ./lyx() [0x911f0e]
( 20) ./lyx: ./lyx() [0x90c5e9]
( 21) ./lyx: ./lyx() [0x98abf1]
( 22) ./lyx: ./lyx() [0x98ac78]
( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
QMetaObject::activate(QObject*, QMetaObject const*, int, void**)
( 24) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::triggered(bool)
( 25) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QAction::activate(QAction::ActionEvent)
( 26) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7fbd1d2cafa3]
( 27) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QAbstractButton::mouseReleaseEvent(QMouseEvent*)
( 28) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QToolButton::mouseReleaseEvent(QMouseEvent*)
( 29) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QWidget::event(QEvent*)
( 30) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QApplicationPrivate::notify_helper(QObject*, QEvent*)
( 31) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QApplication::notify(QObject*, QEvent*)
( 32) ./lyx: ./lyx() [0x916195]
( 33) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
QCoreApplication::notifyInternal(QObject*, QEvent*)
( 34) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*,
QWidget*, QWidget**, QPointer&, bool)
( 35) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249ddc) [0x7fbd1cf73ddc]
( 36) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QApplication::x11ProcessEvent(_XEvent*)
( 37) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7fbd1cf9c592]
( 38) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7)
[0x7fbd1b301417]
( 39) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650) [0x7fbd1b301650]
( 40) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)
[0x7fbd1b3016dc]
( 41) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
QEventDispatcherGlib::processEvents(QFlags)
( 42) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7fbd1cf9c666]
( 43) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
QEventLoop::processEvents(QFlags)
( 44) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
QEventLoop::exec(QFlags)
( 45) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec()
( 46) ./lyx: ./lyx() [0x643306]
( 47) ./lyx: ./lyx() [0x50827d]
( 48) /lib/x86_64-linux-gnu/libc.so.6:
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbd1b7f1b97]
( 49) ./lyx: ./lyx() [0x512eba]


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

Re: Bug in LyX regarding page format and hyperref

[Jürgen Spitzmüller]

Am Montag, den 05.08.2019, 16:19 +0200 schrieb Jürgen Spitzmüller:
> But still, if A4 is selected in LyX and memoir outputs US
> letter, that's simply plain wrong. We can do better.

This will be fixed in LyX 2.3.4.

Jürgen


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

Re: Bug in LyX regarding page format and hyperref

[Jürgen Spitzmüller]

Am Montag, den 05.08.2019, 08:22 -0500 schrieb Les:
> I doubt if accounting for Memoir's idiosyncracies is practical. The
> Memoir class allows fine tuning of numerous parameters that LyX
> doesn't
> even know about.

I know. But still, if A4 is selected in LyX and memoir outputs US
letter, that's simply plain wrong. We can do better.

Jürgen


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

Re: Bug in LyX regarding page format and hyperref

[Les]

On Mon, 05 Aug 2019 10:40:53 +0200
Jürgen Spitzmüller  wrote:

> Yes, memoir overrides geometry (which is used for the custom margins).
> However, we could account for that in LyX. See
> https://www.lyx.org/trac/ticket/10970

I doubt if accounting for Memoir's idiosyncracies is practical. The
Memoir class allows fine tuning of numerous parameters that LyX doesn't
even know about. It's not just page format, its:
\setstocksize
\settrimmedsize
\settrims
\settypeblocksize
\setlrmargins
\setlength{\marginparwidth}
\pagestyle
\chapterstyle
and many other parameters I've never used.

If you're not prepared to read the 609 page Memoir manual (memman.pdf)
you really shouldn't try to use Memoir.

If you do read it, and understand it, you will view page layout in a
completely new way.

I have used memoir extensively for years, and I'm still learning how to
improve page layout. If you want good page layout that is nearly what
you need, use KOMA-script Book. If you want an exact page layout, use
Memoir, but be prepared to learn how to do it.

Les
-- 
Les Denham

Re: Bug in LyX regarding page format and hyperref

[Jürgen Spitzmüller]

Am Samstag, den 27.07.2019, 11:06 -0400 schrieb Paul A. Rubin:
> I don't have any experience with book classes, so I do not know the 
> peculiarities of the Memoir class. I suspect this is problem with
> how 
> Memoir reacts to certain combinations of things, rather than a LyX
> bug. 

Yes, memoir overrides geometry (which is used for the custom margins).
However, we could account for that in LyX. See
https://www.lyx.org/trac/ticket/10970

Jürgen


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

Re: Bug in LyX regarding page format and hyperref

[Baris Erkus]

On 27-Jul-19 9:32 AM, Marius Shekow wrote:
> Hi again,
>
> I forgot to mention that you also need to set custom page margins. An
> example file is attached.
>
> Best regards!
>
> Am 26.07.2019 um 20:14 schrieb Marius Shekow:
>> Hi,
>>
>> I've noticed that the recent Lyx versions (2.3.x) generate a PDF that
>> is of "US Letter" size, even though I've explicitly set up A4 in the
>> document settings (Page Layout -> Format). This happens once I enable
>> Hyperref support in the document settings.
>>
>> As suggested in
>> https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size
>>  
>>
>> it seems that adding "a4paper" as custom option to the documentclass
>> seems to work. This is extreme expert knowledge that you should not
>> expect your users to have. When a normal/novice user sets up A4, then
>> the generated PDF should be A4 (and the same goes for any other page
>> format).
>>
>> Is this something that you could fix?
>>
>> Best regards!
>> Marius
>>
Hello Marius,

As you may be aware of that LyX serves as a front-end for the LaTeX 
system. When you select a paper size in LyX, LyX -probably- simply adds 
that paper size as an option to the document class in the generated tex 
file.

On the other hand, LaTeX is a sophisticated typesetting system, where 
many packages and classes are used. Sometimes, some of these packages 
and classes have conflicts and associated rules. When you try to use 
some specific packages for a given class, you may not be allowed to 
change some settings.

As far as I observe, LyX developers are trying to identify these 
conflicts and implement LyX-based solutions for some of them. However, 
it is not always possible to follow every single one of these 
conflicts/rules since there are so many of these packages and classes. 
Further, LaTeX packages are being updated constantly and may result a 
conflict after an update, which makes it very difficult to track them.

To put this in another way, if you are not using LyX, but using 
conventional text-based LaTeX typesetting, you will probably encounter 
these issues as well. If this issue is a well-known issue, LyX 
developers might have provided a solution in LyX. However, it is not 
always possible for LyX to have a solution. In this case, you are 
supposed to identify the issue and provide a solution by yourself, which 
we LyX-used do all the time.

Best Regards,

Baris

-- 
↓↓
Please bottom-post. Start your reply here:

Re: Bug in LyX regarding page format and hyperref

[Marius Shekow]

Hi,

I was aware of https://wiki.lyx.org/LyX/UsingMemoirInLyX but at the same
time that page seems outdated, as it explicitly mentions Lyx 1.5, which
is dated. I saw that it also mentions section 6.3 of the "Additional
Features" LyX help document (valid for LyX 2.x), but did not see this
caveat (US Letter) being listed. It may still make sense for LyX to
handle this specific case, but that's up to you. I'm content with the
fix I found (which I mentioned in the original post).

I've been using memoir simply out of habit. I don't think I'm using
specific features that other book classes wouldn't offer. I'd say that I
just liked the look of the generated PDF that came out of the box, in
comparison to other book classes. I may look into scrbook for the next
project, though.

Best!
Marius

Am 27.07.2019 um 17:27 schrieb Axel Dessecker:

Am Samstag, 27. Juli 2019, 08:32:33 CEST schrieb Marius Shekow:

Hi again,

I forgot to mention that you also need to set custom page margins. An
example file is attached.

Best regards!

Am 26.07.2019 um 20:14 schrieb Marius Shekow:

Hi,

I've noticed that the recent Lyx versions (2.3.x) generate a PDF that
is of "US Letter" size, even though I've explicitly set up A4 in the
document settings (Page Layout -> Format). This happens once I enable
Hyperref support in the document settings.

As suggested in
https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-packa
ge-change-the-paper-size it seems that adding "a4paper" as custom option
to the documentclass seems to work. This is extreme expert knowledge that
you should not expect your users to have. When a normal/novice user sets
up A4, then the generated PDF should be A4 (and the same goes for any
other page format).

Is this something that you could fix?

Best regards!
Marius

Marius,

I can reproduce this behaviour, which seems to be associated with the memoir
class. Very configurable but tricky, as announced at
https://wiki.lyx.org/LyX/UsingMemoirInLyX .

Is there a specific reason why you are not using scrbook?

Axel

Re: Bug in LyX regarding page format and hyperref

[Axel Dessecker]

Am Samstag, 27. Juli 2019, 08:32:33 CEST schrieb Marius Shekow:
> Hi again,
> 
> I forgot to mention that you also need to set custom page margins. An
> example file is attached.
> 
> Best regards!
> 
> Am 26.07.2019 um 20:14 schrieb Marius Shekow:
> > Hi,
> > 
> > I've noticed that the recent Lyx versions (2.3.x) generate a PDF that
> > is of "US Letter" size, even though I've explicitly set up A4 in the
> > document settings (Page Layout -> Format). This happens once I enable
> > Hyperref support in the document settings.
> > 
> > As suggested in
> > https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-packa
> > ge-change-the-paper-size it seems that adding "a4paper" as custom option
> > to the documentclass seems to work. This is extreme expert knowledge that
> > you should not expect your users to have. When a normal/novice user sets
> > up A4, then the generated PDF should be A4 (and the same goes for any
> > other page format).
> > 
> > Is this something that you could fix?
> > 
> > Best regards!
> > Marius

Marius,

I can reproduce this behaviour, which seems to be associated with the memoir 
class. Very configurable but tricky, as announced at 
https://wiki.lyx.org/LyX/UsingMemoirInLyX .

Is there a specific reason why you are not using scrbook?

Axel

Re: Bug in LyX regarding page format and hyperref

[Paul A. Rubin]

On 7/27/19 2:32 AM, Marius Shekow wrote:

Hi again,

I forgot to mention that you also need to set custom page margins. An
example file is attached.

Best regards!

Am 26.07.2019 um 20:14 schrieb Marius Shekow:

Hi,

I've noticed that the recent Lyx versions (2.3.x) generate a PDF that
is of "US Letter" size, even though I've explicitly set up A4 in the
document settings (Page Layout -> Format). This happens once I enable
Hyperref support in the document settings.

As suggested in
https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size 


it seems that adding "a4paper" as custom option to the documentclass
seems to work. This is extreme expert knowledge that you should not
expect your users to have. When a normal/novice user sets up A4, then
the generated PDF should be A4 (and the same goes for any other page
format).

Is this something that you could fix?

Best regards!
Marius


Please bottom post in messages to the forum.

I can confirm your example compiles to US letter when it should compile 
to A4, but the trigger mechanism is more complex than hyperref + custom 
margins + A4 paper size. It only seems to happen with the Memoir class. 
I tried the basic book class, the AMS book class and also the basic 
article class, and they all compiled to A4.


I don't have any experience with book classes, so I do not know the 
peculiarities of the Memoir class. I suspect this is problem with how 
Memoir reacts to certain combinations of things, rather than a LyX bug. 
Perhaps an experience Memoir user can weigh in.


Paul

Re: Bug in LyX regarding page format and hyperref

[Marius Shekow]

Hi again,

I forgot to mention that you also need to set custom page margins. An
example file is attached.

Best regards!

Am 26.07.2019 um 20:14 schrieb Marius Shekow:

Hi,

I've noticed that the recent Lyx versions (2.3.x) generate a PDF that
is of "US Letter" size, even though I've explicitly set up A4 in the
document settings (Page Layout -> Format). This happens once I enable
Hyperref support in the document settings.

As suggested in
https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size
it seems that adding "a4paper" as custom option to the documentclass
seems to work. This is extreme expert knowledge that you should not
expect your users to have. When a normal/novice user sets up A4, then
the generated PDF should be A4 (and the same goes for any other page
format).

Is this something that you could fix?

Best regards!
Marius



newfile2.lyx
Description: application/lyx

Re: Bug in LyX regarding page format and hyperref

[Paul A. Rubin]

On 7/26/19 2:14 PM, Marius Shekow wrote:

Hi,

I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is
of "US Letter" size, even though I've explicitly set up A4 in the
document settings (Page Layout -> Format). This happens once I enable
Hyperref support in the document settings.

As suggested in
https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size 


it seems that adding "a4paper" as custom option to the documentclass
seems to work. This is extreme expert knowledge that you should not
expect your users to have. When a normal/novice user sets up A4, then
the generated PDF should be A4 (and the same goes for any other page
format).

Is this something that you could fix?

Best regards!
Marius

I'm unable to reproduce that here. I switched a document from US Letter 
to A4 in the page layout settings, turned on hyperref in the PDF 
settings, viewed the document (using pdflatex), and the resulting file 
was A4 (confirmed by checking File > Properties in the PDF viewer). I 
also tried A2, which produces a visibly different result (many fewer pages).


If you can reproduce the bug, please reply with a minimal working 
example of it.


Paul

Bug in LyX regarding page format and hyperref

[Marius Shekow]

Hi,

I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is
of "US Letter" size, even though I've explicitly set up A4 in the
document settings (Page Layout -> Format). This happens once I enable
Hyperref support in the document settings.

As suggested in
https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size
it seems that adding "a4paper" as custom option to the documentclass
seems to work. This is extreme expert knowledge that you should not
expect your users to have. When a normal/novice user sets up A4, then
the generated PDF should be A4 (and the same goes for any other page
format).

Is this something that you could fix?

Best regards!
Marius

Re: Bug in LyX 2.2.0?

[Uwe Stöhr]

Am 14.07.2016 um 09:52 schrieb Bernt Lie:


On my *job laptop*, I get the following error message when I try to preview the 
document I work on: [cid:image002.jpg@01D1DDB5.6D9DC410]


So on this PC the LaTeX package "units" is not installed. LaTeX packages 
are handled by the program MiKTeX. MiKTeX is by default configured to 
install missing packages automatically. It seems that this failed. I 
suggest to

- open an Internet connection
- log in to Windows as Admin
- check in the MiKTeX settings (available via Windows' start menu) that 
the option "Install missing packages on the fly" is set to "Yes".

- reconfigure LyX using the menu Tools -> Reconfigure

Does it now work?

regards Uwe

Weird KDE Bug in LyX

[Richard Heck]

For anyone running LyX 2.2.0 under KDE (or using a KDE-based window 
manager, or anything of that sort):


There is an annoying new feature, KDE's "accelerator manager", that 
automatically adds shortcuts. This causes conflicts and so forth in many 
Qt-based programs, when those programs are run with Qt5. If you are 
experiencing this issue, please see

http://www.lyx.org/trac/ticket/10261#comment:16
for a workaround.

Richard Heck

Re: Math preview bug (?) in LyX 2.1.4

[Scott Kostyshak]

On Fri, Apr 01, 2016 at 06:05:46AM -0700, Hal Kierstead wrote:
> I have very occasionally had this problem even while editing several short 
> formulas, and have fixed it in the same way.

OK good to know. Let us know if you see this problem with 2.2.0. It
would be nice to figure out what's going on. Perhaps it is a threading
or caching issue.

You and Paola are both on Mac, I believe, but Alexander is on Fedora so
it seems not limited to one platform. I don't think I have ever seen
this issue though on Ubuntu.

Scott

> Hal Kierstead
> 
> > On Mar 31, 2016, at 11:27 PM, Scott Kostyshak  wrote:
> > 
> > On Tue, Mar 01, 2016 at 06:31:56PM +, Paola Manzini wrote:
> >> I can confirm I have the same problem in  2.2.0alpha2 on Mac OS El 
> >> Capitan, though I haven’t tried the latest beta. I have the feeling it 
> >> happens much less often that with 2.1.4 (it happened to me just today for 
> >> the first time since installing the alpha2 version, and I use LyX for many 
> >> hours every day). One good reason to try the new beta!
> > 
> > Paola is there any way to reliably reproduce the problem? In any case,
> > it's good news that it happens less often on 2.2.0alpha2 than 2.1.4.
> > 
> > Scott
> > 
> >>> On 1 Mar 2016, at 17:32, PhilipPirrip  wrote:
> >>> 
> >>> In addition to what Scott said: can you share the document that's causing 
> >>> you problems, I can test it on Fedora 23 in both LyX 2.1.4 and LyX 
> >>> 2.2.0dev for you.
> >>> 
> >>> 
> >>> 
> >>> 
> >>> On 03/01/2016 04:18 AM, Alexander Stasinski wrote:
>  (Apologies if this has already been discussed. I searched the archive
>  and bug reports and did not find anything related. Perhaps I didn't
>  search well enough.)
>  
>  I'm using LyX 2.1.4 on Fedora 22 (4.3.4-200.fc22.x86_64) with instant
>  math preview on. After editing about a page of maths formulae, the
>  instant preview will start displaying "random" previous formulae
>  instead of the correct ones. When I go inside the formula, I can edit
>  the correct one, so LyX has the correct one internally.
>  The problem goes away if I close the document and reopen it, but after
>  about another page or so of editing, the problem reoccurs.
>  
>  I'd be grateful for any advice on how to solve this.
>  
>  Best wishes,
>  Alexander
>  
> >>> 
> >>> 
> >> 
> >> 
> >> 
> >> 
> 


signature.asc
Description: PGP signature

Re: Math preview bug (?) in LyX 2.1.4

[Scott Kostyshak]

On Fri, Apr 01, 2016 at 08:44:27AM +, Paola Manzini wrote:
> sorry Scott, I moved to the beta version and uninstalled alpha2 - but I 
> cannot remember if there was a particular pattern that caused the problem.

No problem, Paula. But if you see the issue on alpha2 I would be
surprised if you don't run into it on beta2. Keep an eye out for it and
let us know if you think of anything that you think might trigger the
bug.

Scott

> > On 1 Apr 2016, at 07:27, Scott Kostyshak  wrote:
> > 
> > On Tue, Mar 01, 2016 at 06:31:56PM +, Paola Manzini wrote:
> >> I can confirm I have the same problem in  2.2.0alpha2 on Mac OS El 
> >> Capitan, though I haven’t tried the latest beta. I have the feeling it 
> >> happens much less often that with 2.1.4 (it happened to me just today for 
> >> the first time since installing the alpha2 version, and I use LyX for many 
> >> hours every day). One good reason to try the new beta!
> > 
> > Paola is there any way to reliably reproduce the problem? In any case,
> > it's good news that it happens less often on 2.2.0alpha2 than 2.1.4.
> > 
> > Scott
> > 
> >>> On 1 Mar 2016, at 17:32, PhilipPirrip  wrote:
> >>> 
> >>> In addition to what Scott said: can you share the document that's causing 
> >>> you problems, I can test it on Fedora 23 in both LyX 2.1.4 and LyX 
> >>> 2.2.0dev for you.
> >>> 
> >>> 
> >>> 
> >>> 
> >>> On 03/01/2016 04:18 AM, Alexander Stasinski wrote:
>  (Apologies if this has already been discussed. I searched the archive
>  and bug reports and did not find anything related. Perhaps I didn't
>  search well enough.)
>  
>  I'm using LyX 2.1.4 on Fedora 22 (4.3.4-200.fc22.x86_64) with instant
>  math preview on. After editing about a page of maths formulae, the
>  instant preview will start displaying "random" previous formulae
>  instead of the correct ones. When I go inside the formula, I can edit
>  the correct one, so LyX has the correct one internally.
>  The problem goes away if I close the document and reopen it, but after
>  about another page or so of editing, the problem reoccurs.
>  
>  I'd be grateful for any advice on how to solve this.
>  
>  Best wishes,
>  Alexander
>  
> >>> 
> >>> 
> >> 
> >> 
> >> 
> >> 
> 
> -- 
> Prof. Paola Manzini
> School of Economics and Finance
> University of St. Andrews
> Castlecliffe, The Scores
> St. Andrews KY16 9AL
> Scotland, U.K.
> 
> tel: +44 (0)1334 462436
> fax: +44 (0)1334 462444
> http://www.st-andrews.ac.uk/~pm210/
> Skype: paolamanzini
> 
> The University of St Andrews is a charity registered in Scotland : No 
> SC013532 
> 
> 
> 


signature.asc
Description: PGP signature

Re: Math preview bug (?) in LyX 2.1.4

[Hal Kierstead]

I have very occasionally had this problem even while editing several short 
formulas, and have fixed it in the same way.

Hal Kierstead

> On Mar 31, 2016, at 11:27 PM, Scott Kostyshak  wrote:
> 
> On Tue, Mar 01, 2016 at 06:31:56PM +, Paola Manzini wrote:
>> I can confirm I have the same problem in  2.2.0alpha2 on Mac OS El Capitan, 
>> though I haven’t tried the latest beta. I have the feeling it happens much 
>> less often that with 2.1.4 (it happened to me just today for the first time 
>> since installing the alpha2 version, and I use LyX for many hours every 
>> day). One good reason to try the new beta!
> 
> Paola is there any way to reliably reproduce the problem? In any case,
> it's good news that it happens less often on 2.2.0alpha2 than 2.1.4.
> 
> Scott
> 
>>> On 1 Mar 2016, at 17:32, PhilipPirrip  wrote:
>>> 
>>> In addition to what Scott said: can you share the document that's causing 
>>> you problems, I can test it on Fedora 23 in both LyX 2.1.4 and LyX 2.2.0dev 
>>> for you.
>>> 
>>> 
>>> 
>>> 
>>> On 03/01/2016 04:18 AM, Alexander Stasinski wrote:
 (Apologies if this has already been discussed. I searched the archive
 and bug reports and did not find anything related. Perhaps I didn't
 search well enough.)
 
 I'm using LyX 2.1.4 on Fedora 22 (4.3.4-200.fc22.x86_64) with instant
 math preview on. After editing about a page of maths formulae, the
 instant preview will start displaying "random" previous formulae
 instead of the correct ones. When I go inside the formula, I can edit
 the correct one, so LyX has the correct one internally.
 The problem goes away if I close the document and reopen it, but after
 about another page or so of editing, the problem reoccurs.
 
 I'd be grateful for any advice on how to solve this.
 
 Best wishes,
 Alexander
 
>>> 
>>> 
>> 
>> 
>> 
>> 

Re: Math preview bug (?) in LyX 2.1.4

[Paola Manzini]

sorry Scott, I moved to the beta version and uninstalled alpha2 - but I cannot 
remember if there was a particular pattern that caused the problem.
> On 1 Apr 2016, at 07:27, Scott Kostyshak  wrote:
> 
> On Tue, Mar 01, 2016 at 06:31:56PM +, Paola Manzini wrote:
>> I can confirm I have the same problem in  2.2.0alpha2 on Mac OS El Capitan, 
>> though I haven’t tried the latest beta. I have the feeling it happens much 
>> less often that with 2.1.4 (it happened to me just today for the first time 
>> since installing the alpha2 version, and I use LyX for many hours every 
>> day). One good reason to try the new beta!
> 
> Paola is there any way to reliably reproduce the problem? In any case,
> it's good news that it happens less often on 2.2.0alpha2 than 2.1.4.
> 
> Scott
> 
>>> On 1 Mar 2016, at 17:32, PhilipPirrip  wrote:
>>> 
>>> In addition to what Scott said: can you share the document that's causing 
>>> you problems, I can test it on Fedora 23 in both LyX 2.1.4 and LyX 2.2.0dev 
>>> for you.
>>> 
>>> 
>>> 
>>> 
>>> On 03/01/2016 04:18 AM, Alexander Stasinski wrote:
 (Apologies if this has already been discussed. I searched the archive
 and bug reports and did not find anything related. Perhaps I didn't
 search well enough.)
 
 I'm using LyX 2.1.4 on Fedora 22 (4.3.4-200.fc22.x86_64) with instant
 math preview on. After editing about a page of maths formulae, the
 instant preview will start displaying "random" previous formulae
 instead of the correct ones. When I go inside the formula, I can edit
 the correct one, so LyX has the correct one internally.
 The problem goes away if I close the document and reopen it, but after
 about another page or so of editing, the problem reoccurs.
 
 I'd be grateful for any advice on how to solve this.
 
 Best wishes,
 Alexander
 
>>> 
>>> 
>> 
>> 
>> 
>> 

-- 
Prof. Paola Manzini
School of Economics and Finance
University of St. Andrews
Castlecliffe, The Scores
St. Andrews KY16 9AL
Scotland, U.K.

tel: +44 (0)1334 462436
fax: +44 (0)1334 462444
http://www.st-andrews.ac.uk/~pm210/
Skype: paolamanzini

The University of St Andrews is a charity registered in Scotland : No SC013532 

Re: Math preview bug (?) in LyX 2.1.4

[Scott Kostyshak]

On Tue, Mar 01, 2016 at 06:31:56PM +, Paola Manzini wrote:
> I can confirm I have the same problem in  2.2.0alpha2 on Mac OS El Capitan, 
> though I haven’t tried the latest beta. I have the feeling it happens much 
> less often that with 2.1.4 (it happened to me just today for the first time 
> since installing the alpha2 version, and I use LyX for many hours every day). 
> One good reason to try the new beta!

Paola is there any way to reliably reproduce the problem? In any case,
it's good news that it happens less often on 2.2.0alpha2 than 2.1.4.

Scott

> > On 1 Mar 2016, at 17:32, PhilipPirrip  wrote:
> > 
> > In addition to what Scott said: can you share the document that's causing 
> > you problems, I can test it on Fedora 23 in both LyX 2.1.4 and LyX 2.2.0dev 
> > for you.
> > 
> > 
> > 
> > 
> > On 03/01/2016 04:18 AM, Alexander Stasinski wrote:
> >> (Apologies if this has already been discussed. I searched the archive
> >> and bug reports and did not find anything related. Perhaps I didn't
> >> search well enough.)
> >> 
> >> I'm using LyX 2.1.4 on Fedora 22 (4.3.4-200.fc22.x86_64) with instant
> >> math preview on. After editing about a page of maths formulae, the
> >> instant preview will start displaying "random" previous formulae
> >> instead of the correct ones. When I go inside the formula, I can edit
> >> the correct one, so LyX has the correct one internally.
> >> The problem goes away if I close the document and reopen it, but after
> >> about another page or so of editing, the problem reoccurs.
> >> 
> >> I'd be grateful for any advice on how to solve this.
> >> 
> >> Best wishes,
> >> Alexander
> >> 
> > 
> > 
> 
> 
> 
> 


signature.asc
Description: PGP signature

Re: Math preview bug (?) in LyX 2.1.4

[Paola Manzini]

I can confirm I have the same problem in  2.2.0alpha2 on Mac OS El Capitan, 
though I haven’t tried the latest beta. I have the feeling it happens much less 
often that with 2.1.4 (it happened to me just today for the first time since 
installing the alpha2 version, and I use LyX for many hours every day). One 
good reason to try the new beta!

> On 1 Mar 2016, at 17:32, PhilipPirrip  wrote:
> 
> In addition to what Scott said: can you share the document that's causing you 
> problems, I can test it on Fedora 23 in both LyX 2.1.4 and LyX 2.2.0dev for 
> you.
> 
> 
> 
> 
> On 03/01/2016 04:18 AM, Alexander Stasinski wrote:
>> (Apologies if this has already been discussed. I searched the archive
>> and bug reports and did not find anything related. Perhaps I didn't
>> search well enough.)
>> 
>> I'm using LyX 2.1.4 on Fedora 22 (4.3.4-200.fc22.x86_64) with instant
>> math preview on. After editing about a page of maths formulae, the
>> instant preview will start displaying "random" previous formulae
>> instead of the correct ones. When I go inside the formula, I can edit
>> the correct one, so LyX has the correct one internally.
>> The problem goes away if I close the document and reopen it, but after
>> about another page or so of editing, the problem reoccurs.
>> 
>> I'd be grateful for any advice on how to solve this.
>> 
>> Best wishes,
>> Alexander
>> 
> 
> 

Re: Math preview bug (?) in LyX 2.1.4

[PhilipPirrip]

In addition to what Scott said: can you share the document that's 
causing you problems, I can test it on Fedora 23 in both LyX 2.1.4 and 
LyX 2.2.0dev for you.





On 03/01/2016 04:18 AM, Alexander Stasinski wrote:

(Apologies if this has already been discussed. I searched the archive
and bug reports and did not find anything related. Perhaps I didn't
search well enough.)

I'm using LyX 2.1.4 on Fedora 22 (4.3.4-200.fc22.x86_64) with instant
math preview on. After editing about a page of maths formulae, the
instant preview will start displaying "random" previous formulae
instead of the correct ones. When I go inside the formula, I can edit
the correct one, so LyX has the correct one internally.
The problem goes away if I close the document and reopen it, but after
about another page or so of editing, the problem reoccurs.

I'd be grateful for any advice on how to solve this.

Best wishes,
Alexander

Re: Math preview bug (?) in LyX 2.1.4

[Scott Kostyshak]

On Tue, Mar 01, 2016 at 09:18:48AM +, Alexander Stasinski wrote:
> (Apologies if this has already been discussed. I searched the archive
> and bug reports and did not find anything related. Perhaps I didn't
> search well enough.)
> 
> I'm using LyX 2.1.4 on Fedora 22 (4.3.4-200.fc22.x86_64) with instant
> math preview on. After editing about a page of maths formulae, the
> instant preview will start displaying "random" previous formulae
> instead of the correct ones. When I go inside the formula, I can edit
> the correct one, so LyX has the correct one internally.
> The problem goes away if I close the document and reopen it, but after
> about another page or so of editing, the problem reoccurs.
> 
> I'd be grateful for any advice on how to solve this.
> 
> Best wishes,
> Alexander

Hi Alexander,

Thanks for the feedback. There have been numerous improvements to our
preview machinery. The first thing to do would be to test 2.2.0beta2 to
see if you still see a problem with that. If it is the case, then we
would investigate further. Are you able to test 2.2.0beta2? I'm not sure
if there are Fedora binaries available. I don't know Fedora's
updates-testing works. If it's not available through that, would you be
interested in compiling LyX? I know we have at least two Fedora users
that compile LyX around here so I'm sure we would be able to help with
any problem you come across. Note that the latest pre-release sources
are here:

ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.0-latest

Best,

Scott


signature.asc
Description: PGP signature

Math preview bug (?) in LyX 2.1.4

[Alexander Stasinski]

(Apologies if this has already been discussed. I searched the archive
and bug reports and did not find anything related. Perhaps I didn't
search well enough.)

I'm using LyX 2.1.4 on Fedora 22 (4.3.4-200.fc22.x86_64) with instant
math preview on. After editing about a page of maths formulae, the
instant preview will start displaying "random" previous formulae
instead of the correct ones. When I go inside the formula, I can edit
the correct one, so LyX has the correct one internally.
The problem goes away if I close the document and reopen it, but after
about another page or so of editing, the problem reoccurs.

I'd be grateful for any advice on how to solve this.

Best wishes,
Alexander

WORKAROUND and BUG: Yosemite + LyX

[Rainer M Krug]

THis seems to be a problem with paths and environmental variables passed
to sub-processes (also mentiond on the R sig mac list): Yosemite seems
to have implemented security mechanisms which do (to me) unknown things
to paths and environmental variables.

So, in a nutshell:

1) If you do a reconfigure in LyX started from the icon / finder /
spotlight, the reconfigure seems not to find the files needed, and does
finish nearly immediately and does not creates an (empty?) configuration
file

2) If you start lyx from the terminal

--8---cut here---start-8---
/PATH/TO/LyX.app/Contents/MacOS/lyx
--8---cut here---end---8---

and reconfigure then, it is working.

Workaround: 
Startt from terminal and reconfigure - after this everything seems to be
working

Solution:
No idea, but I guess an update in LyX

Hope this helps,

Rainer


Christopher Menzel chris.men...@gmail.com writes:

 Hal Kierstead wrote:
 I am trying to use LyX 2.1.2 with Yosemite, but review does not work
 for me.  I cannot even preview the help manuals.  I can export them
 to LaTex and then compile them with LaTex.  This must be some path
 problem, but I do not know how to deal with it.  Any help would be
 appreciated.

 Couple of very quick ideas:

 . Perhaps reconfiguring (Tools - reconfigure) might help.
 . If you aren't using the latest version of MacTeX
 http://tug.org/mactex/, consider upgrading.

 -chris


-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


pgpYK1ccEvlVl.pgp
Description: PGP signature

Re: WORKAROUND and BUG: Yosemite + LyX

[Yihui Xie]

Yes, this may solve some problems but not all. The PATH bug is still
there on Yosemite, and I see it can still bite me in LyX after I
reconfigured from the terminal. For the time being, the only reliable
solution seems to be starting LyX from the terminal. See more info at
http://stackoverflow.com/q/26491934/559676 (and the link in the
answer). Since this is a general problem on Yosemite, you might find
other apps are affected as well (as long as they launch sub processes
and call programs that are not in /bin:/usr/bin:/sbin:/usr/sbin). The
solution of starting apps from the terminal should apply to all of
them.

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Web: http://yihui.name


On Wed, Oct 22, 2014 at 4:06 AM, Rainer M Krug rai...@krugs.de wrote:
 THis seems to be a problem with paths and environmental variables passed
 to sub-processes (also mentiond on the R sig mac list): Yosemite seems
 to have implemented security mechanisms which do (to me) unknown things
 to paths and environmental variables.

 So, in a nutshell:

 1) If you do a reconfigure in LyX started from the icon / finder /
 spotlight, the reconfigure seems not to find the files needed, and does
 finish nearly immediately and does not creates an (empty?) configuration
 file

 2) If you start lyx from the terminal

 --8---cut here---start-8---
 /PATH/TO/LyX.app/Contents/MacOS/lyx
 --8---cut here---end---8---

 and reconfigure then, it is working.

 Workaround:
 Startt from terminal and reconfigure - after this everything seems to be
 working

 Solution:
 No idea, but I guess an update in LyX

 Hope this helps,

 Rainer


 Christopher Menzel chris.men...@gmail.com writes:

 Hal Kierstead wrote:
 I am trying to use LyX 2.1.2 with Yosemite, but review does not work
 for me.  I cannot even preview the help manuals.  I can export them
 to LaTex and then compile them with LaTex.  This must be some path
 problem, but I do not know how to deal with it.  Any help would be
 appreciated.

 Couple of very quick ideas:

 . Perhaps reconfiguring (Tools - reconfigure) might help.
 . If you aren't using the latest version of MacTeX
 http://tug.org/mactex/, consider upgrading.

 -chris


 --
 Rainer M. Krug
 email: Raineratkrugsdotde
 PGP: 0x0F52F982

Re: WORKAROUND and BUG: Yosemite + LyX

[Liviu Andronic]

On Wed, Oct 22, 2014 at 6:10 PM, Yihui Xie x...@yihui.name wrote:
 Yes, this may solve some problems but not all. The PATH bug is still
 there on Yosemite, and I see it can still bite me in LyX after I
 reconfigured from the terminal. For the time being, the only reliable
 solution seems to be starting LyX from the terminal.

Or ditching Apple altogether? :)

Liviu


 See more info at
 http://stackoverflow.com/q/26491934/559676 (and the link in the
 answer). Since this is a general problem on Yosemite, you might find
 other apps are affected as well (as long as they launch sub processes
 and call programs that are not in /bin:/usr/bin:/sbin:/usr/sbin). The
 solution of starting apps from the terminal should apply to all of
 them.

 Regards,
 Yihui
 --
 Yihui Xie xieyi...@gmail.com
 Web: http://yihui.name


 On Wed, Oct 22, 2014 at 4:06 AM, Rainer M Krug rai...@krugs.de wrote:
 THis seems to be a problem with paths and environmental variables passed
 to sub-processes (also mentiond on the R sig mac list): Yosemite seems
 to have implemented security mechanisms which do (to me) unknown things
 to paths and environmental variables.

 So, in a nutshell:

 1) If you do a reconfigure in LyX started from the icon / finder /
 spotlight, the reconfigure seems not to find the files needed, and does
 finish nearly immediately and does not creates an (empty?) configuration
 file

 2) If you start lyx from the terminal

 --8---cut here---start-8---
 /PATH/TO/LyX.app/Contents/MacOS/lyx
 --8---cut here---end---8---

 and reconfigure then, it is working.

 Workaround:
 Startt from terminal and reconfigure - after this everything seems to be
 working

 Solution:
 No idea, but I guess an update in LyX

 Hope this helps,

 Rainer


 Christopher Menzel chris.men...@gmail.com writes:

 Hal Kierstead wrote:
 I am trying to use LyX 2.1.2 with Yosemite, but review does not work
 for me.  I cannot even preview the help manuals.  I can export them
 to LaTex and then compile them with LaTex.  This must be some path
 problem, but I do not know how to deal with it.  Any help would be
 appreciated.

 Couple of very quick ideas:

 . Perhaps reconfiguring (Tools - reconfigure) might help.
 . If you aren't using the latest version of MacTeX
 http://tug.org/mactex/, consider upgrading.

 -chris


 --
 Rainer M. Krug
 email: Raineratkrugsdotde
 PGP: 0x0F52F982



-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Re: WORKAROUND and BUG: Yosemite + LyX

[Yihui Xie]

I do not use Mac OS X very often (I use it mostly for testing
purposes), so personally I do not care. It is easy to ditch Apple by
myself, but not all Apple users :( (Same thing for Windows)

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Web: http://yihui.name


On Wed, Oct 22, 2014 at 11:47 AM, Liviu Andronic landronim...@gmail.com wrote:
 On Wed, Oct 22, 2014 at 6:10 PM, Yihui Xie x...@yihui.name wrote:
 Yes, this may solve some problems but not all. The PATH bug is still
 there on Yosemite, and I see it can still bite me in LyX after I
 reconfigured from the terminal. For the time being, the only reliable
 solution seems to be starting LyX from the terminal.

 Or ditching Apple altogether? :)

 Liviu

WORKAROUND and BUG: Yosemite + LyX

[Rainer M Krug]

THis seems to be a problem with paths and environmental variables passed
to sub-processes (also mentiond on the R sig mac list): Yosemite seems
to have implemented security mechanisms which do (to me) unknown things
to paths and environmental variables.

So, in a nutshell:

1) If you do a reconfigure in LyX started from the icon / finder /
spotlight, the reconfigure seems not to find the files needed, and does
finish nearly immediately and does not creates an (empty?) configuration
file

2) If you start lyx from the terminal

--8---cut here---start-8---
/PATH/TO/LyX.app/Contents/MacOS/lyx
--8---cut here---end---8---

and reconfigure then, it is working.

Workaround: 
Startt from terminal and reconfigure - after this everything seems to be
working

Solution:
No idea, but I guess an update in LyX

Hope this helps,

Rainer


Christopher Menzel chris.men...@gmail.com writes:

 Hal Kierstead wrote:
 I am trying to use LyX 2.1.2 with Yosemite, but review does not work
 for me.  I cannot even preview the help manuals.  I can export them
 to LaTex and then compile them with LaTex.  This must be some path
 problem, but I do not know how to deal with it.  Any help would be
 appreciated.

 Couple of very quick ideas:

 . Perhaps reconfiguring (Tools - reconfigure) might help.
 . If you aren't using the latest version of MacTeX
 http://tug.org/mactex/, consider upgrading.

 -chris


-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


pgpYK1ccEvlVl.pgp
Description: PGP signature

Re: WORKAROUND and BUG: Yosemite + LyX

[Yihui Xie]

Yes, this may solve some problems but not all. The PATH bug is still
there on Yosemite, and I see it can still bite me in LyX after I
reconfigured from the terminal. For the time being, the only reliable
solution seems to be starting LyX from the terminal. See more info at
http://stackoverflow.com/q/26491934/559676 (and the link in the
answer). Since this is a general problem on Yosemite, you might find
other apps are affected as well (as long as they launch sub processes
and call programs that are not in /bin:/usr/bin:/sbin:/usr/sbin). The
solution of starting apps from the terminal should apply to all of
them.

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Web: http://yihui.name


On Wed, Oct 22, 2014 at 4:06 AM, Rainer M Krug rai...@krugs.de wrote:
 THis seems to be a problem with paths and environmental variables passed
 to sub-processes (also mentiond on the R sig mac list): Yosemite seems
 to have implemented security mechanisms which do (to me) unknown things
 to paths and environmental variables.

 So, in a nutshell:

 1) If you do a reconfigure in LyX started from the icon / finder /
 spotlight, the reconfigure seems not to find the files needed, and does
 finish nearly immediately and does not creates an (empty?) configuration
 file

 2) If you start lyx from the terminal

 --8---cut here---start-8---
 /PATH/TO/LyX.app/Contents/MacOS/lyx
 --8---cut here---end---8---

 and reconfigure then, it is working.

 Workaround:
 Startt from terminal and reconfigure - after this everything seems to be
 working

 Solution:
 No idea, but I guess an update in LyX

 Hope this helps,

 Rainer


 Christopher Menzel chris.men...@gmail.com writes:

 Hal Kierstead wrote:
 I am trying to use LyX 2.1.2 with Yosemite, but review does not work
 for me.  I cannot even preview the help manuals.  I can export them
 to LaTex and then compile them with LaTex.  This must be some path
 problem, but I do not know how to deal with it.  Any help would be
 appreciated.

 Couple of very quick ideas:

 . Perhaps reconfiguring (Tools - reconfigure) might help.
 . If you aren't using the latest version of MacTeX
 http://tug.org/mactex/, consider upgrading.

 -chris


 --
 Rainer M. Krug
 email: Raineratkrugsdotde
 PGP: 0x0F52F982

Re: WORKAROUND and BUG: Yosemite + LyX

[Liviu Andronic]

On Wed, Oct 22, 2014 at 6:10 PM, Yihui Xie x...@yihui.name wrote:
 Yes, this may solve some problems but not all. The PATH bug is still
 there on Yosemite, and I see it can still bite me in LyX after I
 reconfigured from the terminal. For the time being, the only reliable
 solution seems to be starting LyX from the terminal.

Or ditching Apple altogether? :)

Liviu


 See more info at
 http://stackoverflow.com/q/26491934/559676 (and the link in the
 answer). Since this is a general problem on Yosemite, you might find
 other apps are affected as well (as long as they launch sub processes
 and call programs that are not in /bin:/usr/bin:/sbin:/usr/sbin). The
 solution of starting apps from the terminal should apply to all of
 them.

 Regards,
 Yihui
 --
 Yihui Xie xieyi...@gmail.com
 Web: http://yihui.name


 On Wed, Oct 22, 2014 at 4:06 AM, Rainer M Krug rai...@krugs.de wrote:
 THis seems to be a problem with paths and environmental variables passed
 to sub-processes (also mentiond on the R sig mac list): Yosemite seems
 to have implemented security mechanisms which do (to me) unknown things
 to paths and environmental variables.

 So, in a nutshell:

 1) If you do a reconfigure in LyX started from the icon / finder /
 spotlight, the reconfigure seems not to find the files needed, and does
 finish nearly immediately and does not creates an (empty?) configuration
 file

 2) If you start lyx from the terminal

 --8---cut here---start-8---
 /PATH/TO/LyX.app/Contents/MacOS/lyx
 --8---cut here---end---8---

 and reconfigure then, it is working.

 Workaround:
 Startt from terminal and reconfigure - after this everything seems to be
 working

 Solution:
 No idea, but I guess an update in LyX

 Hope this helps,

 Rainer


 Christopher Menzel chris.men...@gmail.com writes:

 Hal Kierstead wrote:
 I am trying to use LyX 2.1.2 with Yosemite, but review does not work
 for me.  I cannot even preview the help manuals.  I can export them
 to LaTex and then compile them with LaTex.  This must be some path
 problem, but I do not know how to deal with it.  Any help would be
 appreciated.

 Couple of very quick ideas:

 . Perhaps reconfiguring (Tools - reconfigure) might help.
 . If you aren't using the latest version of MacTeX
 http://tug.org/mactex/, consider upgrading.

 -chris


 --
 Rainer M. Krug
 email: Raineratkrugsdotde
 PGP: 0x0F52F982



-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Re: WORKAROUND and BUG: Yosemite + LyX

[Yihui Xie]

I do not use Mac OS X very often (I use it mostly for testing
purposes), so personally I do not care. It is easy to ditch Apple by
myself, but not all Apple users :( (Same thing for Windows)

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Web: http://yihui.name


On Wed, Oct 22, 2014 at 11:47 AM, Liviu Andronic landronim...@gmail.com wrote:
 On Wed, Oct 22, 2014 at 6:10 PM, Yihui Xie x...@yihui.name wrote:
 Yes, this may solve some problems but not all. The PATH bug is still
 there on Yosemite, and I see it can still bite me in LyX after I
 reconfigured from the terminal. For the time being, the only reliable
 solution seems to be starting LyX from the terminal.

 Or ditching Apple altogether? :)

 Liviu

WORKAROUND and BUG: Yosemite + LyX

[Rainer M Krug]

THis seems to be a problem with paths and environmental variables passed
to sub-processes (also mentiond on the R sig mac list): Yosemite seems
to have implemented security mechanisms which do (to me) unknown things
to paths and environmental variables.

So, in a nutshell:

1) If you do a reconfigure in LyX started from the icon / finder /
spotlight, the reconfigure seems not to find the files needed, and does
finish nearly immediately and does not creates an (empty?) configuration
file

2) If you start lyx from the terminal

--8<---cut here---start->8---
/PATH/TO/LyX.app/Contents/MacOS/lyx
--8<---cut here---end--->8---

and reconfigure then, it is working.

Workaround: 
Startt from terminal and reconfigure - after this everything seems to be
working

Solution:
No idea, but I guess an update in LyX

Hope this helps,

Rainer


Christopher Menzel  writes:

> Hal Kierstead wrote:
>> I am trying to use LyX 2.1.2 with Yosemite, but review does not work
>> for me.  I cannot even preview the help manuals.  I can export them
>> to LaTex and then compile them with LaTex.  This must be some path
>> problem, but I do not know how to deal with it.  Any help would be
>> appreciated.
>
> Couple of very quick ideas:
>
> . Perhaps reconfiguring (Tools -> reconfigure) might help.
> . If you aren't using the latest version of MacTeX
> , consider upgrading.
>
> -chris
>

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


pgpYK1ccEvlVl.pgp
Description: PGP signature

Re: WORKAROUND and BUG: Yosemite + LyX

[Yihui Xie]

Yes, this may solve some problems but not all. The PATH bug is still
there on Yosemite, and I see it can still bite me in LyX after I
reconfigured from the terminal. For the time being, the only reliable
solution seems to be starting LyX from the terminal. See more info at
http://stackoverflow.com/q/26491934/559676 (and the link in the
answer). Since this is a general problem on Yosemite, you might find
other apps are affected as well (as long as they launch sub processes
and call programs that are not in /bin:/usr/bin:/sbin:/usr/sbin). The
solution of starting apps from the terminal should apply to all of
them.

Regards,
Yihui
--
Yihui Xie 
Web: http://yihui.name


On Wed, Oct 22, 2014 at 4:06 AM, Rainer M Krug  wrote:
> THis seems to be a problem with paths and environmental variables passed
> to sub-processes (also mentiond on the R sig mac list): Yosemite seems
> to have implemented security mechanisms which do (to me) unknown things
> to paths and environmental variables.
>
> So, in a nutshell:
>
> 1) If you do a reconfigure in LyX started from the icon / finder /
> spotlight, the reconfigure seems not to find the files needed, and does
> finish nearly immediately and does not creates an (empty?) configuration
> file
>
> 2) If you start lyx from the terminal
>
> --8<---cut here---start->8---
> /PATH/TO/LyX.app/Contents/MacOS/lyx
> --8<---cut here---end--->8---
>
> and reconfigure then, it is working.
>
> Workaround:
> Startt from terminal and reconfigure - after this everything seems to be
> working
>
> Solution:
> No idea, but I guess an update in LyX
>
> Hope this helps,
>
> Rainer
>
>
> Christopher Menzel  writes:
>
>> Hal Kierstead wrote:
>>> I am trying to use LyX 2.1.2 with Yosemite, but review does not work
>>> for me.  I cannot even preview the help manuals.  I can export them
>>> to LaTex and then compile them with LaTex.  This must be some path
>>> problem, but I do not know how to deal with it.  Any help would be
>>> appreciated.
>>
>> Couple of very quick ideas:
>>
>> . Perhaps reconfiguring (Tools -> reconfigure) might help.
>> . If you aren't using the latest version of MacTeX
>> , consider upgrading.
>>
>> -chris
>>
>
> --
> Rainer M. Krug
> email: Rainerkrugsde
> PGP: 0x0F52F982

Re: WORKAROUND and BUG: Yosemite + LyX

[Liviu Andronic]

On Wed, Oct 22, 2014 at 6:10 PM, Yihui Xie  wrote:
> Yes, this may solve some problems but not all. The PATH bug is still
> there on Yosemite, and I see it can still bite me in LyX after I
> reconfigured from the terminal. For the time being, the only reliable
> solution seems to be starting LyX from the terminal.
>
Or ditching Apple altogether? :)

Liviu


> See more info at
> http://stackoverflow.com/q/26491934/559676 (and the link in the
> answer). Since this is a general problem on Yosemite, you might find
> other apps are affected as well (as long as they launch sub processes
> and call programs that are not in /bin:/usr/bin:/sbin:/usr/sbin). The
> solution of starting apps from the terminal should apply to all of
> them.
>
> Regards,
> Yihui
> --
> Yihui Xie 
> Web: http://yihui.name
>
>
> On Wed, Oct 22, 2014 at 4:06 AM, Rainer M Krug  wrote:
>> THis seems to be a problem with paths and environmental variables passed
>> to sub-processes (also mentiond on the R sig mac list): Yosemite seems
>> to have implemented security mechanisms which do (to me) unknown things
>> to paths and environmental variables.
>>
>> So, in a nutshell:
>>
>> 1) If you do a reconfigure in LyX started from the icon / finder /
>> spotlight, the reconfigure seems not to find the files needed, and does
>> finish nearly immediately and does not creates an (empty?) configuration
>> file
>>
>> 2) If you start lyx from the terminal
>>
>> --8<---cut here---start->8---
>> /PATH/TO/LyX.app/Contents/MacOS/lyx
>> --8<---cut here---end--->8---
>>
>> and reconfigure then, it is working.
>>
>> Workaround:
>> Startt from terminal and reconfigure - after this everything seems to be
>> working
>>
>> Solution:
>> No idea, but I guess an update in LyX
>>
>> Hope this helps,
>>
>> Rainer
>>
>>
>> Christopher Menzel  writes:
>>
>>> Hal Kierstead wrote:
 I am trying to use LyX 2.1.2 with Yosemite, but review does not work
 for me.  I cannot even preview the help manuals.  I can export them
 to LaTex and then compile them with LaTex.  This must be some path
 problem, but I do not know how to deal with it.  Any help would be
 appreciated.
>>>
>>> Couple of very quick ideas:
>>>
>>> . Perhaps reconfiguring (Tools -> reconfigure) might help.
>>> . If you aren't using the latest version of MacTeX
>>> , consider upgrading.
>>>
>>> -chris
>>>
>>
>> --
>> Rainer M. Krug
>> email: Rainerkrugsde
>> PGP: 0x0F52F982



-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Re: WORKAROUND and BUG: Yosemite + LyX

[Yihui Xie]

I do not use Mac OS X very often (I use it mostly for testing
purposes), so personally I do not care. It is easy to ditch Apple by
myself, but not all Apple users :( (Same thing for Windows)

Regards,
Yihui
--
Yihui Xie 
Web: http://yihui.name


On Wed, Oct 22, 2014 at 11:47 AM, Liviu Andronic  wrote:
> On Wed, Oct 22, 2014 at 6:10 PM, Yihui Xie  wrote:
>> Yes, this may solve some problems but not all. The PATH bug is still
>> there on Yosemite, and I see it can still bite me in LyX after I
>> reconfigured from the terminal. For the time being, the only reliable
>> solution seems to be starting LyX from the terminal.
>>
> Or ditching Apple altogether? :)
>
> Liviu

bug in lyx-HTML conversion via tth

[travis+ml-lyx]

I wrote to the author of tth:

 Anyway, I wanted to alert you to a potential bug.  When I use lyx's
 hyperef feature to make a hyperlink (as opposed to embedding a URL,
 where the text is the same as the href target), it generates a .tex
 file that contains a line like this:

 \usepackage[unicode=true, pdfusetitle,
 bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
 breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
 {hyperref}

 When I run it through tth, it creates a title tag of hyperref.

He responded:

Hello. Thanks for this message. The problem is with the way Lyx is laying
out its \usepackage command. TtH knows nothing about \usepackage. It treats
it as an unknown command.

http://hutchinson.belmont.ma.us/tth/manual/sec9.html#commands+unknown93
explains that such commands ought to be laid out _without_ whitespace
between themselves and their arguments. Because Lyx is inserting whitespace
before {hyperref}, TtH scans it as if it is the start of the text.

The only way to fix this properly is for Lyx to avoid adding that extra
whitespace between ] and {. No space or newline is allowed. You could fix
it by hand in the .tex file yourself; but that's a bit annoying.
-- 
A Weapon of Mass Construction
My emails do not have attachments; it's a digital signature that your mail
program doesn't understand. | http://www.subspacefield.org/~travis/ 
If you are a spammer, please email j...@subspacefield.org to get blacklisted.


pgpYx08tACCKS.pgp
Description: PGP signature

bug in lyx-HTML conversion via tth

[travis+ml-lyx]

I wrote to the author of tth:

 Anyway, I wanted to alert you to a potential bug.  When I use lyx's
 hyperef feature to make a hyperlink (as opposed to embedding a URL,
 where the text is the same as the href target), it generates a .tex
 file that contains a line like this:

 \usepackage[unicode=true, pdfusetitle,
 bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
 breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
 {hyperref}

 When I run it through tth, it creates a title tag of hyperref.

He responded:

Hello. Thanks for this message. The problem is with the way Lyx is laying
out its \usepackage command. TtH knows nothing about \usepackage. It treats
it as an unknown command.

http://hutchinson.belmont.ma.us/tth/manual/sec9.html#commands+unknown93
explains that such commands ought to be laid out _without_ whitespace
between themselves and their arguments. Because Lyx is inserting whitespace
before {hyperref}, TtH scans it as if it is the start of the text.

The only way to fix this properly is for Lyx to avoid adding that extra
whitespace between ] and {. No space or newline is allowed. You could fix
it by hand in the .tex file yourself; but that's a bit annoying.
-- 
A Weapon of Mass Construction
My emails do not have attachments; it's a digital signature that your mail
program doesn't understand. | http://www.subspacefield.org/~travis/ 
If you are a spammer, please email j...@subspacefield.org to get blacklisted.


pgpYx08tACCKS.pgp
Description: PGP signature

bug in lyx->HTML conversion via tth

[travis+ml-lyx]

I wrote to the author of tth:

> Anyway, I wanted to alert you to a potential bug.  When I use lyx's
> "hyperef" feature to make a hyperlink (as opposed to embedding a URL,
> where the text is the same as the href target), it generates a .tex
> file that contains a line like this:
>
> \usepackage[unicode=true, pdfusetitle,
> bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
> breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
> {hyperref}
>
> When I run it through tth, it creates a  tag of "hyperref".

He responded:

Hello. Thanks for this message. The problem is with the way Lyx is laying
out its \usepackage command. TtH knows nothing about \usepackage. It treats
it as an unknown command.

http://hutchinson.belmont.ma.us/tth/manual/sec9.html#commands+unknown93
explains that such commands ought to be laid out _without_ whitespace
between themselves and their arguments. Because Lyx is inserting whitespace
before {hyperref}, TtH scans it as if it is the start of the text.

The only way to fix this properly is for Lyx to avoid adding that extra
whitespace between ] and {. No space or newline is allowed. You could fix
it by hand in the .tex file yourself; but that's a bit annoying.
-- 
A Weapon of Mass Construction
My emails do not have attachments; it's a digital signature that your mail
program doesn't understand. | http://www.subspacefield.org/~travis/ 
If you are a spammer, please email j...@subspacefield.org to get blacklisted.


pgpYx08tACCKS.pgp
Description: PGP signature

Re: [bug report] Lyx 1.6.4 crashes while editing formula

[Olivier Ripoll]

Falk Sticken wrote:

Hi
I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not
reported in the bug tracker. When I start editing an inline math formula
(ALT+M M) and type 
\mathc 
SPACE 
BACKSPACE 
al 
SPACE 
LyX crashes.

A backtrace follows below.
bye,
Falk


Hi,

I can reproduce on windows (alt installer) if I replace the BACKSPACE by 
a left arrow (backspace will select the full \mathc and al will 
replace it)


There is coincidently a crash report on lyx-french on Mac/Windows when 
correcting an index/exponent in an equation.


But both look to me like incarnations of this bug, fixed 8 hours ago:
http://www.lyx.org/trac/ticket/6193

Best regards,

Olivier

RE: Re: [bug report] Lyx 1.6.4 crashes while editing formula

[Vincent van Ravesteijn - TNW]

 

Falk Sticken wrote:
 Hi
 I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not

 reported in the bug tracker. When I start editing an inline math 
 formula (ALT+M M) and type \mathc
 SPACE
 BACKSPACE
 al 
 SPACE
 LyX crashes.
 A backtrace follows below.
 bye,
 Falk

But both look to me like incarnations of this bug,
fixed 8 hours ago:
http://www.lyx.org/trac/ticket/6193


It seems more like bug http://www.lyx.org/trac/ticket/6110 to me.

Vincent

Re: [bug report] Lyx 1.6.4 crashes while editing formula

[Olivier Ripoll]

Vincent van Ravesteijn - TNW wrote:
 


Falk Sticken wrote:

Hi
I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not


reported in the bug tracker. When I start editing an inline math 
formula (ALT+M M) and type \mathc

SPACE
BACKSPACE
al 
SPACE

LyX crashes.
A backtrace follows below.
bye,
Falk

But both look to me like incarnations of this bug,
fixed 8 hours ago:
http://www.lyx.org/trac/ticket/6193



It seems more like bug http://www.lyx.org/trac/ticket/6110 to me.



You're right. The half-good news being both are fixed in trunk.

Best regards,

Olivier


Vincent

Re: [bug report] Lyx 1.6.4 crashes while editing formula

[Olivier Ripoll]

Falk Sticken wrote:

Hi
I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not
reported in the bug tracker. When I start editing an inline math formula
(ALT+M M) and type 
\mathc 
SPACE 
BACKSPACE 
al 
SPACE 
LyX crashes.

A backtrace follows below.
bye,
Falk


Hi,

I can reproduce on windows (alt installer) if I replace the BACKSPACE by 
a left arrow (backspace will select the full \mathc and al will 
replace it)


There is coincidently a crash report on lyx-french on Mac/Windows when 
correcting an index/exponent in an equation.


But both look to me like incarnations of this bug, fixed 8 hours ago:
http://www.lyx.org/trac/ticket/6193

Best regards,

Olivier

RE: Re: [bug report] Lyx 1.6.4 crashes while editing formula

[Vincent van Ravesteijn - TNW]

 

Falk Sticken wrote:
 Hi
 I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not

 reported in the bug tracker. When I start editing an inline math 
 formula (ALT+M M) and type \mathc
 SPACE
 BACKSPACE
 al 
 SPACE
 LyX crashes.
 A backtrace follows below.
 bye,
 Falk

But both look to me like incarnations of this bug,
fixed 8 hours ago:
http://www.lyx.org/trac/ticket/6193


It seems more like bug http://www.lyx.org/trac/ticket/6110 to me.

Vincent

Re: [bug report] Lyx 1.6.4 crashes while editing formula

[Olivier Ripoll]

Vincent van Ravesteijn - TNW wrote:
 


Falk Sticken wrote:

Hi
I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not


reported in the bug tracker. When I start editing an inline math 
formula (ALT+M M) and type \mathc

SPACE
BACKSPACE
al 
SPACE

LyX crashes.
A backtrace follows below.
bye,
Falk

But both look to me like incarnations of this bug,
fixed 8 hours ago:
http://www.lyx.org/trac/ticket/6193



It seems more like bug http://www.lyx.org/trac/ticket/6110 to me.



You're right. The half-good news being both are fixed in trunk.

Best regards,

Olivier


Vincent

Re: [bug report] Lyx 1.6.4 crashes while editing formula

[Olivier Ripoll]

Falk Sticken wrote:

Hi
I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not
reported in the bug tracker. When I start editing an inline math formula
(ALT+M M) and type 
"\mathc" 
SPACE 
BACKSPACE 
"al" 
SPACE 
LyX crashes.

A backtrace follows below.
bye,
Falk


Hi,

I can reproduce on windows (alt installer) if I replace the BACKSPACE by 
a left arrow (backspace will select the full \mathc and "al" will 
replace it)


There is coincidently a crash report on lyx-french on Mac/Windows when 
correcting an index/exponent in an equation.


But both look to me like incarnations of this bug, fixed 8 hours ago:
http://www.lyx.org/trac/ticket/6193

Best regards,

Olivier

RE: Re: [bug report] Lyx 1.6.4 crashes while editing formula

[Vincent van Ravesteijn - TNW]

 

>Falk Sticken wrote:
>> Hi
>> I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not

>> reported in the bug tracker. When I start editing an inline math 
>> formula (ALT+M M) and type "\mathc"
>> SPACE
>> BACKSPACE
>> "al" 
>> SPACE
>> LyX crashes.
>> A backtrace follows below.
>> bye,
>> Falk
>
>But both look to me like incarnations of this bug,
>fixed 8 hours ago:
>http://www.lyx.org/trac/ticket/6193
>

It seems more like bug http://www.lyx.org/trac/ticket/6110 to me.

Vincent

Re: [bug report] Lyx 1.6.4 crashes while editing formula

[Olivier Ripoll]

Vincent van Ravesteijn - TNW wrote:
 


Falk Sticken wrote:

Hi
I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not


reported in the bug tracker. When I start editing an inline math 
formula (ALT+M M) and type "\mathc"

SPACE
BACKSPACE
"al" 
SPACE

LyX crashes.
A backtrace follows below.
bye,
Falk

But both look to me like incarnations of this bug,
fixed 8 hours ago:
http://www.lyx.org/trac/ticket/6193



It seems more like bug http://www.lyx.org/trac/ticket/6110 to me.



You're right. The half-good news being both are "fixed in trunk".

Best regards,

Olivier


Vincent

[bug report] Lyx 1.6.4 crashes while editing formula

[Falk Sticken]

Hi
I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not
reported in the bug tracker. When I start editing an inline math formula
(ALT+M M) and type 
\mathc 
SPACE 
BACKSPACE 
al 
SPACE 
LyX crashes.
A backtrace follows below.
bye,
Falk

#0  0xb6fcd3b8 in ?? () from /lib/libc.so.6
#1  0x080d541a in lyx::DocIterator::innerParagraph() const ()
#2  0x081d47ba in lyx::samePar(lyx::DocIterator const, lyx::DocIterator
const) ()
#3  0x081d4f67 in lyx::BufferView::setInlineCompletion(lyx::Cursor,
lyx::DocIterator const, std::basic_stringwchar_t,
std::char_traitswchar_t, std::allocatorwchar_t  const, unsigned
int) ()
#4  0x0841eceb in lyx::frontend::GuiCompleter::hideInline(lyx::Cursor)
()
#5  0x0841fb21 in
lyx::frontend::GuiCompleter::updateVisibility(lyx::Cursor, bool, bool,
bool) ()
#6  0x0839f166 in lyx::frontend::GuiView::updateCompletion(lyx::Cursor,
bool, bool) ()
#7  0x081356e8 in lyx::LyXFunc::dispatch(lyx::FuncRequest const) ()
#8  0x08137d83 in lyx::LyXFunc::processKeySym(lyx::KeySymbol const,
lyx::KeyModifier) ()
#9  0x083bd401 in lyx::frontend::GuiWorkArea::keyPressEvent(QKeyEvent*)
()
#10 0xb784691e in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#11 0xb7b7ca83 in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4
#12 0xb7c13c8d in QAbstractScrollArea::event(QEvent*) ()
   from /usr/lib/libQtGui.so.4
#13 0x083ba1bf in lyx::frontend::GuiWorkArea::event(QEvent*) ()
#14 0xb77ee8fc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
   from /usr/lib/libQtGui.so.4
---Type return to continue, or q return to quit---
#15 0xb77f7836 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libQtGui.so.4
#16 0x08381208 in lyx::frontend::GuiApplication::notify(QObject*,
QEvent*) ()
#17 0xb7593961 in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib/libQtCore.so.4
#18 0xb784f4be in ?? () from /usr/lib/libQtGui.so.4
#19 0xb7884470 in ?? () from /usr/lib/libQtGui.so.4
#20 0xb7886606 in ?? () from /usr/lib/libQtGui.so.4
#21 0xb785ebd5 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/libQtGui.so.4
#22 0xb788808a in ?? () from /usr/lib/libQtGui.so.4
#23 0xb73b99a8 in g_main_context_dispatch ()
from /usr/lib/libglib-2.0.so.0
#24 0xb73bd063 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb73bd221 in g_main_context_iteration ()
from /usr/lib/libglib-2.0.so.0
#26 0xb75bdfb8 in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/libQtCore.so.4
#27 0xb7887785 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb759201a in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /usr/lib/libQtCore.so.4
#29 0xb75921da in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) ()
   from /usr/lib/libQtCore.so.4
#30 0xb7594895 in QCoreApplication::exec() ()
from /usr/lib/libQtCore.so.4
#31 0xb77ee777 in QApplication::exec() () from /usr/lib/libQtGui.so.4
---Type return to continue, or q return to quit---
#32 0x081235fe in lyx::LyX::exec(int, char**) ()
#33 0x08071fa9 in main ()

[bug report] Lyx 1.6.4 crashes while editing formula

[Falk Sticken]

Hi
I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not
reported in the bug tracker. When I start editing an inline math formula
(ALT+M M) and type 
\mathc 
SPACE 
BACKSPACE 
al 
SPACE 
LyX crashes.
A backtrace follows below.
bye,
Falk

#0  0xb6fcd3b8 in ?? () from /lib/libc.so.6
#1  0x080d541a in lyx::DocIterator::innerParagraph() const ()
#2  0x081d47ba in lyx::samePar(lyx::DocIterator const, lyx::DocIterator
const) ()
#3  0x081d4f67 in lyx::BufferView::setInlineCompletion(lyx::Cursor,
lyx::DocIterator const, std::basic_stringwchar_t,
std::char_traitswchar_t, std::allocatorwchar_t  const, unsigned
int) ()
#4  0x0841eceb in lyx::frontend::GuiCompleter::hideInline(lyx::Cursor)
()
#5  0x0841fb21 in
lyx::frontend::GuiCompleter::updateVisibility(lyx::Cursor, bool, bool,
bool) ()
#6  0x0839f166 in lyx::frontend::GuiView::updateCompletion(lyx::Cursor,
bool, bool) ()
#7  0x081356e8 in lyx::LyXFunc::dispatch(lyx::FuncRequest const) ()
#8  0x08137d83 in lyx::LyXFunc::processKeySym(lyx::KeySymbol const,
lyx::KeyModifier) ()
#9  0x083bd401 in lyx::frontend::GuiWorkArea::keyPressEvent(QKeyEvent*)
()
#10 0xb784691e in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#11 0xb7b7ca83 in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4
#12 0xb7c13c8d in QAbstractScrollArea::event(QEvent*) ()
   from /usr/lib/libQtGui.so.4
#13 0x083ba1bf in lyx::frontend::GuiWorkArea::event(QEvent*) ()
#14 0xb77ee8fc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
   from /usr/lib/libQtGui.so.4
---Type return to continue, or q return to quit---
#15 0xb77f7836 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libQtGui.so.4
#16 0x08381208 in lyx::frontend::GuiApplication::notify(QObject*,
QEvent*) ()
#17 0xb7593961 in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib/libQtCore.so.4
#18 0xb784f4be in ?? () from /usr/lib/libQtGui.so.4
#19 0xb7884470 in ?? () from /usr/lib/libQtGui.so.4
#20 0xb7886606 in ?? () from /usr/lib/libQtGui.so.4
#21 0xb785ebd5 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/libQtGui.so.4
#22 0xb788808a in ?? () from /usr/lib/libQtGui.so.4
#23 0xb73b99a8 in g_main_context_dispatch ()
from /usr/lib/libglib-2.0.so.0
#24 0xb73bd063 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb73bd221 in g_main_context_iteration ()
from /usr/lib/libglib-2.0.so.0
#26 0xb75bdfb8 in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/libQtCore.so.4
#27 0xb7887785 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb759201a in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /usr/lib/libQtCore.so.4
#29 0xb75921da in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) ()
   from /usr/lib/libQtCore.so.4
#30 0xb7594895 in QCoreApplication::exec() ()
from /usr/lib/libQtCore.so.4
#31 0xb77ee777 in QApplication::exec() () from /usr/lib/libQtGui.so.4
---Type return to continue, or q return to quit---
#32 0x081235fe in lyx::LyX::exec(int, char**) ()
#33 0x08071fa9 in main ()

[bug report] Lyx 1.6.4 crashes while editing formula

[Falk Sticken]

Hi
I have found a bug in LyX 1.6.4 on Linux (openSUSE 11.1) which is not
reported in the bug tracker. When I start editing an inline math formula
(ALT+M M) and type 
"\mathc" 
SPACE 
BACKSPACE 
"al" 
SPACE 
LyX crashes.
A backtrace follows below.
bye,
Falk

#0  0xb6fcd3b8 in ?? () from /lib/libc.so.6
#1  0x080d541a in lyx::DocIterator::innerParagraph() const ()
#2  0x081d47ba in lyx::samePar(lyx::DocIterator const&, lyx::DocIterator
const&) ()
#3  0x081d4f67 in lyx::BufferView::setInlineCompletion(lyx::Cursor&,
lyx::DocIterator const&, std::basic_string<wchar_t,
std::char_traits, std::allocator > const&, unsigned
int) ()
#4  0x0841eceb in lyx::frontend::GuiCompleter::hideInline(lyx::Cursor&)
()
#5  0x0841fb21 in
lyx::frontend::GuiCompleter::updateVisibility(lyx::Cursor&, bool, bool,
bool) ()
#6  0x0839f166 in lyx::frontend::GuiView::updateCompletion(lyx::Cursor&,
bool, bool) ()
#7  0x081356e8 in lyx::LyXFunc::dispatch(lyx::FuncRequest const&) ()
#8  0x08137d83 in lyx::LyXFunc::processKeySym(lyx::KeySymbol const&,
lyx::KeyModifier) ()
#9  0x083bd401 in lyx::frontend::GuiWorkArea::keyPressEvent(QKeyEvent*)
()
#10 0xb784691e in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#11 0xb7b7ca83 in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4
#12 0xb7c13c8d in QAbstractScrollArea::event(QEvent*) ()
   from /usr/lib/libQtGui.so.4
#13 0x083ba1bf in lyx::frontend::GuiWorkArea::event(QEvent*) ()
#14 0xb77ee8fc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
   from /usr/lib/libQtGui.so.4
---Type  to continue, or q  to quit---
#15 0xb77f7836 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libQtGui.so.4
#16 0x08381208 in lyx::frontend::GuiApplication::notify(QObject*,
QEvent*) ()
#17 0xb7593961 in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib/libQtCore.so.4
#18 0xb784f4be in ?? () from /usr/lib/libQtGui.so.4
#19 0xb7884470 in ?? () from /usr/lib/libQtGui.so.4
#20 0xb7886606 in ?? () from /usr/lib/libQtGui.so.4
#21 0xb785ebd5 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/libQtGui.so.4
#22 0xb788808a in ?? () from /usr/lib/libQtGui.so.4
#23 0xb73b99a8 in g_main_context_dispatch ()
from /usr/lib/libglib-2.0.so.0
#24 0xb73bd063 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb73bd221 in g_main_context_iteration ()
from /usr/lib/libglib-2.0.so.0
#26 0xb75bdfb8 in
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/libQtCore.so.4
#27 0xb7887785 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb759201a in
QEventLoop::processEvents(QFlags) ()
from /usr/lib/libQtCore.so.4
#29 0xb75921da in
QEventLoop::exec(QFlags) ()
   from /usr/lib/libQtCore.so.4
#30 0xb7594895 in QCoreApplication::exec() ()
from /usr/lib/libQtCore.so.4
#31 0xb77ee777 in QApplication::exec() () from /usr/lib/libQtGui.so.4
---Type  to continue, or q  to quit---
#32 0x081235fe in lyx::LyX::exec(int&, char**) ()
#33 0x08071fa9 in main ()

Re: Bug in LyX 1.6.0

[Jürgen Spitzmüller]

Stefano Franchi wrote:
 X Error: RenderBadPicture (invalid Picture parameter) 182
   Extension:    156 (RENDER)
   Minor opcode: 7 (RenderFreePicture)
   Resource id:  0x2b2e6fa
 X Error: BadPixmap (invalid Pixmap parameter) 4
   Major opcode: 54 (X_FreePixmap)
   Resource id:  0x2b2e6f9


There's a similar report here:
http://bugzilla.lyx.org/show_bug.cgi?id=5501

Maybe you can add some input.

Jürgen

Re: Bug in LyX 1.6.0

[Stefano Franchi]

On Sunday 23 November 2008 03:55:29 am Jürgen Spitzmüller wrote:
 Stefano Franchi wrote:
  X Error: RenderBadPicture (invalid Picture parameter) 182
    Extension:    156 (RENDER)
    Minor opcode: 7 (RenderFreePicture)
    Resource id:  0x2b2e6fa
  X Error: BadPixmap (invalid Pixmap parameter) 4
    Major opcode: 54 (X_FreePixmap)
    Resource id:  0x2b2e6f9

 There's a similar report here:
 http://bugzilla.lyx.org/show_bug.cgi?id=5501

 Maybe you can add some input.

 Jürgen

Ok, I did it.

Stefano
-- 
__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  [EMAIL PROTECTED]
College Station, TX 77843-4237

Re: Bug in LyX 1.6.0

[Jürgen Spitzmüller]

Stefano Franchi wrote:
 X Error: RenderBadPicture (invalid Picture parameter) 182
   Extension:    156 (RENDER)
   Minor opcode: 7 (RenderFreePicture)
   Resource id:  0x2b2e6fa
 X Error: BadPixmap (invalid Pixmap parameter) 4
   Major opcode: 54 (X_FreePixmap)
   Resource id:  0x2b2e6f9


There's a similar report here:
http://bugzilla.lyx.org/show_bug.cgi?id=5501

Maybe you can add some input.

Jürgen

Re: Bug in LyX 1.6.0

[Stefano Franchi]

On Sunday 23 November 2008 03:55:29 am Jürgen Spitzmüller wrote:
 Stefano Franchi wrote:
  X Error: RenderBadPicture (invalid Picture parameter) 182
    Extension:    156 (RENDER)
    Minor opcode: 7 (RenderFreePicture)
    Resource id:  0x2b2e6fa
  X Error: BadPixmap (invalid Pixmap parameter) 4
    Major opcode: 54 (X_FreePixmap)
    Resource id:  0x2b2e6f9

 There's a similar report here:
 http://bugzilla.lyx.org/show_bug.cgi?id=5501

 Maybe you can add some input.

 Jürgen

Ok, I did it.

Stefano
-- 
__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  [EMAIL PROTECTED]
College Station, TX 77843-4237

Re: Bug in LyX 1.6.0

[Jürgen Spitzmüller]

Stefano Franchi wrote:
> X Error: RenderBadPicture (invalid Picture parameter) 182
>   Extension:    156 (RENDER)
>   Minor opcode: 7 (RenderFreePicture)
>   Resource id:  0x2b2e6fa
> X Error: BadPixmap (invalid Pixmap parameter) 4
>   Major opcode: 54 (X_FreePixmap)
>   Resource id:  0x2b2e6f9


There's a similar report here:
http://bugzilla.lyx.org/show_bug.cgi?id=5501

Maybe you can add some input.

Jürgen

Re: Bug in LyX 1.6.0

[Stefano Franchi]

On Sunday 23 November 2008 03:55:29 am Jürgen Spitzmüller wrote:
> Stefano Franchi wrote:
> > X Error: RenderBadPicture (invalid Picture parameter) 182
> >   Extension:    156 (RENDER)
> >   Minor opcode: 7 (RenderFreePicture)
> >   Resource id:  0x2b2e6fa
> > X Error: BadPixmap (invalid Pixmap parameter) 4
> >   Major opcode: 54 (X_FreePixmap)
> >   Resource id:  0x2b2e6f9
>
> There's a similar report here:
> http://bugzilla.lyx.org/show_bug.cgi?id=5501
>
> Maybe you can add some input.
>
> Jürgen

Ok, I did it.

Stefano
-- 
__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas A University  Fax: (979) 845-0458
305B Bolton Hall  [EMAIL PROTECTED]
College Station, TX 77843-4237

Bug in LyX 1.6.0

[Stefano Franchi]

I had a strange behavior occurring in my last LyX session:

I was happily writing in the main editing window, while having the outline 
open in a separate window and on a separate monitor when suddenly the main 
window went blank. And I really mean blank: the editing pane became a white 
blanket (I use the default pink as background color). Interestingly, the tab I 
had open on another file was completely unaffected.

 I had not been saving for a while, so I was afraid I had lost some work. To 
my surprise, the window was still responsive, the menus were visible and 
accessible, etc. I could save my file, leave LyX and restart. On the console, I 
had a few screenful of errors of this kind:

X Error: RenderBadPicture (invalid Picture parameter) 182
  Extension:156 (RENDER)
  Minor opcode: 7 (RenderFreePicture)
  Resource id:  0x2b2e6fa
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2b2e6f9

When I quit LyX, the following messages appeared on the console:
QClipboard::setData: Cannot set X11 selection owner for CLIPBOARD   
 
X Error of failed request:  RenderBadPicture (invalid Picture parameter)
 
  Major opcode of failed request:  156 (RENDER) 
 
  Minor opcode of failed request:  7 (RenderFreePicture)
 
  Picture id in failed request: 0x2b4a448   
 
  Serial number of failed request:  58441931
 
  Current serial number in output stream:  58446888 
 
Locking assertion failure.  Backtrace:  
 
#0 /usr/lib/libxcb-xlib.so.0 [0x7fc53c5d29fc]   
 
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x17) [0x7fc53c5d2b77]   
 
#2 /usr/lib/libX11.so.6 [0x7fc53e63d8c0]
 
#3 /usr/lib/libXrender.so.1(XRenderFreePicture+0x46) [0x7fc53d0a8a26]   
 
#4 /usr/lib/libQtGui.so.4 [0x7fc53f8c3cfb]  
 
#5 /usr/lib/libQtGui.so.4 [0x7fc53f8c4680]  
 
#6 /usr/lib/libQtGui.so.4(_ZN7QPixmap5derefEv+0x53) [0x7fc53f8b9fa3]
 
#7 /usr/lib/libQtGui.so.4(_ZN7QPixmapD1Ev+0x24) [0x7fc53f8ba2e4]
#8 /usr/lib/kde4/plugins/styles/oxygen.so [0x7fc53a625b2c]
#9 /usr/lib/kde4/plugins/styles/oxygen.so [0x7fc53a62f327]
#10 /usr/lib/kde4/plugins/styles/oxygen.so [0x7fc53a630237]
#11 /lib/libc.so.6(exit+0x9d) [0x7fc53eb4e66d]
#12 /usr/lib/libX11.so.6 [0x7fc53e6365ed]
#13 /usr/lib/libX11.so.6(_XError+0xf4) [0x7fc53e636784]
#14 /usr/lib/libX11.so.6 [0x7fc53e63e20f]
#15 /usr/lib/libX11.so.6(_XReply+0x18a) [0x7fc53e63e5ba]
#16 /usr/lib/libX11.so.6(XSync+0x63) [0x7fc53e631ff3]
#17 /usr/lib/libX11.so.6(XCloseDisplay+0x70) [0x7fc53e610b80]
#18 /usr/lib/libQtGui.so.4 [0x7fc53f85d7cd]
#19 /usr/lib/libQtGui.so.4(_ZN12QApplicationD2Ev+0x5b8) [0x7fc53f8088d8]


Cheers,

S.

-- 
__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  [EMAIL PROTECTED]
College Station, TX 77843-4237

Bug in LyX 1.6.0

[Stefano Franchi]

I had a strange behavior occurring in my last LyX session:

I was happily writing in the main editing window, while having the outline 
open in a separate window and on a separate monitor when suddenly the main 
window went blank. And I really mean blank: the editing pane became a white 
blanket (I use the default pink as background color). Interestingly, the tab I 
had open on another file was completely unaffected.

 I had not been saving for a while, so I was afraid I had lost some work. To 
my surprise, the window was still responsive, the menus were visible and 
accessible, etc. I could save my file, leave LyX and restart. On the console, I 
had a few screenful of errors of this kind:

X Error: RenderBadPicture (invalid Picture parameter) 182
  Extension:156 (RENDER)
  Minor opcode: 7 (RenderFreePicture)
  Resource id:  0x2b2e6fa
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2b2e6f9

When I quit LyX, the following messages appeared on the console:
QClipboard::setData: Cannot set X11 selection owner for CLIPBOARD   
 
X Error of failed request:  RenderBadPicture (invalid Picture parameter)
 
  Major opcode of failed request:  156 (RENDER) 
 
  Minor opcode of failed request:  7 (RenderFreePicture)
 
  Picture id in failed request: 0x2b4a448   
 
  Serial number of failed request:  58441931
 
  Current serial number in output stream:  58446888 
 
Locking assertion failure.  Backtrace:  
 
#0 /usr/lib/libxcb-xlib.so.0 [0x7fc53c5d29fc]   
 
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x17) [0x7fc53c5d2b77]   
 
#2 /usr/lib/libX11.so.6 [0x7fc53e63d8c0]
 
#3 /usr/lib/libXrender.so.1(XRenderFreePicture+0x46) [0x7fc53d0a8a26]   
 
#4 /usr/lib/libQtGui.so.4 [0x7fc53f8c3cfb]  
 
#5 /usr/lib/libQtGui.so.4 [0x7fc53f8c4680]  
 
#6 /usr/lib/libQtGui.so.4(_ZN7QPixmap5derefEv+0x53) [0x7fc53f8b9fa3]
 
#7 /usr/lib/libQtGui.so.4(_ZN7QPixmapD1Ev+0x24) [0x7fc53f8ba2e4]
#8 /usr/lib/kde4/plugins/styles/oxygen.so [0x7fc53a625b2c]
#9 /usr/lib/kde4/plugins/styles/oxygen.so [0x7fc53a62f327]
#10 /usr/lib/kde4/plugins/styles/oxygen.so [0x7fc53a630237]
#11 /lib/libc.so.6(exit+0x9d) [0x7fc53eb4e66d]
#12 /usr/lib/libX11.so.6 [0x7fc53e6365ed]
#13 /usr/lib/libX11.so.6(_XError+0xf4) [0x7fc53e636784]
#14 /usr/lib/libX11.so.6 [0x7fc53e63e20f]
#15 /usr/lib/libX11.so.6(_XReply+0x18a) [0x7fc53e63e5ba]
#16 /usr/lib/libX11.so.6(XSync+0x63) [0x7fc53e631ff3]
#17 /usr/lib/libX11.so.6(XCloseDisplay+0x70) [0x7fc53e610b80]
#18 /usr/lib/libQtGui.so.4 [0x7fc53f85d7cd]
#19 /usr/lib/libQtGui.so.4(_ZN12QApplicationD2Ev+0x5b8) [0x7fc53f8088d8]


Cheers,

S.

-- 
__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  [EMAIL PROTECTED]
College Station, TX 77843-4237

Bug in LyX 1.6.0

[Stefano Franchi]

I had a strange behavior occurring in my last LyX session:

I was happily writing in the main editing window, while having the outline 
open in a separate window and on a separate monitor when suddenly the main 
window went blank. And I really mean blank: the editing pane became a white 
blanket (I use the default pink as background color). Interestingly, the tab I 
had open on another file was completely unaffected.

 I had not been saving for a while, so I was afraid I had lost some work. To 
my surprise, the window was still responsive, the menus were visible and 
accessible, etc. I could save my file, leave LyX and restart. On the console, I 
had a few screenful of errors of this kind:

X Error: RenderBadPicture (invalid Picture parameter) 182
  Extension:156 (RENDER)
  Minor opcode: 7 (RenderFreePicture)
  Resource id:  0x2b2e6fa
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2b2e6f9

When I quit LyX, the following messages appeared on the console:
QClipboard::setData: Cannot set X11 selection owner for CLIPBOARD   
 
X Error of failed request:  RenderBadPicture (invalid Picture parameter)
 
  Major opcode of failed request:  156 (RENDER) 
 
  Minor opcode of failed request:  7 (RenderFreePicture)
 
  Picture id in failed request: 0x2b4a448   
 
  Serial number of failed request:  58441931
 
  Current serial number in output stream:  58446888 
 
Locking assertion failure.  Backtrace:  
 
#0 /usr/lib/libxcb-xlib.so.0 [0x7fc53c5d29fc]   
 
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x17) [0x7fc53c5d2b77]   
 
#2 /usr/lib/libX11.so.6 [0x7fc53e63d8c0]
 
#3 /usr/lib/libXrender.so.1(XRenderFreePicture+0x46) [0x7fc53d0a8a26]   
 
#4 /usr/lib/libQtGui.so.4 [0x7fc53f8c3cfb]  
 
#5 /usr/lib/libQtGui.so.4 [0x7fc53f8c4680]  
 
#6 /usr/lib/libQtGui.so.4(_ZN7QPixmap5derefEv+0x53) [0x7fc53f8b9fa3]
 
#7 /usr/lib/libQtGui.so.4(_ZN7QPixmapD1Ev+0x24) [0x7fc53f8ba2e4]
#8 /usr/lib/kde4/plugins/styles/oxygen.so [0x7fc53a625b2c]
#9 /usr/lib/kde4/plugins/styles/oxygen.so [0x7fc53a62f327]
#10 /usr/lib/kde4/plugins/styles/oxygen.so [0x7fc53a630237]
#11 /lib/libc.so.6(exit+0x9d) [0x7fc53eb4e66d]
#12 /usr/lib/libX11.so.6 [0x7fc53e6365ed]
#13 /usr/lib/libX11.so.6(_XError+0xf4) [0x7fc53e636784]
#14 /usr/lib/libX11.so.6 [0x7fc53e63e20f]
#15 /usr/lib/libX11.so.6(_XReply+0x18a) [0x7fc53e63e5ba]
#16 /usr/lib/libX11.so.6(XSync+0x63) [0x7fc53e631ff3]
#17 /usr/lib/libX11.so.6(XCloseDisplay+0x70) [0x7fc53e610b80]
#18 /usr/lib/libQtGui.so.4 [0x7fc53f85d7cd]
#19 /usr/lib/libQtGui.so.4(_ZN12QApplicationD2Ev+0x5b8) [0x7fc53f8088d8]


Cheers,

S.

-- 
__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas A University  Fax: (979) 845-0458
305B Bolton Hall  [EMAIL PROTECTED]
College Station, TX 77843-4237

Possible bug of LyX 1.6.0rc4 / Clipboard

[Andre Bonhote]

Hi

Maybe it's the wrong list, but I hope someone is going to forward to the
correct place. I have an issue here with LyX 1.6.0rc4 on Windows XP. I think
I found the culprit, too: It's a small tool called Clipboard Help+Spell. You
can get it here [1].

Fact is: If CBHAS is running, LyX crashes when bigger portions of text or
tables get copied to the clipboard. Yes, LyX crashes, not CBHAS ;-) As soon
as I turn the latter off, it works smoothly.

Maybe this is fixed in rc5 already.

Regards

André

[1]
http://www.donationcoder.com/Software/Mouser/clipboardhelpandspell/index.html

Possible bug of LyX 1.6.0rc4 / Clipboard

[Andre Bonhote]

Hi

Maybe it's the wrong list, but I hope someone is going to forward to the
correct place. I have an issue here with LyX 1.6.0rc4 on Windows XP. I think
I found the culprit, too: It's a small tool called Clipboard Help+Spell. You
can get it here [1].

Fact is: If CBHAS is running, LyX crashes when bigger portions of text or
tables get copied to the clipboard. Yes, LyX crashes, not CBHAS ;-) As soon
as I turn the latter off, it works smoothly.

Maybe this is fixed in rc5 already.

Regards

André

[1]
http://www.donationcoder.com/Software/Mouser/clipboardhelpandspell/index.html

Possible bug of LyX 1.6.0rc4 / Clipboard

[Andre Bonhote]

Hi

Maybe it's the wrong list, but I hope someone is going to forward to the
correct place. I have an issue here with LyX 1.6.0rc4 on Windows XP. I think
I found the culprit, too: It's a small tool called Clipboard Help+Spell. You
can get it here [1].

Fact is: If CBHAS is running, LyX crashes when bigger portions of text or
tables get copied to the clipboard. Yes, LyX crashes, not CBHAS ;-) As soon
as I turn the latter off, it works smoothly.

Maybe this is fixed in rc5 already.

Regards

André

[1]
http://www.donationcoder.com/Software/Mouser/clipboardhelpandspell/index.html

Bug in LyX 1.6.0rc?

[Juha Meriluoto]

When I open a document (any help file will do) and click on table of
contents box the catalog sidebar opens but is empty.  I have to select
something else to show from the drop menu, e.g. list of graphics, then
table of contents again and everything works ok.  This concerns
LyXWinInstaller, both rc1 and rc2.  I'm running on WinXP SP3.

 - Juha

Bug in LyX 1.6.0rc?

[Juha Meriluoto]

When I open a document (any help file will do) and click on table of
contents box the catalog sidebar opens but is empty.  I have to select
something else to show from the drop menu, e.g. list of graphics, then
table of contents again and everything works ok.  This concerns
LyXWinInstaller, both rc1 and rc2.  I'm running on WinXP SP3.

 - Juha

Bug in LyX 1.6.0rc?

[Juha Meriluoto]

When I open a document (any help file will do) and click on "table of
contents" box the catalog sidebar opens but is empty.  I have to select
something else to show from the drop menu, e.g. list of graphics, then
table of contents again and everything works ok.  This concerns
LyXWinInstaller, both rc1 and rc2.  I'm running on WinXP SP3.

 - Juha

Bug in LyX 1.6-RC1

[Mukhtar Ullah]

I don't know if it is a known bug, but LyX 1.6-RC1 crashes whenever I try to
copy a piece of text that contains ERT from one LyX document to another.

Can anyone confirm this?

Mukhtar

Re: Bug in LyX 1.6-RC1

[Pavel Sanda]

 I don't know if it is a known bug, but LyX 1.6-RC1 crashes whenever I try to
 copy a piece of text that contains ERT from one LyX document to another.
 
 Can anyone confirm this?

no, can you confirm it on rc2?
pavel

Re: Bug in LyX 1.6-RC1

[Olivier Ripoll]

Mukhtar Ullah wrote:

I don't know if it is a known bug, but LyX 1.6-RC1 crashes whenever I try to
copy a piece of text that contains ERT from one LyX document to another.

Can anyone confirm this?


Yes, indeed, it just crashed on WinXP when trying that.
Are you using windows? MacOS ? linux ?
(Un)fortunately, now, I cannot reproduce it any more... which seems to 
be the case with several 1.6 crashes.


Best regards,

Olivier



Mukhtar

Bug in LyX 1.6-RC1

[Mukhtar Ullah]

I don't know if it is a known bug, but LyX 1.6-RC1 crashes whenever I try to
copy a piece of text that contains ERT from one LyX document to another.

Can anyone confirm this?

Mukhtar

Re: Bug in LyX 1.6-RC1

[Pavel Sanda]

 I don't know if it is a known bug, but LyX 1.6-RC1 crashes whenever I try to
 copy a piece of text that contains ERT from one LyX document to another.
 
 Can anyone confirm this?

no, can you confirm it on rc2?
pavel

Re: Bug in LyX 1.6-RC1

[Olivier Ripoll]

Mukhtar Ullah wrote:

I don't know if it is a known bug, but LyX 1.6-RC1 crashes whenever I try to
copy a piece of text that contains ERT from one LyX document to another.

Can anyone confirm this?


Yes, indeed, it just crashed on WinXP when trying that.
Are you using windows? MacOS ? linux ?
(Un)fortunately, now, I cannot reproduce it any more... which seems to 
be the case with several 1.6 crashes.


Best regards,

Olivier



Mukhtar

Bug in LyX 1.6-RC1

[Mukhtar Ullah]

I don't know if it is a known bug, but LyX 1.6-RC1 crashes whenever I try to
copy a piece of text that contains ERT from one LyX document to another.

Can anyone confirm this?

Mukhtar

Re: Bug in LyX 1.6-RC1

[Pavel Sanda]

> I don't know if it is a known bug, but LyX 1.6-RC1 crashes whenever I try to
> copy a piece of text that contains ERT from one LyX document to another.
> 
> Can anyone confirm this?

no, can you confirm it on rc2?
pavel

Re: Bug in LyX 1.6-RC1

[Olivier Ripoll]

Mukhtar Ullah wrote:

I don't know if it is a known bug, but LyX 1.6-RC1 crashes whenever I try to
copy a piece of text that contains ERT from one LyX document to another.

Can anyone confirm this?


Yes, indeed, it just crashed on WinXP when trying that.
Are you using windows? MacOS ? linux ?
(Un)fortunately, now, I cannot reproduce it any more... which seems to 
be the case with several 1.6 crashes.


Best regards,

Olivier



Mukhtar

Re: bug using lyx-1.5.2 export at the command line?

[Oscar Lopez]

Jürgen Spitzmüller [EMAIL PROTECTED] writes:

Does it crash on any file or only on specific files? If the latter, do these
files contain something specufic, such as a branch inset?

It crash on a simple beamer lyx file (just a frame and an item, no text with
branches, no notes, nothing particular, just a branch defined in Document
Settings and activated)

Also, running the command in gdb to produce a backtrance would help.

Here you have:
% gdb lyx
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as i486-linux-gnu...Using host libthread_db library
/lib/tls/i686/cmov/libthread_db.so.1.

(gdb) run :0 -e pdf2 test.lyx
Starting program: /usr/local/bin/lyx :0 -e pdf2 test.lyx
[Thread debugging using libthread_db enabled]
[New Thread -1220835648 (LWP 15502)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1220835648 (LWP 15502)]
0x0806f7a9 in lyx::Branch::Branch ()
(gdb) bt
#0  0x0806f7a9 in lyx::Branch::Branch ()
#1  0x0806fa77 in lyx::BranchList::add ()
#2  0x0809bbdf in lyx::BufferParams::readToken ()
#3  0x0807d741 in lyx::Buffer::readHeader ()
#4  0x0807deb5 in lyx::Buffer::readDocument ()
#5  0x0807f38c in lyx::Buffer::readFile ()
#6  0x0807fceb in lyx::Buffer::readFile ()
#7  0x0808b899 in lyx::(anonymous namespace)::readFile ()
#8  0x0808c1d1 in lyx::loadLyXFile ()
#9  0x08143079 in lyx::LyX::loadFiles ()
#10 0x08150465 in lyx::LyX::exec ()
#11 0x08067614 in main ()

I have played around a little bit and I can confirm that independently of the
document class everytime the document has a branch defined at Document Settings
(activated or not) the export from the command line fails. However File-
Export- PDF (pdflatex) it works.



Jürgen

Thanks Jurgen
Best regards
PS Sorry for the delay but yesterday gmane were down

Re: bug using lyx-1.5.2 export at the command line?

[Jürgen Spitzmüller]

Oscar Lopez wrote:
 I have played around a little bit and I can confirm that independently of
 the document class everytime the document has a branch defined at Document
 Settings (activated or not) the export from the command line fails. However
 File- Export- PDF (pdflatex) it works.

I see. This bug has been fixed in the meantime (for forthcoming 1.5.3):
http://bugzilla.lyx.org/show_bug.cgi?id=4255

Jürgen

Re: bug using lyx-1.5.2 export at the command line?

[Oscar Lopez]

Jürgen Spitzmüller [EMAIL PROTECTED] writes:

Does it crash on any file or only on specific files? If the latter, do these
files contain something specufic, such as a branch inset?

It crash on a simple beamer lyx file (just a frame and an item, no text with
branches, no notes, nothing particular, just a branch defined in Document
Settings and activated)

Also, running the command in gdb to produce a backtrance would help.

Here you have:
% gdb lyx
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as i486-linux-gnu...Using host libthread_db library
/lib/tls/i686/cmov/libthread_db.so.1.

(gdb) run :0 -e pdf2 test.lyx
Starting program: /usr/local/bin/lyx :0 -e pdf2 test.lyx
[Thread debugging using libthread_db enabled]
[New Thread -1220835648 (LWP 15502)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1220835648 (LWP 15502)]
0x0806f7a9 in lyx::Branch::Branch ()
(gdb) bt
#0  0x0806f7a9 in lyx::Branch::Branch ()
#1  0x0806fa77 in lyx::BranchList::add ()
#2  0x0809bbdf in lyx::BufferParams::readToken ()
#3  0x0807d741 in lyx::Buffer::readHeader ()
#4  0x0807deb5 in lyx::Buffer::readDocument ()
#5  0x0807f38c in lyx::Buffer::readFile ()
#6  0x0807fceb in lyx::Buffer::readFile ()
#7  0x0808b899 in lyx::(anonymous namespace)::readFile ()
#8  0x0808c1d1 in lyx::loadLyXFile ()
#9  0x08143079 in lyx::LyX::loadFiles ()
#10 0x08150465 in lyx::LyX::exec ()
#11 0x08067614 in main ()

I have played around a little bit and I can confirm that independently of the
document class everytime the document has a branch defined at Document Settings
(activated or not) the export from the command line fails. However File-
Export- PDF (pdflatex) it works.



Jürgen

Thanks Jurgen
Best regards
PS Sorry for the delay but yesterday gmane were down

Re: bug using lyx-1.5.2 export at the command line?

[Jürgen Spitzmüller]

Oscar Lopez wrote:
 I have played around a little bit and I can confirm that independently of
 the document class everytime the document has a branch defined at Document
 Settings (activated or not) the export from the command line fails. However
 File- Export- PDF (pdflatex) it works.

I see. This bug has been fixed in the meantime (for forthcoming 1.5.3):
http://bugzilla.lyx.org/show_bug.cgi?id=4255

Jürgen

Re: bug using lyx-1.5.2 export at the command line?

[Oscar Lopez]

Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:

>Does it crash on any file or only on specific files? If the latter, do these
>files contain something specufic, such as a branch inset?

It crash on a simple beamer lyx file (just a frame and an item, no text with
branches, no notes, nothing particular, just a branch defined in Document
Settings and activated)

>Also, running the command in gdb to produce a backtrance would help.

Here you have:
% gdb lyx
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library
"/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run :0 -e pdf2 test.lyx
Starting program: /usr/local/bin/lyx :0 -e pdf2 test.lyx
[Thread debugging using libthread_db enabled]
[New Thread -1220835648 (LWP 15502)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1220835648 (LWP 15502)]
0x0806f7a9 in lyx::Branch::Branch ()
(gdb) bt
#0  0x0806f7a9 in lyx::Branch::Branch ()
#1  0x0806fa77 in lyx::BranchList::add ()
#2  0x0809bbdf in lyx::BufferParams::readToken ()
#3  0x0807d741 in lyx::Buffer::readHeader ()
#4  0x0807deb5 in lyx::Buffer::readDocument ()
#5  0x0807f38c in lyx::Buffer::readFile ()
#6  0x0807fceb in lyx::Buffer::readFile ()
#7  0x0808b899 in lyx::(anonymous namespace)::readFile ()
#8  0x0808c1d1 in lyx::loadLyXFile ()
#9  0x08143079 in lyx::LyX::loadFiles ()
#10 0x08150465 in lyx::LyX::exec ()
#11 0x08067614 in main ()

I have played around a little bit and I can confirm that independently of the
document class everytime the document has a branch defined at Document Settings
(activated or not) the export from the command line fails. However File->
Export-> PDF (pdflatex) it works.


>
>Jürgen

Thanks Jurgen
Best regards
PS Sorry for the delay but yesterday gmane were down

Re: bug using lyx-1.5.2 export at the command line?

[Jürgen Spitzmüller]

Oscar Lopez wrote:
> I have played around a little bit and I can confirm that independently of
> the document class everytime the document has a branch defined at Document
> Settings (activated or not) the export from the command line fails. However
> File-> Export-> PDF (pdflatex) it works.

I see. This bug has been fixed in the meantime (for forthcoming 1.5.3):
http://bugzilla.lyx.org/show_bug.cgi?id=4255

Jürgen

Re: bug using lyx-1.5.2 export at the command line?

[Jürgen Spitzmüller]

Oscar Lopez wrote:
 Hello

 When I try to export a pdf file using the command line at my linux box the
 I get the following message
 % lyx -e pdf2 file.lyx
 lyx: SIGSEGV signal caught
 Sorry, you have found a bug in LyX. Please read the bug-reporting
 instructions in Help-Introduction and send us a bug report, if necessary.
 Thanks !

Does it crash on any file or only on specific files? If the latter, do these 
files contain something specufic, such as a branch inset?

Also, running the command in gdb to produce a backtrance would help.

Jürgen

Re: bug using lyx-1.5.2 export at the command line?

[Jürgen Spitzmüller]

Oscar Lopez wrote:
 Hello

 When I try to export a pdf file using the command line at my linux box the
 I get the following message
 % lyx -e pdf2 file.lyx
 lyx: SIGSEGV signal caught
 Sorry, you have found a bug in LyX. Please read the bug-reporting
 instructions in Help-Introduction and send us a bug report, if necessary.
 Thanks !

Does it crash on any file or only on specific files? If the latter, do these 
files contain something specufic, such as a branch inset?

Also, running the command in gdb to produce a backtrance would help.

Jürgen

Re: bug using lyx-1.5.2 export at the command line?

[Jürgen Spitzmüller]

Oscar Lopez wrote:
> Hello
>
> When I try to export a pdf file using the command line at my linux box the
> I get the following message
> % lyx -e pdf2 file.lyx
> lyx: SIGSEGV signal caught
> Sorry, you have found a bug in LyX. Please read the bug-reporting
> instructions in Help->Introduction and send us a bug report, if necessary.
> Thanks !

Does it crash on any file or only on specific files? If the latter, do these 
files contain something specufic, such as a branch inset?

Also, running the command in gdb to produce a backtrance would help.

Jürgen

bug using lyx-1.5.2 export at the command line?

[Oscar Lopez]

Hello 

When I try to export a pdf file using the command line at my linux box the I get
the following message 
% lyx -e pdf2 file.lyx
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting instructions
in Help-Introduction and send us a bug report, if necessary. Thanks !
Bye.

Does anybody experience the same problem? Is this a know bug?

If it helps I compiled the tar.gz file and 
% lyx --version
LyX 1.5.2 (Fri, Oct 5, 2007)
Built on Oct 10 2007, 18:21:05
Configuration
  Host type:i686-pc-linux-gnu
  Special build flags:  aiksaurus pch  use-aspell use-ispell
  C   Compiler: gcc
  C   Compiler LyX flags:
  C   Compiler flags: -O2
  C++ Compiler: g++ (4.0.3)
  C++ Compiler LyX flags:
  C++ Compiler flags: -O2
  Linker flags:
  Linker user flags:
  Qt 4 Frontend:
  Qt 4 version: 4.1.2
  Packaging:posix
  LyX binary dir:   /usr/local/bin
  LyX files dir:/usr/local/share/lyx



Thanks for your help
Best regards

bug using lyx-1.5.2 export at the command line?

[Oscar Lopez]

Hello 

When I try to export a pdf file using the command line at my linux box the I get
the following message 
% lyx -e pdf2 file.lyx
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting instructions
in Help-Introduction and send us a bug report, if necessary. Thanks !
Bye.

Does anybody experience the same problem? Is this a know bug?

If it helps I compiled the tar.gz file and 
% lyx --version
LyX 1.5.2 (Fri, Oct 5, 2007)
Built on Oct 10 2007, 18:21:05
Configuration
  Host type:i686-pc-linux-gnu
  Special build flags:  aiksaurus pch  use-aspell use-ispell
  C   Compiler: gcc
  C   Compiler LyX flags:
  C   Compiler flags: -O2
  C++ Compiler: g++ (4.0.3)
  C++ Compiler LyX flags:
  C++ Compiler flags: -O2
  Linker flags:
  Linker user flags:
  Qt 4 Frontend:
  Qt 4 version: 4.1.2
  Packaging:posix
  LyX binary dir:   /usr/local/bin
  LyX files dir:/usr/local/share/lyx



Thanks for your help
Best regards

bug using lyx-1.5.2 export at the command line?

[Oscar Lopez]

Hello 

When I try to export a pdf file using the command line at my linux box the I get
the following message 
% lyx -e pdf2 file.lyx
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting instructions
in Help->Introduction and send us a bug report, if necessary. Thanks !
Bye.

Does anybody experience the same problem? Is this a know bug?

If it helps I compiled the tar.gz file and 
% lyx --version
LyX 1.5.2 (Fri, Oct 5, 2007)
Built on Oct 10 2007, 18:21:05
Configuration
  Host type:i686-pc-linux-gnu
  Special build flags:  aiksaurus pch  use-aspell use-ispell
  C   Compiler: gcc
  C   Compiler LyX flags:
  C   Compiler flags: -O2
  C++ Compiler: g++ (4.0.3)
  C++ Compiler LyX flags:
  C++ Compiler flags: -O2
  Linker flags:
  Linker user flags:
  Qt 4 Frontend:
  Qt 4 version: 4.1.2
  Packaging:posix
  LyX binary dir:   /usr/local/bin
  LyX files dir:/usr/local/share/lyx



Thanks for your help
Best regards

Bug in Lyx for windows beta3

[Valter Filipe Silva]

Hello,



When a type a inline math formula followed by a comma, and, after a pass 
the cursor on it (using the right arrow key) lyx generates an fatal error.

Is this issue correct in newer versions
Best regards


Valter

--
-
PLEASE UPDATE YOUR ADDRESS BOOK WITH MY NEW E-MAIL: [EMAIL PROTECTED]


Valter Filipe Silva
[EMAIL PROTECTED]

Departamento de Electrónica, Telecomunicações e Informática
Escola Superior de Tecnologia e Gestão de Águeda
Universidade de Aveiro
3810-193 Aveiro

Re: Bug in Lyx for windows beta3

[Jürgen Spitzmüller]

Valter Filipe Silva wrote:
 When a type a inline math formula followed by a comma, and, after a pass
 the cursor on it (using the right arrow key) lyx generates an fatal error.

You mean it crashes?

 Is this issue correct in newer versions

If I understood you correctly, then I think it is fixed.

Jürgen

Re: Bug in Lyx for windows beta3

[Valter Filipe Silva]

Hello,


I install Lyx RC2 but when i try to open my document it crash ! I'm back 
to Beta3.

Best regards


VFS





Valter Filipe Silva wrote:

Hello,



When a type a inline math formula followed by a comma, and, after a 
pass the cursor on it (using the right arrow key) lyx generates an 
fatal error.

Is this issue correct in newer versions
Best regards


Valter




--
-
PLEASE UPDATE YOUR ADDRESS BOOK WITH MY NEW E-MAIL: [EMAIL PROTECTED]


Valter Filipe Silva
[EMAIL PROTECTED]

Departamento de Electrónica, Telecomunicações e Informática
Escola Superior de Tecnologia e Gestão de Águeda
Universidade de Aveiro
3810-193 Aveiro

Re: Bug in Lyx for windows beta3

[Jürgen Spitzmüller]

Valter Filipe Silva wrote:
 I install Lyx RC2 but when i try to open my document it crash !

could you produce a test case?

Jürgen

Bug in Lyx for windows beta3

[Valter Filipe Silva]

Hello,



When a type a inline math formula followed by a comma, and, after a pass 
the cursor on it (using the right arrow key) lyx generates an fatal error.

Is this issue correct in newer versions
Best regards


Valter

--
-
PLEASE UPDATE YOUR ADDRESS BOOK WITH MY NEW E-MAIL: [EMAIL PROTECTED]


Valter Filipe Silva
[EMAIL PROTECTED]

Departamento de Electrónica, Telecomunicações e Informática
Escola Superior de Tecnologia e Gestão de Águeda
Universidade de Aveiro
3810-193 Aveiro

Re: Bug in Lyx for windows beta3

[Jürgen Spitzmüller]

Valter Filipe Silva wrote:
 When a type a inline math formula followed by a comma, and, after a pass
 the cursor on it (using the right arrow key) lyx generates an fatal error.

You mean it crashes?

 Is this issue correct in newer versions

If I understood you correctly, then I think it is fixed.

Jürgen

Re: Bug in Lyx for windows beta3

[Valter Filipe Silva]

Hello,


I install Lyx RC2 but when i try to open my document it crash ! I'm back 
to Beta3.

Best regards


VFS





Valter Filipe Silva wrote:

Hello,



When a type a inline math formula followed by a comma, and, after a 
pass the cursor on it (using the right arrow key) lyx generates an 
fatal error.

Is this issue correct in newer versions
Best regards


Valter




--
-
PLEASE UPDATE YOUR ADDRESS BOOK WITH MY NEW E-MAIL: [EMAIL PROTECTED]


Valter Filipe Silva
[EMAIL PROTECTED]

Departamento de Electrónica, Telecomunicações e Informática
Escola Superior de Tecnologia e Gestão de Águeda
Universidade de Aveiro
3810-193 Aveiro

Re: Bug in Lyx for windows beta3

[Jürgen Spitzmüller]

Valter Filipe Silva wrote:
 I install Lyx RC2 but when i try to open my document it crash !

could you produce a test case?

Jürgen

Bug in Lyx for windows beta3

[Valter Filipe Silva]

Hello,



When a type a inline math formula followed by a comma, and, after a pass 
the cursor on it (using the right arrow key) lyx generates an fatal error.

Is this issue correct in newer versions
Best regards


Valter

--
-
PLEASE UPDATE YOUR ADDRESS BOOK WITH MY NEW E-MAIL: [EMAIL PROTECTED]


Valter Filipe Silva
[EMAIL PROTECTED]

Departamento de Electrónica, Telecomunicações e Informática
Escola Superior de Tecnologia e Gestão de Águeda
Universidade de Aveiro
3810-193 Aveiro