Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Todd Denniston 
Pavel Sanda wrote, On 01/-10/-28163 02:59 PM:
 Todd Denniston wrote:
 So is this affecting current lyx 1.6.x on other distros?
 
 not on gentoo. what qt version do you have installed?
 pavel
 

Just so I am sure,
when you open/fire up lyx for steps 5-10, the outline pane is already open?
to reproduce for me, outline *had* to be open already and I had to select 
*back* to the first tab.

rpm -qa qt\*
qt-3.3.6-23.el5
qt-devel-3.3.6-23.el5
qt4-4.2.1-1

and ldd indicates lyx is using qt4
ldd /usr/bin/lyx |grep -i qt
libQtGui.so.4 = /usr/lib/qt4/lib/libQtGui.so.4 (0x0588b000)
libQtCore.so.4 = /usr/lib/qt4/lib/libQtCore.so.4 (0x00373000)

Unfortunately the lyx debug package was not put in EPEL so the bt may be less 
than desired.

gdb lyx
set args -dbg 8  lyxcrash2.txt 21
run


Thanks for the time you have spent looking at this, you and the other reports 
are beginning to sound
like it may be a `CentOS/RHEL 5 has something too old`, which is possible. I am 
just glad lyx 1.6
runs at all on it.
-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
Starting program: /usr/bin/lyx -dbg 8  lyxcrash2.txt 21
[Thread debugging using libthread_db enabled]
[New Thread 0xb7c86b90 (LWP 25250)]
Detaching after fork from child process 25251.

Program received signal SIGSEGV, Segmentation fault.
0x082da6d5 in lyx::Toc::item(lyx::DocIterator const) const ()
(gdb) bt
#0  0x082da6d5 in lyx::Toc::item(lyx::DocIterator const) const ()
#1  0x08551708 in lyx::frontend::TocModel::modelIndex(lyx::DocIterator const) 
const ()
#2  0x085519fb in lyx::frontend::TocModels::currentIndex(QString const) const
()
#3  0x086c54e7 in lyx::frontend::TocWidget::updateView() ()
#4  0x0850fcd2 in lyx::frontend::GuiView::updateDialogs() ()
#5  0x0850fe43 in lyx::frontend::GuiView::restartCursor() ()
#6  0x0823ccb9 in lyx::LyXFunc::dispatch(lyx::FuncRequest const) ()
#7  0x08221456 in lyx::dispatch(lyx::FuncRequest const) ()
#8  0x0855bc75 in lyx::frontend::Action::action() ()
#9  0x0855bd02 in lyx::frontend::Action::qt_metacall(QMetaObject::Call, int, 
void**) ()
#10 0x00464100 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/qt4/lib/libQtCore.so.4
#11 0x0046435f in QMetaObject::activate(QObject*, QMetaObject const*, int, int, 
void**) () from /usr/lib/qt4/lib/libQtCore.so.4
#12 0x0598b171 in QAction::triggered(bool) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#13 0x0598be2f in QAction::activate(QAction::ActionEvent) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#14 0x05c89464 in ?? () from /usr/lib/qt4/lib/libQtGui.so.4
#15 0x05c8bc26 in QMenu::mouseReleaseEvent(QMouseEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#16 0x059daae1 in QWidget::event(QEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#17 0x05c866fc in QMenu::event(QEvent*) () from /usr/lib/qt4/lib/libQtGui.so.4
#18 0x05991810 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#19 0x05994293 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#20 0x084ed2db in lyx::frontend::GuiApplication::notify(QObject*, QEvent*) ()
#21 0x059ed7c8 in ?? () from /usr/lib/qt4/lib/libQtGui.so.4
#22 0x059ec3df in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#23 0x05a0f275 in ?? () from /usr/lib/qt4/lib/libQtGui.so.4
#24 0x00451ef1 in 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib/qt4/lib/libQtCore.so.4
#25 0x00451ffa in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) ()
   from /usr/lib/qt4/lib/libQtCore.so.4
#26 0x0045459d in QCoreApplication::exec() ()
   from /usr/lib/qt4/lib/libQtCore.so.4
#27 0x05991287 in QApplication::exec() () from /usr/lib/qt4/lib/libQtGui.so.4
#28 0x0822d5be in lyx::LyX::exec(int, char**) ()
#29 0x081558f9 in main ()

