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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
--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
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
[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.
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
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
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
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
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
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
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
--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
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
[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.
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
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
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
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
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
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
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
--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,
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
[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.
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
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
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
42 matches
Mail list logo
