Re: Some info about lyx-qt 1.3.2 segfaults
Fernando Perez wrote: 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. It's a qt bug. I can reproduce this kind of crash with any qt or kde app of my choice (kmail, knode, konqueror, qtdesigner). I have sent a bug report to trolltech, but I suspect there is nothing we can do about it. BTW: Are you all using qt 3.1.2? Regards, Juergen.
Re: Some info about lyx-qt 1.3.2 segfaults
Juergen Spitzmueller wrote: Fernando Perez wrote: 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. It's a qt bug. I can reproduce this kind of crash with any qt or kde app of my choice (kmail, knode, konqueror, qtdesigner). I have sent a bug report to trolltech, but I suspect there is nothing we can do about it. You're right, I just tested knode and I get the same crash. It always seems to occur if you try to open with the keyboard a menu entry which itself has a submenu. The submenu doesn't get highlighted, but when you press right arrow, the crash occurs. Oh well, at least now you know it's not a lyx-specific bug. It's kind of funny that this hasn't been detected before, considering how widespread KDE is. I can see lyx users not having run into it, since lyx-qt is still new and the lyx user base is much smaller than the KDE one. I hope the trolltech team gives you some response. BTW: Are you all using qt 3.1.2? Yup: qt-3.1.2-7.fdr.0.rh80 This rpm is from freshrpms.org. Best, f.
Re: Some info about lyx-qt 1.3.2 segfaults
On Wed, Jul 02, 2003 at 08:10:33AM -0600, Fernando Perez wrote: funny that this hasn't been detected before, considering how widespread KDE is. I can see lyx users not having run into it, since lyx-qt is still new and the lyx user base is much smaller than the KDE one. I hope the Qt 3.1.2 is relatively new, so won't be in wide use yet. I guess we can expect updates relatively soon regards john
Re: Some info about lyx-qt 1.3.2 segfaults
John Levon wrote: On Wed, Jul 02, 2003 at 08:10:33AM -0600, Fernando Perez wrote: funny that this hasn't been detected before, considering how widespread KDE is. I can see lyx users not having run into it, since lyx-qt is still new and the lyx user base is much smaller than the KDE one. I hope the Qt 3.1.2 is relatively new, so won't be in wide use yet. I guess we can expect updates relatively soon Right. I hadn't realized that this was a qt-3.1.2-specific bug, which was not present in 3.1.1. I only learned that after reading the thread in lyx-dev where you guys discussed that fact. Best, f.
Re: Some info about lyx-qt 1.3.2 segfaults
Fernando Perez wrote: 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. It's a qt bug. I can reproduce this kind of crash with any qt or kde app of my choice (kmail, knode, konqueror, qtdesigner). I have sent a bug report to trolltech, but I suspect there is nothing we can do about it. BTW: Are you all using qt 3.1.2? Regards, Juergen.
Re: Some info about lyx-qt 1.3.2 segfaults
Juergen Spitzmueller wrote: Fernando Perez wrote: 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. It's a qt bug. I can reproduce this kind of crash with any qt or kde app of my choice (kmail, knode, konqueror, qtdesigner). I have sent a bug report to trolltech, but I suspect there is nothing we can do about it. You're right, I just tested knode and I get the same crash. It always seems to occur if you try to open with the keyboard a menu entry which itself has a submenu. The submenu doesn't get highlighted, but when you press right arrow, the crash occurs. Oh well, at least now you know it's not a lyx-specific bug. It's kind of funny that this hasn't been detected before, considering how widespread KDE is. I can see lyx users not having run into it, since lyx-qt is still new and the lyx user base is much smaller than the KDE one. I hope the trolltech team gives you some response. BTW: Are you all using qt 3.1.2? Yup: qt-3.1.2-7.fdr.0.rh80 This rpm is from freshrpms.org. Best, f.
Re: Some info about lyx-qt 1.3.2 segfaults
On Wed, Jul 02, 2003 at 08:10:33AM -0600, Fernando Perez wrote: funny that this hasn't been detected before, considering how widespread KDE is. I can see lyx users not having run into it, since lyx-qt is still new and the lyx user base is much smaller than the KDE one. I hope the Qt 3.1.2 is relatively new, so won't be in wide use yet. I guess we can expect updates relatively soon regards john
Re: Some info about lyx-qt 1.3.2 segfaults
John Levon wrote: On Wed, Jul 02, 2003 at 08:10:33AM -0600, Fernando Perez wrote: funny that this hasn't been detected before, considering how widespread KDE is. I can see lyx users not having run into it, since lyx-qt is still new and the lyx user base is much smaller than the KDE one. I hope the Qt 3.1.2 is relatively new, so won't be in wide use yet. I guess we can expect updates relatively soon Right. I hadn't realized that this was a qt-3.1.2-specific bug, which was not present in 3.1.1. I only learned that after reading the thread in lyx-dev where you guys discussed that fact. Best, f.
Re: Some info about lyx-qt 1.3.2 segfaults
Fernando Perez wrote: > 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. It's a qt bug. I can reproduce this kind of crash with any qt or kde app of my choice (kmail, knode, konqueror, qtdesigner). I have sent a bug report to trolltech, but I suspect there is nothing we can do about it. BTW: Are you all using qt 3.1.2? Regards, Juergen.
Re: Some info about lyx-qt 1.3.2 segfaults
Juergen Spitzmueller wrote: Fernando Perez wrote: 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. It's a qt bug. I can reproduce this kind of crash with any qt or kde app of my choice (kmail, knode, konqueror, qtdesigner). I have sent a bug report to trolltech, but I suspect there is nothing we can do about it. You're right, I just tested knode and I get the same crash. It always seems to occur if you try to open with the keyboard a menu entry which itself has a submenu. The submenu doesn't get highlighted, but when you press right arrow, the crash occurs. Oh well, at least now you know it's not a lyx-specific bug. It's kind of funny that this hasn't been detected before, considering how widespread KDE is. I can see lyx users not having run into it, since lyx-qt is still new and the lyx user base is much smaller than the KDE one. I hope the trolltech team gives you some response. BTW: Are you all using qt 3.1.2? Yup: qt-3.1.2-7.fdr.0.rh80 This rpm is from freshrpms.org. Best, f.
Re: Some info about lyx-qt 1.3.2 segfaults
On Wed, Jul 02, 2003 at 08:10:33AM -0600, Fernando Perez wrote: > funny that this hasn't been detected before, considering how widespread KDE > is. I can see lyx users not having run into it, since lyx-qt is still new > and the lyx user base is much smaller than the KDE one. I hope the Qt 3.1.2 is relatively new, so won't be in wide use yet. I guess we can expect updates relatively soon regards john
Re: Some info about lyx-qt 1.3.2 segfaults
John Levon wrote: On Wed, Jul 02, 2003 at 08:10:33AM -0600, Fernando Perez wrote: funny that this hasn't been detected before, considering how widespread KDE is. I can see lyx users not having run into it, since lyx-qt is still new and the lyx user base is much smaller than the KDE one. I hope the Qt 3.1.2 is relatively new, so won't be in wide use yet. I guess we can expect updates relatively soon Right. I hadn't realized that this was a qt-3.1.2-specific bug, which was not present in 3.1.1. I only learned that after reading the thread in lyx-dev where you guys discussed that fact. Best, f.
Some info about lyx-qt 1.3.2 segfaults
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.
Re: Some info about lyx-qt 1.3.2 segfaults
On 2003-07-01, 17:52 GMT, Fernando Perez wrote: Platform: RedHat 8.0, KDE 3.1, Qt 3.1. Lyx 1.3.2, using the Lyx.org supplied rpms. I've got the same with Debian 3.0, KDE 3.1.2, LyX 1.3.2 compiled by hand on my computer. This is the end of gdb story: (no debugging symbols found)...(no debugging symbols found)...[New\ Cannot find thread 2049: invalid thread handle (gdb) lyx: SIGHUP signal caught Ukonen (SIGTERM) ~$ Bye. This crash is 100% reproducible. Sure it is. I hope this is of some use. Me too. Matej -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488
Re: Some info about lyx-qt 1.3.2 segfaults
Fernando Perez wrote: 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 Could you try to get a complete backtrace? Not running kde, or enabling/using a core file maybe helps. Regards, Alfredo
Re: Some info about lyx-qt 1.3.2 segfaults
Alfredo Braunstein wrote: Could you try to get a complete backtrace? Not running kde, or enabling/using a core file maybe helps. Under Gnome it's even a bit worse: after killing gdb and reentering X, the mouse pointer disappears! Hitting Alt-F1 to get a keyboard menu seems to resucitate the pointer. Anyway, enabling core files doesn't seem to help much, as the lyx.org rpms have no debugging info in them. Sorry, but I don't have time right now to make a debug build and play with it. If I make lyx dump core and try to load the core into gdb, the backtrace is pretty uninformative: (gdb) core core.18511 Core was generated by `lyx'. Program terminated with signal 6, Aborted. #0 0x42028851 in ?? () (gdb) bt full #0 0x42028851 in ?? () No symbol table info available. #1 0x420284f4 in ?? () No symbol table info available. #2 0x42029beb in ?? () No symbol table info available. ... more of the same (19 stack frames total) ... Sorry for not being able to work more on this one. Best, f.
Re: Some info about lyx-qt 1.3.2 segfaults
--NMuMz9nt05w80d4+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Matej Cepl [EMAIL PROTECTED], 2003-07-01 14:22 -0400: On 2003-07-01, 17:52 GMT, Fernando Perez wrote: Platform: RedHat 8.0, KDE 3.1, Qt 3.1. Lyx 1.3.2, using the Lyx.org su= pplied=20 rpms. =20 I've got the same with Debian 3.0, KDE 3.1.2, LyX 1.3.2 compiled by hand on my computer. [...] This crash is 100% reproducible. =20 Sure it is. Then again it works for me (doesn't crash when I do what the OP did): [EMAIL PROTECTED]:~$ lyx --version LyX 1.3.2 of Tue, May 6 2003 Built on May 12 2003, 15:27:38 Configuration Host type: i686-pc-linux-gnu Special build flags:use-pspell C Compiler: gcc C Compiler flags: -g -O2 C++ Compiler: g++ (2.95.4) C++ Compiler flags: -O2 -Wno-non-template-friend -ftemplate-d= epth-30 Linker flags: =20 Frontend: qt Qt version: 3.0.3=20 LyX binary dir: /usr/bin LyX files dir: /usr/share/lyx Also self-compiled on Debian (woody w/ Adrian Bunk's additions).=20 -Andre --NMuMz9nt05w80d4+ Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/Ad3cmlbrvn+0waMRAqokAJwKj6VUTWZmaneptT0AqYMcNPU/AACgtUQC xrLx+g0rZ+WjMXa0EcLTHzU= =Cu8v -END PGP SIGNATURE- --NMuMz9nt05w80d4+--
Re: Some info about lyx-qt 1.3.2 segfaults
Yes, Fernando. I experience the same failure, and posted the exact same screen copy of gdb output to the lyx-devel list last Friday. I can't get my environment to survive the crash either, but ONLY under gdb, oddly. No one has offered up an answer, and others suggest everything works the right way. Someone suggested that my build might be on top of incompatible libraries and includes, but did not suggest how to investigate this. More broadly, the failure occurs whenever trying to access a submenu using keyboard shortcuts, under qt. I'm using Redhat 9, kde/qt 3.1.2. Failure under my own builds and circulating rh9 rpms for lyx 1.3.2. On Tue, Jul 01, 2003 at 11:52:16AM -0600, 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.
Re: Some info about lyx-qt 1.3.2 segfaults
[EMAIL PROTECTED] wrote: way. Someone suggested that my build might be on top of incompatible libraries and includes, but did not suggest how to investigate this. It seems that we have to discard this, since you (and others) get the same with the precompiled version/with standard systems. More broadly, the failure occurs whenever trying to access a submenu using keyboard shortcuts, under qt. I'm using Redhat 9, kde/qt 3.1.2. Failure under my own builds and circulating rh9 rpms for lyx 1.3.2. I don't know if I've mentioned it, but I have Redhat 9, with the provided qt 3.1.1-6 and I cannot reproduce it at all. Regards, Alfredo
Re: Some info about lyx-qt 1.3.2 segfaults
Fernando Perez wrote: Anyway, enabling core files doesn't seem to help much, as the lyx.org rpms have no debugging info in them. Sorry, but I don't have time right now to Ah yes, forgot about that. Thanks anyway, Alfredo
Re: Some info about lyx-qt 1.3.2 segfaults
On 2003-07-01, 20:42 GMT, Alfredo Braunstein wrote: way. Someone suggested that my build might be on top of incompatible libraries and includes, but did not suggest how to investigate this. It seems that we have to discard this, since you (and others) get the same with the precompiled version/with standard systems. Just to note, that my system is not standard (using additional KDE from debian.kde.org). Matej -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488
Re: Some info about lyx-qt 1.3.2 segfaults
Alfredo Braunstein wrote: I don't know if I've mentioned it, but I have Redhat 9, with the provided qt 3.1.1-6 and I cannot reproduce it at all. More specifically (in case it helps you guys), I'm using RedHat 8.0, but I updated my qt/kde from freshrpms.org to: kdelibs-3.1.2-0.fdr.3.rh80 qt-3.1.2-7.fdr.0.rh80 My Lyx is from lyx.org: lyx-1.3.2-1_qt Again, sorry I can't do deeper debugging here. Best, f.
Some info about lyx-qt 1.3.2 segfaults
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.
Re: Some info about lyx-qt 1.3.2 segfaults
On 2003-07-01, 17:52 GMT, Fernando Perez wrote: Platform: RedHat 8.0, KDE 3.1, Qt 3.1. Lyx 1.3.2, using the Lyx.org supplied rpms. I've got the same with Debian 3.0, KDE 3.1.2, LyX 1.3.2 compiled by hand on my computer. This is the end of gdb story: (no debugging symbols found)...(no debugging symbols found)...[New\ Cannot find thread 2049: invalid thread handle (gdb) lyx: SIGHUP signal caught Ukonen (SIGTERM) ~$ Bye. This crash is 100% reproducible. Sure it is. I hope this is of some use. Me too. Matej -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488
Re: Some info about lyx-qt 1.3.2 segfaults
Fernando Perez wrote: 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 Could you try to get a complete backtrace? Not running kde, or enabling/using a core file maybe helps. Regards, Alfredo
Re: Some info about lyx-qt 1.3.2 segfaults
Alfredo Braunstein wrote: Could you try to get a complete backtrace? Not running kde, or enabling/using a core file maybe helps. Under Gnome it's even a bit worse: after killing gdb and reentering X, the mouse pointer disappears! Hitting Alt-F1 to get a keyboard menu seems to resucitate the pointer. Anyway, enabling core files doesn't seem to help much, as the lyx.org rpms have no debugging info in them. Sorry, but I don't have time right now to make a debug build and play with it. If I make lyx dump core and try to load the core into gdb, the backtrace is pretty uninformative: (gdb) core core.18511 Core was generated by `lyx'. Program terminated with signal 6, Aborted. #0 0x42028851 in ?? () (gdb) bt full #0 0x42028851 in ?? () No symbol table info available. #1 0x420284f4 in ?? () No symbol table info available. #2 0x42029beb in ?? () No symbol table info available. ... more of the same (19 stack frames total) ... Sorry for not being able to work more on this one. Best, f.
Re: Some info about lyx-qt 1.3.2 segfaults
--NMuMz9nt05w80d4+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Matej Cepl [EMAIL PROTECTED], 2003-07-01 14:22 -0400: On 2003-07-01, 17:52 GMT, Fernando Perez wrote: Platform: RedHat 8.0, KDE 3.1, Qt 3.1. Lyx 1.3.2, using the Lyx.org su= pplied=20 rpms. =20 I've got the same with Debian 3.0, KDE 3.1.2, LyX 1.3.2 compiled by hand on my computer. [...] This crash is 100% reproducible. =20 Sure it is. Then again it works for me (doesn't crash when I do what the OP did): [EMAIL PROTECTED]:~$ lyx --version LyX 1.3.2 of Tue, May 6 2003 Built on May 12 2003, 15:27:38 Configuration Host type: i686-pc-linux-gnu Special build flags:use-pspell C Compiler: gcc C Compiler flags: -g -O2 C++ Compiler: g++ (2.95.4) C++ Compiler flags: -O2 -Wno-non-template-friend -ftemplate-d= epth-30 Linker flags: =20 Frontend: qt Qt version: 3.0.3=20 LyX binary dir: /usr/bin LyX files dir: /usr/share/lyx Also self-compiled on Debian (woody w/ Adrian Bunk's additions).=20 -Andre --NMuMz9nt05w80d4+ Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/Ad3cmlbrvn+0waMRAqokAJwKj6VUTWZmaneptT0AqYMcNPU/AACgtUQC xrLx+g0rZ+WjMXa0EcLTHzU= =Cu8v -END PGP SIGNATURE- --NMuMz9nt05w80d4+--
Re: Some info about lyx-qt 1.3.2 segfaults
Yes, Fernando. I experience the same failure, and posted the exact same screen copy of gdb output to the lyx-devel list last Friday. I can't get my environment to survive the crash either, but ONLY under gdb, oddly. No one has offered up an answer, and others suggest everything works the right way. Someone suggested that my build might be on top of incompatible libraries and includes, but did not suggest how to investigate this. More broadly, the failure occurs whenever trying to access a submenu using keyboard shortcuts, under qt. I'm using Redhat 9, kde/qt 3.1.2. Failure under my own builds and circulating rh9 rpms for lyx 1.3.2. On Tue, Jul 01, 2003 at 11:52:16AM -0600, 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.
Re: Some info about lyx-qt 1.3.2 segfaults
[EMAIL PROTECTED] wrote: way. Someone suggested that my build might be on top of incompatible libraries and includes, but did not suggest how to investigate this. It seems that we have to discard this, since you (and others) get the same with the precompiled version/with standard systems. More broadly, the failure occurs whenever trying to access a submenu using keyboard shortcuts, under qt. I'm using Redhat 9, kde/qt 3.1.2. Failure under my own builds and circulating rh9 rpms for lyx 1.3.2. I don't know if I've mentioned it, but I have Redhat 9, with the provided qt 3.1.1-6 and I cannot reproduce it at all. Regards, Alfredo
Re: Some info about lyx-qt 1.3.2 segfaults
Fernando Perez wrote: Anyway, enabling core files doesn't seem to help much, as the lyx.org rpms have no debugging info in them. Sorry, but I don't have time right now to Ah yes, forgot about that. Thanks anyway, Alfredo
Re: Some info about lyx-qt 1.3.2 segfaults
On 2003-07-01, 20:42 GMT, Alfredo Braunstein wrote: way. Someone suggested that my build might be on top of incompatible libraries and includes, but did not suggest how to investigate this. It seems that we have to discard this, since you (and others) get the same with the precompiled version/with standard systems. Just to note, that my system is not standard (using additional KDE from debian.kde.org). Matej -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488
Re: Some info about lyx-qt 1.3.2 segfaults
Alfredo Braunstein wrote: I don't know if I've mentioned it, but I have Redhat 9, with the provided qt 3.1.1-6 and I cannot reproduce it at all. More specifically (in case it helps you guys), I'm using RedHat 8.0, but I updated my qt/kde from freshrpms.org to: kdelibs-3.1.2-0.fdr.3.rh80 qt-3.1.2-7.fdr.0.rh80 My Lyx is from lyx.org: lyx-1.3.2-1_qt Again, sorry I can't do deeper debugging here. Best, f.
Some info about lyx-qt 1.3.2 segfaults
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.
Re: Some info about lyx-qt 1.3.2 segfaults
On 2003-07-01, 17:52 GMT, Fernando Perez wrote: > Platform: RedHat 8.0, KDE 3.1, Qt 3.1. Lyx 1.3.2, using the Lyx.org supplied > rpms. I've got the same with Debian 3.0, KDE 3.1.2, LyX 1.3.2 compiled by hand on my computer. This is the end of gdb story: (no debugging symbols found)...(no debugging symbols found)...[New\ Cannot find thread 2049: invalid thread handle (gdb) lyx: SIGHUP signal caught Ukončen (SIGTERM) ~$ Bye. > This crash is 100% reproducible. Sure it is. > I hope this is of some use. Me too. Matej -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488
Re: Some info about lyx-qt 1.3.2 segfaults
Fernando Perez wrote: > 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 Could you try to get a complete backtrace? Not running kde, or enabling/using a core file maybe helps. Regards, Alfredo
Re: Some info about lyx-qt 1.3.2 segfaults
Alfredo Braunstein wrote: Could you try to get a complete backtrace? Not running kde, or enabling/using a core file maybe helps. Under Gnome it's even a bit worse: after killing gdb and reentering X, the mouse pointer disappears! Hitting Alt-F1 to get a keyboard menu seems to resucitate the pointer. Anyway, enabling core files doesn't seem to help much, as the lyx.org rpms have no debugging info in them. Sorry, but I don't have time right now to make a debug build and play with it. If I make lyx dump core and try to load the core into gdb, the backtrace is pretty uninformative: (gdb) core core.18511 Core was generated by `lyx'. Program terminated with signal 6, Aborted. #0 0x42028851 in ?? () (gdb) bt full #0 0x42028851 in ?? () No symbol table info available. #1 0x420284f4 in ?? () No symbol table info available. #2 0x42029beb in ?? () No symbol table info available. ... more of the same (19 stack frames total) ... Sorry for not being able to work more on this one. Best, f.
Re: Some info about lyx-qt 1.3.2 segfaults
--NMuMz9nt05w80d4+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Matej Cepl <[EMAIL PROTECTED]>, 2003-07-01 14:22 -0400: > On 2003-07-01, 17:52 GMT, Fernando Perez wrote: > > Platform: RedHat 8.0, KDE 3.1, Qt 3.1. Lyx 1.3.2, using the Lyx.org su= pplied=20 > > rpms. >=20 > I've got the same with Debian 3.0, KDE 3.1.2, LyX 1.3.2 compiled by hand > on my computer. [...] > > This crash is 100% reproducible. >=20 > Sure it is. Then again it works for me (doesn't crash when I do what the OP did): [EMAIL PROTECTED]:~$ lyx --version LyX 1.3.2 of Tue, May 6 2003 Built on May 12 2003, 15:27:38 Configuration Host type: i686-pc-linux-gnu Special build flags:use-pspell C Compiler: gcc C Compiler flags: -g -O2 C++ Compiler: g++ (2.95.4) C++ Compiler flags: -O2 -Wno-non-template-friend -ftemplate-d= epth-30 Linker flags: =20 Frontend: qt Qt version: 3.0.3=20 LyX binary dir: /usr/bin LyX files dir: /usr/share/lyx Also self-compiled on Debian (woody w/ Adrian Bunk's additions).=20 -Andre --NMuMz9nt05w80d4+ Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/Ad3cmlbrvn+0waMRAqokAJwKj6VUTWZmaneptT0AqYMcNPU/AACgtUQC xrLx+g0rZ+WjMXa0EcLTHzU= =Cu8v -END PGP SIGNATURE- --NMuMz9nt05w80d4+--
Re: Some info about lyx-qt 1.3.2 segfaults
Yes, Fernando. I experience the same failure, and posted the exact same screen copy of gdb output to the lyx-devel list last Friday. I can't get my environment to survive the crash either, but ONLY under gdb, oddly. No one has offered up an answer, and others suggest everything works the right way. Someone suggested that my build might be on top of incompatible libraries and includes, but did not suggest how to investigate this. More broadly, the failure occurs whenever trying to access a submenu using keyboard shortcuts, under qt. I'm using Redhat 9, kde/qt 3.1.2. Failure under my own builds and circulating rh9 rpms for lyx 1.3.2. On Tue, Jul 01, 2003 at 11:52:16AM -0600, 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.
Re: Some info about lyx-qt 1.3.2 segfaults
[EMAIL PROTECTED] wrote: > way. Someone suggested that my build might be on top of incompatible > libraries and includes, but did not suggest how to investigate this. It seems that we have to discard this, since you (and others) get the same with the precompiled version/with standard systems. > More broadly, the failure occurs whenever trying to access a submenu using > keyboard shortcuts, under qt. > > I'm using Redhat 9, kde/qt 3.1.2. Failure under my own builds and > circulating rh9 rpms for lyx 1.3.2. I don't know if I've mentioned it, but I have Redhat 9, with the provided qt 3.1.1-6 and I cannot reproduce it at all. Regards, Alfredo
Re: Some info about lyx-qt 1.3.2 segfaults
Fernando Perez wrote: > Anyway, enabling core files doesn't seem to help much, as the lyx.org rpms > have no debugging info in them. Sorry, but I don't have time right now to Ah yes, forgot about that. Thanks anyway, Alfredo
Re: Some info about lyx-qt 1.3.2 segfaults
On 2003-07-01, 20:42 GMT, Alfredo Braunstein wrote: >> way. Someone suggested that my build might be on top of incompatible >> libraries and includes, but did not suggest how to investigate this. > > It seems that we have to discard this, since you (and others) get the same > with the precompiled version/with standard systems. Just to note, that my system is not standard (using additional KDE from debian.kde.org). Matej -- Matej Cepl, GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488
Re: Some info about lyx-qt 1.3.2 segfaults
Alfredo Braunstein wrote: I don't know if I've mentioned it, but I have Redhat 9, with the provided qt 3.1.1-6 and I cannot reproduce it at all. More specifically (in case it helps you guys), I'm using RedHat 8.0, but I updated my qt/kde from freshrpms.org to: kdelibs-3.1.2-0.fdr.3.rh80 qt-3.1.2-7.fdr.0.rh80 My Lyx is from lyx.org: lyx-1.3.2-1_qt Again, sorry I can't do deeper debugging here. Best, f.
