rgheck wrote:
Van Damme Michael wrote:
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
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 possible
rgheck wrote:
Van Damme Michael wrote:
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
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 possible
rgheck wrote:
Van Damme Michael wrote:
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
>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
Van Damme Michael wrote:
since I like lyx I will invest time to try to find out which package is the
cause.
please do then. it could help in the similar cases too...
pavel
Van Damme Michael wrote:
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 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 my thesis
Van Damme Michael wrote:
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
On Sunday 08 March 2009 11:48:57 am James Mansion wrote:
Van Damme Michael wrote:
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
Van Damme Michael wrote:
since I like lyx I will invest time to try to find out which package is the
cause.
please do then. it could help in the similar cases too...
pavel
Van Damme Michael wrote:
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 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 my thesis
Van Damme Michael wrote:
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
On Sunday 08 March 2009 11:48:57 am James Mansion wrote:
Van Damme Michael wrote:
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
Van Damme Michael wrote:
> since I like lyx I will invest time to try to find out which package is the
> cause.
please do then. it could help in the similar cases too...
pavel
Van Damme Michael wrote:
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 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
Van Damme Michael wrote:
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
On Sunday 08 March 2009 11:48:57 am James Mansion wrote:
> Van Damme Michael wrote:
> > 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
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
Van Damme Michael wrote:
If anyone has any suggestions I would be very grateful.
from the list you gave i would try what happen if you downgrade
xorg-* and also libpng could be related.
qt upgrade didnt happen?
the last resort is to compile lyx in debug mode, run it under gdb
and provide us
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
Van Damme Michael wrote:
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
Pavel Sanda wrote:
Van Damme Michael wrote:
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
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 victim of
Van Damme Michael 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
On Saturday 07 March 2009 06:28:34 pm Van Damme Michael wrote:
On fedora, libxcb is in a separate package, but it has never been updated
(the installed version is the one that came with fedora 10 originally). I
have downgraded myx xorg packages to the previously installed version, but
that
On Saturday 07 March 2009 15:30:19 Pavel Sanda wrote:
Van Damme Michael wrote:
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
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 are no
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
Van Damme Michael wrote:
If anyone has any suggestions I would be very grateful.
from the list you gave i would try what happen if you downgrade
xorg-* and also libpng could be related.
qt upgrade didnt happen?
the last resort is to compile lyx in debug mode, run it under gdb
and provide us
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
Van Damme Michael wrote:
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
Pavel Sanda wrote:
Van Damme Michael wrote:
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
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 victim of
Van Damme Michael 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
On Saturday 07 March 2009 06:28:34 pm Van Damme Michael wrote:
On fedora, libxcb is in a separate package, but it has never been updated
(the installed version is the one that came with fedora 10 originally). I
have downgraded myx xorg packages to the previously installed version, but
that
On Saturday 07 March 2009 15:30:19 Pavel Sanda wrote:
Van Damme Michael wrote:
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
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 are no
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
Van Damme Michael wrote:
> If anyone has any suggestions I would be very grateful.
from the list you gave i would try what happen if you downgrade
xorg-* and also libpng could be related.
qt upgrade didnt happen?
the last resort is to compile lyx in debug mode, run it under gdb
and provide us
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
Van Damme Michael wrote:
>
> 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 ()
Pavel Sanda wrote:
> Van Damme Michael wrote:
> >
> > 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
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
Van Damme Michael 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
On Saturday 07 March 2009 06:28:34 pm Van Damme Michael wrote:
> On fedora, libxcb is in a separate package, but it has never been updated
> (the installed version is the one that came with fedora 10 originally). I
> have downgraded myx xorg packages to the previously installed version, but
>
On Saturday 07 March 2009 15:30:19 Pavel Sanda wrote:
> Van Damme Michael wrote:
> > 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
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
51 matches
Mail list logo