Setting debug level to 8
Debugging `gui' (GUI handling)
GuiApplication.cpp(993): About to create new window with ID 0
GuiView.cpp(120): show banner: 1
Menus.cpp(1603): populating menu bar
Menus.cpp(1610): menu bar entries 8
Menus.cpp(1629): menu bar item File is a submenu named file
Menus.cpp(1629): menu bar item Edit is a submenu named edit
Menus.cpp(1629): menu bar item View is a submenu named view
Menus.cpp(1629): menu bar item Insert is a submenu named insert
Menus.cpp(1629): menu bar item Navigate is a submenu named navigate
Menus.cpp(1629): menu bar item Document is a submenu named document
Menus.cpp(1629): menu bar item Tools is a submenu named tools
Menus.cpp(1629): menu bar item Help is a submenu named help
GuiView.cpp(519): Passed Geometry 933x1180+512+-153
Menus.cpp(1649): Triggered menu: file
Menus.cpp(1194): populating menu 
Menus.cpp(1199):  *  menu entries 21
Menus.cpp(1194): populating menu file_lastfiles
Menus.cpp(1199):  *  menu entries 20
Menus.cpp(1194): populating menu file_vc
Menus.cpp(1196):ERROR: empty menu file_vc
Menus.cpp(1194): populating menu

Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Pavel Sanda 
Todd Denniston wrote:
 when you open/fire up lyx for steps 5-10, the outline pane is already open?

yes.

 to reproduce for me, outline *had* to be open already and I had to select 
 *back* to the first tab.
 
 qt4-4.2.1-1

 gdb lyx
 set args -dbg 8  lyxcrash2.txt 21
 run

the backtrace somewhat confirm my suspictions was that its outliner, which kill 
the whole thing down.
we made changes in 1.6.6.1 so it does not crash with qt 4.6, but it may
be possible that it was damaging for 4.2.1...
if my guess is true, then 1.6.5 should work (i would happy to know this, so we 
can warn users to upgrade
for newer Qt...)

 Thanks for the time you have spent looking at this, you and the other reports 
 are beginning to sound
 like it may be a `CentOS/RHEL 5 has something too old`, which is possible. I 
 am just glad lyx 1.6
 runs at all on it.

workaround is not to use outliner when switching buffers... ;)

pavel

Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Todd Denniston 
Pavel Sanda wrote, On Fri, 03 Sep 2010 09:01:37 -0700:
 
 if my guess is true, then 1.6.5 should work (i would happy to know this, so we
 can warn users to upgrade for newer Qt...)

Grab copy of EPEL way back...that I had almost removed
yum remove lyx
yum install lyx-1.6.5-5.el5
lyx #setup outline
lyx # test {no breakage}
lyx # test {get breakage}
gdb lyx
set args -dbg 8  lyxcrash2.txt 21
run
Starting program: /usr/bin/lyx -dbg 8  lyxcrash2.txt 21
[Thread debugging using libthread_db enabled]
warning: .dynamic section for /usr/lib/libmng.so.1 is not at the expected 
address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for /usr/lib/liblcms.so.1 is not at the expected 
address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for /usr/lib/qt4/lib/libQtXml.so.4 is not at the 
expected address
warning: difference appears to be caused by prelink, adjusting expectations
[New Thread 0xb7c81b90 (LWP 24928)]
Detaching after fork from child process 24929.

Program received signal SIGSEGV, Segmentation fault.
0x082d5ad5 in lyx::Toc::item(lyx::DocIterator const) const ()
(gdb) bt

[The BT is the same except the addresses changed. i.e.
#0  0x082d5ad5 #1  0x085457a8 #2  0x08545e1b ... #10 0x00c3c100 ... #29 
0x081548d9]
[lyxcrash2.txt is the same except I get newfile1  newfile2 instead of newfile2 
 newfile3, i.e.
under a different and new account]

BTW1 I tried with `rm ~/.lyx/ -fr` `yum install lyx-1.6.3-1.el5` and got the 
same fault.
BTW2 the deltas that Rex lists between 1.6.5 and 1.6.5-5 I doubt affect this:
* Sun Feb 14 2010 Rex Dieter rdie...@fedoraproject.org - 1.6.5-5
- FTBFS lyx-1.6.5-4.fc13: ImplicitDSOLinking (#565009)

* Thu Jan 21 2010 Rex Dieter rdie...@fedoraproject.org - 1.6.5-4
- -fonts: Provides: lyx-{cmex10,cmmi10,cmr10,cmsy10}-fonts

* Sat Jan 16 2010 Rex Dieter rdie...@fedoraproject.org - 1.6.5-3
- rebiuld (boost)
- use simple font template

* Wed Dec 09 2009 José Matos jama...@fc.up.pt - 1.6.5-2
- Add patch for autoconf 2.65 (F13+)

* Wed Dec 09 2009 José Matos jama...@fc.up.pt - 1.6.5-1
- lyx-1.6.5



 workaround is not to use outliner when switching buffers... ;)

Workaround is to not use outliner, and switch buffers, and then close one. ;)
I just happened to hit this yesterday because I happened to want (for the first 
time :) to close
JUST one buffer instead of the whole program.  Of course I ended up getting 
whole program shutdown. :)
I can generally live with that workaround, especially as it seems to affect not 
very many folks.

Thanks again.

-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Pavel Sanda 
Todd Denniston wrote:
 Program received signal SIGSEGV, Segmentation fault.
 0x082d5ad5 in lyx::Toc::item(lyx::DocIterator const) const ()
 (gdb) bt


ok i was wrong. another possibility would be to update qt's...

pavel

Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Todd Denniston 
Pavel Sanda wrote, On 01/-10/-28163 02:59 PM:
 Todd Denniston wrote:
 So is this affecting current lyx 1.6.x on other distros?
 
 not on gentoo. what qt version do you have installed?
 pavel
 

Just so I am sure,
when you open/fire up lyx for steps 5-10, the outline pane is already open?
to reproduce for me, outline *had* to be open already and I had to select 
*back* to the first tab.

rpm -qa qt\*
qt-3.3.6-23.el5
qt-devel-3.3.6-23.el5
qt4-4.2.1-1

and ldd indicates lyx is using qt4
ldd /usr/bin/lyx |grep -i qt
libQtGui.so.4 = /usr/lib/qt4/lib/libQtGui.so.4 (0x0588b000)
libQtCore.so.4 = /usr/lib/qt4/lib/libQtCore.so.4 (0x00373000)

Unfortunately the lyx debug package was not put in EPEL so the bt may be less 
than desired.

gdb lyx
set args -dbg 8  lyxcrash2.txt 21
run


Thanks for the time you have spent looking at this, you and the other reports 
are beginning to sound
like it may be a `CentOS/RHEL 5 has something too old`, which is possible. I am 
just glad lyx 1.6
runs at all on it.
-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
Starting program: /usr/bin/lyx -dbg 8  lyxcrash2.txt 21
[Thread debugging using libthread_db enabled]
[New Thread 0xb7c86b90 (LWP 25250)]
Detaching after fork from child process 25251.

Program received signal SIGSEGV, Segmentation fault.
0x082da6d5 in lyx::Toc::item(lyx::DocIterator const) const ()
(gdb) bt
#0  0x082da6d5 in lyx::Toc::item(lyx::DocIterator const) const ()
#1  0x08551708 in lyx::frontend::TocModel::modelIndex(lyx::DocIterator const) 
const ()
#2  0x085519fb in lyx::frontend::TocModels::currentIndex(QString const) const
()
#3  0x086c54e7 in lyx::frontend::TocWidget::updateView() ()
#4  0x0850fcd2 in lyx::frontend::GuiView::updateDialogs() ()
#5  0x0850fe43 in lyx::frontend::GuiView::restartCursor() ()
#6  0x0823ccb9 in lyx::LyXFunc::dispatch(lyx::FuncRequest const) ()
#7  0x08221456 in lyx::dispatch(lyx::FuncRequest const) ()
#8  0x0855bc75 in lyx::frontend::Action::action() ()
#9  0x0855bd02 in lyx::frontend::Action::qt_metacall(QMetaObject::Call, int, 
void**) ()
#10 0x00464100 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/qt4/lib/libQtCore.so.4
#11 0x0046435f in QMetaObject::activate(QObject*, QMetaObject const*, int, int, 
void**) () from /usr/lib/qt4/lib/libQtCore.so.4
#12 0x0598b171 in QAction::triggered(bool) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#13 0x0598be2f in QAction::activate(QAction::ActionEvent) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#14 0x05c89464 in ?? () from /usr/lib/qt4/lib/libQtGui.so.4
#15 0x05c8bc26 in QMenu::mouseReleaseEvent(QMouseEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#16 0x059daae1 in QWidget::event(QEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#17 0x05c866fc in QMenu::event(QEvent*) () from /usr/lib/qt4/lib/libQtGui.so.4
#18 0x05991810 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#19 0x05994293 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#20 0x084ed2db in lyx::frontend::GuiApplication::notify(QObject*, QEvent*) ()
#21 0x059ed7c8 in ?? () from /usr/lib/qt4/lib/libQtGui.so.4
#22 0x059ec3df in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#23 0x05a0f275 in ?? () from /usr/lib/qt4/lib/libQtGui.so.4
#24 0x00451ef1 in 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib/qt4/lib/libQtCore.so.4
#25 0x00451ffa in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) ()
   from /usr/lib/qt4/lib/libQtCore.so.4
#26 0x0045459d in QCoreApplication::exec() ()
   from /usr/lib/qt4/lib/libQtCore.so.4
#27 0x05991287 in QApplication::exec() () from /usr/lib/qt4/lib/libQtGui.so.4
#28 0x0822d5be in lyx::LyX::exec(int, char**) ()
#29 0x081558f9 in main ()

Setting debug level to 8
Debugging `gui' (GUI handling)
GuiApplication.cpp(993): About to create new window with ID 0
GuiView.cpp(120): show banner: 1
Menus.cpp(1603): populating menu bar
Menus.cpp(1610): menu bar entries 8
Menus.cpp(1629): menu bar item File is a submenu named file
Menus.cpp(1629): menu bar item Edit is a submenu named edit
Menus.cpp(1629): menu bar item View is a submenu named view
Menus.cpp(1629): menu bar item Insert is a submenu named insert
Menus.cpp(1629): menu bar item Navigate is a submenu named navigate
Menus.cpp(1629): menu bar item Document is a submenu named document
Menus.cpp(1629): menu bar item Tools is a submenu named tools
Menus.cpp(1629): menu bar item Help is a submenu named help
GuiView.cpp(519): Passed Geometry 933x1180+512+-153
Menus.cpp(1649): Triggered menu: file
Menus.cpp(1194): populating menu 
Menus.cpp(1199):  *  menu entries 21
Menus.cpp(1194): populating menu file_lastfiles
Menus.cpp(1199):  *  menu entries 20
Menus.cpp(1194): populating menu file_vc
Menus.cpp(1196):ERROR: empty menu file_vc
Menus.cpp(1194): populating menu

Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Pavel Sanda 
Todd Denniston wrote:
 when you open/fire up lyx for steps 5-10, the outline pane is already open?

