Re: lyx 1.3.2cvs qt backtrace of crash when closing external inset.

2003-03-21 Thread Jean-Marc Lasgouttes
> "John" == John Levon <[EMAIL PROTECTED]> writes: John> On Fri, Mar 21, 2003 at 03:27:05PM +0100, Jean-Marc Lasgouttes John> wrote: Do people really use the externall dialog much ? >> I think they do. John> FWIW, I'd have absolutely *zero* problem with fortnightly stable John> releases :)

Re: lyx 1.3.2cvs qt backtrace of crash when closing external inset.

2003-03-21 Thread John Levon
On Fri, Mar 21, 2003 at 03:27:05PM +0100, Jean-Marc Lasgouttes wrote: > John> Do people really use the externall dialog much ? > > I think they do. FWIW, I'd have absolutely *zero* problem with fortnightly stable releases :) john

Re: lyx 1.3.2cvs qt backtrace of crash when closing external inset.

2003-03-21 Thread Jean-Marc Lasgouttes
> "John" == John Levon <[EMAIL PROTECTED]> writes: John> On Fri, Mar 21, 2003 at 12:03:40PM +0100, Jean-Marc Lasgouttes John> wrote: >> Is this bad enough that we should consider releasing 1.3.2 soon? John> Do people really use the externall dialog much ? I think they do. JMarc

Re: lyx 1.3.2cvs qt backtrace of crash when closing external inset.

2003-03-21 Thread Andre Poenitz
On Fri, Mar 21, 2003 at 01:58:03PM +, John Levon wrote: > > Is this bad enough that we should consider releasing 1.3.2 soon? > > Do people really use the externall dialog much ? I do for xfig. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do th

Re: lyx 1.3.2cvs qt backtrace of crash when closing external inset.

2003-03-21 Thread John Levon
On Fri, Mar 21, 2003 at 12:03:40PM +0100, Jean-Marc Lasgouttes wrote: > Is this bad enough that we should consider releasing 1.3.2 soon? Do people really use the externall dialog much ? > Is there a workaround? Press apply then press close should be ok john

Re: lyx 1.3.2cvs qt backtrace of crash when closing external inset.

2003-03-21 Thread Jean-Marc Lasgouttes
> "John" == John Levon <[EMAIL PROTECTED]> writes: John> On Thu, Mar 20, 2003 at 11:01:23AM +0100, Helge Hafting wrote: >> Closing an external inset in lyx-1.3.1 or 1.3.2cvs may crash. It is >> reproducible John> Sheesh, well I'm a genius I made a wrong patch, fixed it, John> then applie

Re: lyx 1.3.2cvs qt backtrace of crash when closing external inset.

2003-03-20 Thread John Levon
On Thu, Mar 20, 2003 at 11:01:23AM +0100, Helge Hafting wrote: > Closing an external inset in lyx-1.3.1 or 1.3.2cvs may crash. It is > reproducible Sheesh, well I'm a genius I made a wrong patch, fixed it, then applied the wrong patch anyway and didn't notice. Great ! Expect a fix soon t

Re: lyx 1.3.2cvs qt backtrace of crash when closing external inset.

2003-03-20 Thread John Levon
On Thu, Mar 20, 2003 at 11:01:23AM +0100, Helge Hafting wrote: > Closing an external inset in lyx-1.3.1 or 1.3.2cvs may crash. It is > reproducible > with one of my files, the backtrace is at the end of this message. Damnit, how the hell did this happen :( I'll look into it - time to build 1.3

lyx 1.3.2cvs qt backtrace of crash when closing external inset.

2003-03-20 Thread Helge Hafting
Closing an external inset in lyx-1.3.1 or 1.3.2cvs may crash. It is reproducible with one of my files, the backtrace is at the end of this message. I'm using gcc/g++ 3.2 and qt3 from debian unstable. The crash is reproduced like this: Start lyx, open file scroll to the external inset bring up the

Re: backtrace of crash

2001-01-22 Thread hawk
garst gabbed > Are you sure you got your 100dpi fonts reinstalled correctly and you > probably needed to kill and restart X with a proper XF86Config if > perchance you changed that also. logout/login worked. Amongh other odd things the last few days, my xdm login box had reduced in size drasti

Re: backtrace of crash

2001-01-22 Thread Garst R. Reese
hawk wrote: > > > hawk> Also, I removed the 100dpi fonts the other day when I was > > hawk> scrounging for compile space. If anywone speaks debian, this may > > hawk> help: > > > And are things different if you re-enable them? > > They don't seem to be different, no. > > (gdb) run > Starting p

Re: backtrace of crash

2001-01-22 Thread hawk
> hawk> Also, I removed the 100dpi fonts the other day when I was > hawk> scrounging for compile space. If anywone speaks debian, this may > hawk> help: > And are things different if you re-enable them? They don't seem to be different, no. (gdb) run Starting program: /usr/local/bin/lyx Pro

Fwd: Re: backtrace of crash

2001-01-22 Thread Angus Leeming
-- Forwarded Message -- Subject: Re: backtrace of crash Date: Mon, 22 Jan 2001 10:57:10 -0500 From: hawk <[EMAIL PROTECTED]> To: Angus Leeming <[EMAIL PROTECTED]> > Looking at the "list", the symbol is "boldfontname" (no underscores --

Re: backtrace of crash

2001-01-22 Thread Jean-Marc Lasgouttes
> "hawk" == hawk <[EMAIL PROTECTED]> writes: hawk> (gdb) print bold_font_name hawk> No symbol "bold_font_name" in current context. Sorry, it should have been print boldfontname hawk> Also, I removed the 100dpi fonts the other day when I was hawk> scrounging for compile space. If anywone sp

Re: backtrace of crash

2001-01-22 Thread Angus Leeming
Looking at the "list", the symbol is "boldfontname" (no underscores -- see line 205). Please try again. Angus On Monday 22 January 2001 14:55, hawk wrote: > jmarc jiggled > > > "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes: > > > Richard> #1 0x40152b17 in XFreeFont () from /us

Re: backtrace of crash

2001-01-22 Thread hawk
jmarc jiggled > > "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes: > Richard> #1 0x40152b17 in XFreeFont () from /usr/X11R6/lib/libX11.so.6 > Richard> #2 0x400486e2 in fl_set_font_name () from > Richard> /usr/X11R6/lib/libforms.so.0.89 #3 0x80d9057 in LyXGUI::init > Richard> (this=0

Re: backtrace of crash

2001-01-22 Thread Jean-Marc Lasgouttes
> "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes: Richard> #1 0x40152b17 in XFreeFont () from /usr/X11R6/lib/libX11.so.6 Richard> #2 0x400486e2 in fl_set_font_name () from Richard> /usr/X11R6/lib/libforms.so.0.89 #3 0x80d9057 in LyXGUI::init Richard> (this=0x82ff360) at lyx_gui.C:2

backtrace of crash

2001-01-19 Thread Richard E. Hawkins
Is it the output from bt that is needed? >From today's cvs, I get a crash after the splash screen appears, but before itis filled in. bt thgive s me (i've left my own typing in from when gdb seemed to freeze . . .) #0 0x83036f8 in ?? () q #1 0x40152b17 in XFreeFont () from /usr/X11R6/lib/