Hi Fernando
my computer is currently rh8.0 [1] with all current redhat updates.
Using a locally compiled lyx qt binary , does NOT crash following your
procedure.
Note my qt libs are older than yours.
[EMAIL PROTECTED] john]$ ldd `which lyx`
libqt-mt.so.3 => /usr/lib/qt-3.0.5/lib/libqt-mt.so.3
(0x40028000)
libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x40657000)
libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x40660000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40677000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40755000)
libm.so.6 => /lib/i686/libm.so.6 (0x40807000)
libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x4082a000)
libpthread.so.0 => /lib/i686/libpthread.so.0 (0x40832000)
libcups.so.2 => /usr/lib/libcups.so.2 (0x40882000)
libmng.so.1 => /usr/lib/libmng.so.1 (0x4089c000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x408e0000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0x408fe000)
libz.so.1 => /usr/lib/libz.so.1 (0x40922000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x40930000)
libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x409a3000)
libdl.so.2 => /lib/libdl.so.2 (0x409b9000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x409bc000)
libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x409ca000)
libXft.so.2 => /usr/lib/libXft.so.2 (0x409d0000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x409e2000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
libssl.so.2 => /lib/libssl.so.2 (0x40a07000)
libcrypto.so.2 => /lib/libcrypto.so.2 (0x40a37000)
libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x40b0b000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x40b5e000)
libexpat.so.0 => /usr/lib/libexpat.so.0 (0x40ba7000)
[1] xinerama on rh9's XFree86 4.3 is too unstable with a matrox G450 to
use. If you have not used xinerama on 2 monitors, I suggest you don't,
as its impossible to go back. Disabling x font render helps some.
john
On Wed, 2003-07-02 at 03:52, Fernando Perez wrote:
> Hi all,
>
> I'm not subscribed to lyx-dev and I just have already too many email lists.
> But I saw a discussion about lyx-qt 1.3.2 segfaulting under redhat, and I
> figured I'd add a bit of info in case it helps the developers.
>
> Platform: RedHat 8.0, KDE 3.1, Qt 3.1. Lyx 1.3.2, using the Lyx.org supplied
> rpms.
>
> Crash mode: start new document, press Alt-I-S (insert special character). The
> 'Special' menu entry does NOT get highlighted, as it should. Now, press right
> arrow. Lyx crashes.
>
> I tried it under gdb, and when lyx dies, everything seems to lock up,
> including the window manager. But there's a way to recover: type Ctrl-Alt-F1,
> log into a text terminal, and kill the gdb process by hand. Then type Alt-F7
> to go back to X. The system is now unfrozen.
>
> The following is a screen copy of the gdb output:
>
> [~]> gdb lyx
> GNU gdb Red Hat Linux (5.2.1-4)
> Copyright 2002 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 "i386-redhat-linux"...(no debugging symbols found)...
> (gdb) run
> Starting program: /usr/bin/lyx
> [New Thread 16384 (LWP 17855)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 17855)]
> 0x40317212 in QPopupMenu::keyPressEvent(QKeyEvent*) () from
> /usr/lib/qt-3.1/lib/libqt-mt.so.3
> (gdb) Killed
>
> lyx: SIGHUP signal caught
> Bye.
> [~]> Mutex destroy failure: Device or resource busy
>
>
>
> This crash is 100% reproducible.
>
> I hope this is of some use.
>
> Best,
>
> f.