yes.

 to reproduce for me, outline *had* to be open already and I had to select 
 *back* to the first tab.
 
 qt4-4.2.1-1

 gdb lyx
 set args -dbg 8  lyxcrash2.txt 21
 run

the backtrace somewhat confirm my suspictions was that its outliner, which kill 
the whole thing down.
we made changes in 1.6.6.1 so it does not crash with qt 4.6, but it may
be possible that it was damaging for 4.2.1...
if my guess is true, then 1.6.5 should work (i would happy to know this, so we 
can warn users to upgrade
for newer Qt...)

 Thanks for the time you have spent looking at this, you and the other reports 
 are beginning to sound
 like it may be a `CentOS/RHEL 5 has something too old`, which is possible. I 
 am just glad lyx 1.6
 runs at all on it.

workaround is not to use outliner when switching buffers... ;)

pavel

Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Todd Denniston 
Pavel Sanda wrote, On Fri, 03 Sep 2010 09:01:37 -0700:
 
 if my guess is true, then 1.6.5 should work (i would happy to know this, so we
 can warn users to upgrade for newer Qt...)

Grab copy of EPEL way back...that I had almost removed
yum remove lyx
yum install lyx-1.6.5-5.el5
lyx #setup outline
lyx # test {no breakage}
lyx # test {get breakage}
gdb lyx
set args -dbg 8  lyxcrash2.txt 21
run
Starting program: /usr/bin/lyx -dbg 8  lyxcrash2.txt 21
[Thread debugging using libthread_db enabled]
warning: .dynamic section for /usr/lib/libmng.so.1 is not at the expected 
address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for /usr/lib/liblcms.so.1 is not at the expected 
address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for /usr/lib/qt4/lib/libQtXml.so.4 is not at the 
expected address
warning: difference appears to be caused by prelink, adjusting expectations
[New Thread 0xb7c81b90 (LWP 24928)]
Detaching after fork from child process 24929.

