>rgheck wrote:
>>>
>> I'll have a look at this under one of my Fedora 10 machines.
>>
>As I said in the bug report, I was unable to reproduce this problem
>under F10, even fully updated. And that was using the test file attached
>to the report, trying to follow the instructions given. It's pos
>> I have downloaded version 1.6.2svn (from the svn server) and tried it, but
>> the problem remains.
>>
>Is is quick enough to reproduce (or you comuputer fast enough) to run
>Lyx under valgrind until you hit the problem?
>
>James
I've never used valgrind, but it is quick to reproduce. When
Pavel and Steve, thanks for your helpful comments.
>maybe. but there are striking similarities - lyx input frozen, no cpu load, bt
>points somewhere
>in between qt<->xorg, libxcb used; (in this we enter there through
>QInputContext::reset()).
It's true that there are many similarities. There a
Pavel Sanda wrote:
>> #0 0x00943416 in __kernel_vsyscall ()
>> #1 0x006a83d1 in select () from /lib/libc.so.6
>> #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1
>> #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1
>
>ahh i have seen this backtrace
>i guess you are the next
Thank you for your reply.
I've compiled lyx-1.6.1 in debug mode (using the latest stable source available
on the lyx site) and ran it under gdb. Once locked-up, I interrupted it in gdb
and got the following backtrace:
#0 0x00943416 in __kernel_vsyscall ()
#1 0x006a83d1 in select () from /lib/
Hi all,
over the last few months, I've been writing my thesis in lyx (using it many
hours every day). I'm using lyx-1.6.1 on fedora 10 (the version available
through fedora's package manager yum).
Since this week, however, I'm experiencing very frequent crashes (being able to
work for 15 minute
