On Tue, Apr 15, 2008 at 07:46:39PM +0200, Abdelrazak Younes wrote:

> Enrico Forestieri wrote:
> > On Tue, Apr 15, 2008 at 06:58:55PM +0200, Abdelrazak Younes wrote:
> > 
> >> By the way, wasn't there a bug related to Qt4.4? Current svn seems to 
> >> work fine. Or was it for 1.5?
> > 
> > LyX 1.5 crashes on startup,
> 
> Do you have a backtrace to see if I can help? I'd be difficult for me to 
> compile branch right now.

I am not able to get a meaningful backtrace:

QPaintEngine::setSystemClip: Should not be changed while engine is active
QPaintEngine::setSystemClip: Should not be changed while engine is active
QWidgetPrivate::beginSharedPainter: Painter is already active

---Type <return> to continue, or q <return> to quit---
Program received signal SIGSEGV, Segmentation fault.
0x00ae7f09 in ?? ()
(gdb) bt
#0  0x00ae7f09 in ?? ()
#1  0x009c037d in ?? ()
#2  0x0255b938 in ?? ()
#3  0x0000003e in ?? ()
#4  0x00000001 in ?? ()
#5  0x00227900 in ?? ()
#6  0x00000000 in ?? ()
(gdb) 

> > LyX 1.6 was crashing on exit, but maybe
> > this was just fixed by André.
> 
> Hopefully.

The crash on exit seems to be gone, but I get this on "New document":

QPaintEngine::setSystemClip: Should not be changed while engine is active
QPaintEngine::setSystemClip: Should not be changed while engine is active
QWidgetPrivate::beginSharedPainter: Painter is already active
QWidget::repaint: Recursive repaint detected
QWidgetPrivate::endSharedPainter: Attempting to end a null painter

And it even crashed when I loaded an existing document:

QPaintEngine::setSystemClip: Should not be changed while engine is active
QPaintEngine::setSystemClip: Should not be changed while engine is active
QWidgetPrivate::beginSharedPainter: Painter is already active
QWidget::repaint: Recursive repaint detected

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.
Abort (core dumped)

I was not able to reproduce it under gdb, though.

-- 
Enrico

Reply via email to