Program received signal SIGSEGV, Segmentation fault.
0x082d5ad5 in lyx::Toc::item(lyx::DocIterator const) const ()
(gdb) bt

[The BT is the same except the addresses changed. i.e.
#0  0x082d5ad5 #1  0x085457a8 #2  0x08545e1b ... #10 0x00c3c100 ... #29 
0x081548d9]
[lyxcrash2.txt is the same except I get newfile1  newfile2 instead of newfile2 
 newfile3, i.e.
under a different and new account]

BTW1 I tried with `rm ~/.lyx/ -fr` `yum install lyx-1.6.3-1.el5` and got the 
same fault.
BTW2 the deltas that Rex lists between 1.6.5 and 1.6.5-5 I doubt affect this:
* Sun Feb 14 2010 Rex Dieter rdie...@fedoraproject.org - 1.6.5-5
- FTBFS lyx-1.6.5-4.fc13: ImplicitDSOLinking (#565009)

* Thu Jan 21 2010 Rex Dieter rdie...@fedoraproject.org - 1.6.5-4
- -fonts: Provides: lyx-{cmex10,cmmi10,cmr10,cmsy10}-fonts

* Sat Jan 16 2010 Rex Dieter rdie...@fedoraproject.org - 1.6.5-3
- rebiuld (boost)
- use simple font template

* Wed Dec 09 2009 José Matos jama...@fc.up.pt - 1.6.5-2
- Add patch for autoconf 2.65 (F13+)

* Wed Dec 09 2009 José Matos jama...@fc.up.pt - 1.6.5-1
- lyx-1.6.5



 workaround is not to use outliner when switching buffers... ;)

Workaround is to not use outliner, and switch buffers, and then close one. ;)
I just happened to hit this yesterday because I happened to want (for the first 
time :) to close
JUST one buffer instead of the whole program.  Of course I ended up getting 
whole program shutdown. :)
I can generally live with that workaround, especially as it seems to affect not 
very many folks.

Thanks again.

-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Pavel Sanda 
Todd Denniston wrote:
 Program received signal SIGSEGV, Segmentation fault.
 0x082d5ad5 in lyx::Toc::item(lyx::DocIterator const) const ()
 (gdb) bt


ok i was wrong. another possibility would be to update qt's...

pavel

Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Todd Denniston 
Pavel Sanda wrote, On 01/-10/-28163 02:59 PM:
> Todd Denniston wrote:
>> So is this affecting current lyx 1.6.x on other distros?
> 
> not on gentoo. what qt version do you have installed?
> pavel
> 

Just so I am sure,
when you open/fire up lyx for steps 5-10, the outline pane is already open?
to reproduce for me, outline *had* to be open already and I had to select 
*back* to the first tab.

rpm -qa qt\*
qt-3.3.6-23.el5
qt-devel-3.3.6-23.el5
qt4-4.2.1-1

and ldd indicates lyx is using qt4
ldd /usr/bin/lyx |grep -i qt
libQtGui.so.4 => /usr/lib/qt4/lib/libQtGui.so.4 (0x0588b000)
libQtCore.so.4 => /usr/lib/qt4/lib/libQtCore.so.4 (0x00373000)

Unfortunately the lyx debug package was not put in EPEL so the bt may be less 
than desired.

gdb lyx
set args -dbg 8 > lyxcrash2.txt 2>&1
run


Thanks for the time you have spent looking at this, you and the other reports 
are beginning to sound
like it may be a `CentOS/RHEL 5 has something too old`, which is possible. I am 
just glad lyx 1.6
runs at all on it.
-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
Starting program: /usr/bin/lyx -dbg 8 > lyxcrash2.txt 2>&1
[Thread debugging using libthread_db enabled]
[New Thread 0xb7c86b90 (LWP 25250)]
Detaching after fork from child process 25251.

Program received signal SIGSEGV, Segmentation fault.
0x082da6d5 in lyx::Toc::item(lyx::DocIterator const&) const ()
(gdb) bt
#0  0x082da6d5 in lyx::Toc::item(lyx::DocIterator const&) const ()
#1  0x08551708 in lyx::frontend::TocModel::modelIndex(lyx::DocIterator const&) 
const ()
#2  0x085519fb in lyx::frontend::TocModels::currentIndex(QString const&) const
()
#3  0x086c54e7 in lyx::frontend::TocWidget::updateView() ()
#4  0x0850fcd2 in lyx::frontend::GuiView::updateDialogs() ()
#5  0x0850fe43 in lyx::frontend::GuiView::restartCursor() ()
#6  0x0823ccb9 in lyx::LyXFunc::dispatch(lyx::FuncRequest const&) ()
#7  0x08221456 in lyx::dispatch(lyx::FuncRequest const&) ()
#8  0x0855bc75 in lyx::frontend::Action::action() ()
#9  0x0855bd02 in lyx::frontend::Action::qt_metacall(QMetaObject::Call, int, 
void**) ()
#10 0x00464100 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/qt4/lib/libQtCore.so.4
#11 0x0046435f in QMetaObject::activate(QObject*, QMetaObject const*, int, int, 
void**) () from /usr/lib/qt4/lib/libQtCore.so.4
#12 0x0598b171 in QAction::triggered(bool) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#13 0x0598be2f in QAction::activate(QAction::ActionEvent) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#14 0x05c89464 in ?? () from /usr/lib/qt4/lib/libQtGui.so.4
#15 0x05c8bc26 in QMenu::mouseReleaseEvent(QMouseEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#16 0x059daae1 in QWidget::event(QEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#17 0x05c866fc in QMenu::event(QEvent*) () from /usr/lib/qt4/lib/libQtGui.so.4
#18 0x05991810 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#19 0x05994293 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#20 0x084ed2db in lyx::frontend::GuiApplication::notify(QObject*, QEvent*) ()
#21 0x059ed7c8 in ?? () from /usr/lib/qt4/lib/libQtGui.so.4
#22 0x059ec3df in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/qt4/lib/libQtGui.so.4
#23 0x05a0f275 in ?? () from /usr/lib/qt4/lib/libQtGui.so.4
#24 0x00451ef1 in 
QEventLoop::processEvents(QFlags) () from 
/usr/lib/qt4/lib/libQtCore.so.4
#25 0x00451ffa in QEventLoop::exec(QFlags) ()
   from /usr/lib/qt4/lib/libQtCore.so.4
#26 0x0045459d in QCoreApplication::exec() ()
   from /usr/lib/qt4/lib/libQtCore.so.4
#27 0x05991287 in QApplication::exec() () from /usr/lib/qt4/lib/libQtGui.so.4
#28 0x0822d5be in lyx::LyX::exec(int&, char**) ()
#29 0x081558f9 in main ()

Setting debug level to 8
Debugging `gui' (GUI handling)
GuiApplication.cpp(993): About to create new window with ID 0
GuiView.cpp(120): show banner: 1
Menus.cpp(1603): populating menu bar
Menus.cpp(1610): menu bar entries 8
Menus.cpp(1629): menu bar item File is a submenu named file
Menus.cpp(1629): menu bar item Edit is a submenu named edit
Menus.cpp(1629): menu bar item View is a submenu named view
Menus.cpp(1629): menu bar item Insert is a submenu named insert
Menus.cpp(1629): menu bar item Navigate is a submenu named navigate
Menus.cpp(1629): menu bar item Document is a submenu named document
Menus.cpp(1629): menu bar item Tools is a submenu named tools
Menus.cpp(1629): menu bar item Help is a submenu named help
GuiView.cpp(519): Passed Geometry 933x1180+512+-153
Menus.cpp(1649): Triggered menu: file
Menus.cpp(1194): populating menu 
Menus.cpp(1199):  *  menu entries 21
Menus.cpp(1194): populating menu file_lastfiles
Menus.cpp(1199):  *  menu entries 20
Menus.cpp(1194): populating menu file_vc
Menus.cpp(1196):ERROR: empty menu file_vc
Menus.cpp(1194): populating menu file_import
Menus.cpp(1199):  *  menu

Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Pavel Sanda 
Todd Denniston wrote:
> when you open/fire up lyx for steps 5-10, the outline pane is already open?

yes.

> to reproduce for me, outline *had* to be open already and I had to select 
> *back* to the first tab.
> 
> qt4-4.2.1-1

> gdb lyx
> set args -dbg 8 > lyxcrash2.txt 2>&1
> run

the backtrace somewhat confirm my suspictions was that its outliner, which kill 
the whole thing down.
we made changes in 1.6.6.1 so it does not crash with qt 4.6, but it may
be possible that it was damaging for 4.2.1...
if my guess is true, then 1.6.5 should work (i would happy to know this, so we 
can warn users to upgrade
for newer Qt...)

> Thanks for the time you have spent looking at this, you and the other reports 
> are beginning to sound
> like it may be a `CentOS/RHEL 5 has something too old`, which is possible. I 
> am just glad lyx 1.6
> runs at all on it.

workaround is not to use outliner when switching buffers... ;)

pavel

Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Todd Denniston 
Pavel Sanda wrote, On Fri, 03 Sep 2010 09:01:37 -0700:
> 
> if my guess is true, then 1.6.5 should work (i would happy to know this, so we
> can warn users to upgrade for newer Qt...)


yum remove lyx
yum install lyx-1.6.5-5.el5
lyx #setup outline
lyx # test {no breakage}
lyx # test {get breakage}
gdb lyx
set args -dbg 8 > lyxcrash2.txt 2>&1
run
Starting program: /usr/bin/lyx -dbg 8 > lyxcrash2.txt 2>&1
[Thread debugging using libthread_db enabled]
warning: .dynamic section for "/usr/lib/libmng.so.1" is not at the expected 
address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/liblcms.so.1" is not at the expected 
address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/qt4/lib/libQtXml.so.4" is not at the 
expected address
warning: difference appears to be caused by prelink, adjusting expectations
[New Thread 0xb7c81b90 (LWP 24928)]
Detaching after fork from child process 24929.

Program received signal SIGSEGV, Segmentation fault.
0x082d5ad5 in lyx::Toc::item(lyx::DocIterator const&) const ()
(gdb) bt

[The BT is the same except the addresses changed. i.e.
#0  0x082d5ad5 #1  0x085457a8 #2  0x08545e1b ... #10 0x00c3c100 ... #29 
0x081548d9]
[lyxcrash2.txt is the same except I get newfile1 & newfile2 instead of newfile2 
& newfile3, i.e.
under a different and new account]

BTW1 I tried with `rm ~/.lyx/ -fr` `yum install lyx-1.6.3-1.el5` and got the 
same fault.
BTW2 the deltas that Rex lists between 1.6.5 and 1.6.5-5 I doubt affect this:
* Sun Feb 14 2010 Rex Dieter  - 1.6.5-5
- FTBFS lyx-1.6.5-4.fc13: ImplicitDSOLinking (#565009)

* Thu Jan 21 2010 Rex Dieter  - 1.6.5-4
- -fonts: Provides: lyx-{cmex10,cmmi10,cmr10,cmsy10}-fonts

* Sat Jan 16 2010 Rex Dieter  - 1.6.5-3
- rebiuld (boost)
- use simple font template

* Wed Dec 09 2009 José Matos  - 1.6.5-2
- Add patch for autoconf 2.65 (F13+)

* Wed Dec 09 2009 José Matos  - 1.6.5-1
- lyx-1.6.5



> workaround is not to use outliner when switching buffers... ;)

Workaround is to not use outliner, and switch buffers, and then close one. ;)
I just happened to hit this yesterday because I happened to want (for the first 
time :) to close
JUST one buffer instead of the whole program.  Of course I ended up getting 
whole program shutdown. :)
I can generally live with that workaround, especially as it seems to affect not 
very many folks.

Thanks again.

-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

Re: Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-03 Thread Pavel Sanda 
Todd Denniston wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x082d5ad5 in lyx::Toc::item(lyx::DocIterator const&) const ()
> (gdb) bt


ok i was wrong. another possibility would be to update qt's...

pavel

Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-02 Thread James C. Sutherland 
FWIW, I cannot duplicate this on Mac running LyX 1.6.7.
Also, step 6 creates newfile1 for me, not newfile2
James


On Thu, Sep 2, 2010 at 11:01 AM, Todd Denniston 
todd.dennis...@tsb.cranrdte.navy.mil wrote:

 OS: Centos 5.5 up to date (equivalent to RHEL 5.5)
 LyX: lyx 1.6.7 (lyx-1.6.7-1.el5 from the EPEL repository)
 Also affected lyx 1.6.6.1 from the EPEL repository

 simple method to cause crash:
 1) fire up lyx
 2) open a file
 3) turn Outline mode on (get the check beside Document - Outline), if it
 is not already on
 4) exit lyx
 5) fire up lyx
 6) File - New (creates newfile2 tab)
 7) File - New (creates newfile3 tab)
 8) select the tab for the first new file (newfile2)
 9) File - Close
 10) see
 -Begin message
 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.
 Aborted
 -End message

 So is this affecting current lyx 1.6.x on other distros?

 bugzilla's hate me right now, not their fault though, so I am sending to
 the list. :]
 --
 Todd Denniston
 Crane Division, Naval Surface Warfare Center (NSWC Crane)
 Harnessing the Power of Technology for the Warfighter

Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-02 Thread Paul Rubin 
Failed to reproduce on Mint Isadora (essentially Ubuntu 10.04).

/Paul

Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-02 Thread Pavel Sanda 
Todd Denniston wrote:
 So is this affecting current lyx 1.6.x on other distros?

not on gentoo. what qt version do you have installed?
pavel

Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-02 Thread James C. Sutherland 
FWIW, I cannot duplicate this on Mac running LyX 1.6.7.
Also, step 6 creates newfile1 for me, not newfile2
James


On Thu, Sep 2, 2010 at 11:01 AM, Todd Denniston 
todd.dennis...@tsb.cranrdte.navy.mil wrote:

 OS: Centos 5.5 up to date (equivalent to RHEL 5.5)
 LyX: lyx 1.6.7 (lyx-1.6.7-1.el5 from the EPEL repository)
 Also affected lyx 1.6.6.1 from the EPEL repository

 simple method to cause crash:
 1) fire up lyx
 2) open a file
 3) turn Outline mode on (get the check beside Document - Outline), if it
 is not already on
 4) exit lyx
 5) fire up lyx
 6) File - New (creates newfile2 tab)
 7) File - New (creates newfile3 tab)
 8) select the tab for the first new file (newfile2)
 9) File - Close
 10) see
 -Begin message
 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.
 Aborted
 -End message

 So is this affecting current lyx 1.6.x on other distros?

 bugzilla's hate me right now, not their fault though, so I am sending to
 the list. :]
 --
 Todd Denniston
 Crane Division, Naval Surface Warfare Center (NSWC Crane)
 Harnessing the Power of Technology for the Warfighter

Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-02 Thread Paul Rubin 
Failed to reproduce on Mint Isadora (essentially Ubuntu 10.04).

/Paul

Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-02 Thread Pavel Sanda 
Todd Denniston wrote:
 So is this affecting current lyx 1.6.x on other distros?

not on gentoo. what qt version do you have installed?
pavel

Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-02 Thread James C. Sutherland 
FWIW, I cannot duplicate this on Mac running LyX 1.6.7.
Also, step 6 creates "newfile1" for me, not "newfile2"
James


On Thu, Sep 2, 2010 at 11:01 AM, Todd Denniston <
todd.dennis...@tsb.cranrdte.navy.mil> wrote:

> OS: Centos 5.5 up to date (equivalent to RHEL 5.5)
> LyX: lyx 1.6.7 (lyx-1.6.7-1.el5 from the EPEL repository)
> Also affected lyx 1.6.6.1 from the EPEL repository
>
> simple method to cause crash:
> 1) fire up lyx
> 2) open a file
> 3) turn Outline mode on (get the check beside Document -> Outline), if it
> is not already on
> 4) exit lyx
> 5) fire up lyx
> 6) File -> New (creates newfile2 tab)
> 7) File -> New (creates newfile3 tab)
> 8) select the tab for the first new file (newfile2)
> 9) File -> Close
> 10) see
> -Begin message
> 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.
> Aborted
> -End message
>
> So is this affecting current lyx 1.6.x on other distros?
>
> bugzilla's hate me right now, not their fault though, so I am sending to
> the list. :]
> --
> Todd Denniston
> Crane Division, Naval Surface Warfare Center (NSWC Crane)
> Harnessing the Power of Technology for the Warfighter
>

Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-02 Thread Paul Rubin 
Failed to reproduce on Mint Isadora (essentially Ubuntu 10.04).

/Paul

Re: opening two tabs with outline on and closing one, crashes lyx.

2010-09-02 Thread Pavel Sanda 
Todd Denniston wrote:
> So is this affecting current lyx 1.6.x on other distros?

not on gentoo. what qt version do you have installed?
pavel