Neither me, under Windows XP and the last stable LyX.
2009/2/21 Stefano Franchi fran...@philosophy.tamu.edu
On Friday 20 February 2009 17:49:35 Vincent van Ravesteijn wrote:
Vincent van Ravesteijn schreef:
Before releasing 1.6.0 there were a number of bugs which depended on
the location
On 21/02/2009 11:21, Murat Yildizoglu wrote:
Neither me, under Windows XP and the last stable LyX.
Stefano seems to be using a debug build. In this build mode an assertion
causes a crash each time. With a release build assertions are softer
and, most of the time, the only visible effect is a
On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
On 21/02/2009 11:21, Murat Yildizoglu wrote:
Neither me, under Windows XP and the last stable LyX.
Stefano seems to be using a debug build. In this build mode an assertion
causes a crash each time. With a release build assertions
On 21/02/2009 15:10, Stefano Franchi wrote:
On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
On 21/02/2009 11:21, Murat Yildizoglu wrote:
Neither me, under Windows XP and the last stable LyX.
Stefano seems to be using a debug build. In this build mode an assertion
causes a crash
Before releasing 1.6.0 there were a number of bugs
which depended on the location of the cursor at the time of
right-clicking. Maybe this helps you ..
I mean, there happen strange things if you right-click on a
certain inset A.. keep the mouse down and then release it at
another inset
Marcelo Acuña schreef:
Before releasing 1.6.0 there were a number of bugs
which depended on the location of the cursor at the time of
right-clicking. Maybe this helps you ..
I mean, there happen strange things if you right-click on a
certain inset A.. keep the mouse down and then
Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is a message on the console or the
cursor is moving weirdly.
Stefano, whenever you need to work
On 21/02/2009 16:13, Marcelo Acuña wrote:
Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is a message on the console or the
cursor is moving weirdly.
On Saturday 21 February 2009 08:19:16 Abdelrazak Younes wrote:
On 21/02/2009 15:10, Stefano Franchi wrote:
On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
On 21/02/2009 11:21, Murat Yildizoglu wrote:
Neither me, under Windows XP and the last stable LyX.
Stefano seems to
Stefano Franchi wrote:
So what's the best way to have both a debug-enabled and a
plain vanilla lyx installed?
Don't install the debug version. You can run it from where you compiled
it. I just use a little script:
#!/bin/bash
USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
if [ -e
excuse me. I want to say that I compiled lyx without
any debug mode.
When I writing quickly, I get Lyx frozen like
Stefano. I can press F2 key and save my work.
If you can press F2 and save your work then LyX is not
frozen, it's just that it lost the editing focus. This
happens for
On Saturday 21 February 2009 09:46:36 rgheck wrote:
Stefano Franchi wrote:
So what's the best way to have both a debug-enabled and a
plain vanilla lyx installed?
Don't install the debug version. You can run it from where you compiled
it. I just use a little script:
#!/bin/bash
Stefano Franchi wrote:
On Saturday 21 February 2009 09:46:36 rgheck wrote:
Stefano Franchi wrote:
So what's the best way to have both a debug-enabled and a
plain vanilla lyx installed?
Don't install the debug version. You can run it from where you compiled
it. I just use a
On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:
Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is a message on the console or the
On 21/02/2009 17:49, Stefano Franchi wrote:
On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:
Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is
Neither me, under Windows XP and the last stable LyX.
2009/2/21 Stefano Franchi fran...@philosophy.tamu.edu
On Friday 20 February 2009 17:49:35 Vincent van Ravesteijn wrote:
Vincent van Ravesteijn schreef:
Before releasing 1.6.0 there were a number of bugs which depended on
the location
On 21/02/2009 11:21, Murat Yildizoglu wrote:
Neither me, under Windows XP and the last stable LyX.
Stefano seems to be using a debug build. In this build mode an assertion
causes a crash each time. With a release build assertions are softer
and, most of the time, the only visible effect is a
On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
On 21/02/2009 11:21, Murat Yildizoglu wrote:
Neither me, under Windows XP and the last stable LyX.
Stefano seems to be using a debug build. In this build mode an assertion
causes a crash each time. With a release build assertions
On 21/02/2009 15:10, Stefano Franchi wrote:
On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
On 21/02/2009 11:21, Murat Yildizoglu wrote:
Neither me, under Windows XP and the last stable LyX.
Stefano seems to be using a debug build. In this build mode an assertion
causes a crash
Before releasing 1.6.0 there were a number of bugs
which depended on the location of the cursor at the time of
right-clicking. Maybe this helps you ..
I mean, there happen strange things if you right-click on a
certain inset A.. keep the mouse down and then release it at
another inset
Marcelo Acuña schreef:
Before releasing 1.6.0 there were a number of bugs
which depended on the location of the cursor at the time of
right-clicking. Maybe this helps you ..
I mean, there happen strange things if you right-click on a
certain inset A.. keep the mouse down and then
Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is a message on the console or the
cursor is moving weirdly.
Stefano, whenever you need to work
On 21/02/2009 16:13, Marcelo Acuña wrote:
Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is a message on the console or the
cursor is moving weirdly.
On Saturday 21 February 2009 08:19:16 Abdelrazak Younes wrote:
On 21/02/2009 15:10, Stefano Franchi wrote:
On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
On 21/02/2009 11:21, Murat Yildizoglu wrote:
Neither me, under Windows XP and the last stable LyX.
Stefano seems to
Stefano Franchi wrote:
So what's the best way to have both a debug-enabled and a
plain vanilla lyx installed?
Don't install the debug version. You can run it from where you compiled
it. I just use a little script:
#!/bin/bash
USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
if [ -e
excuse me. I want to say that I compiled lyx without
any debug mode.
When I writing quickly, I get Lyx frozen like
Stefano. I can press F2 key and save my work.
If you can press F2 and save your work then LyX is not
frozen, it's just that it lost the editing focus. This
happens for
On Saturday 21 February 2009 09:46:36 rgheck wrote:
Stefano Franchi wrote:
So what's the best way to have both a debug-enabled and a
plain vanilla lyx installed?
Don't install the debug version. You can run it from where you compiled
it. I just use a little script:
#!/bin/bash
Stefano Franchi wrote:
On Saturday 21 February 2009 09:46:36 rgheck wrote:
Stefano Franchi wrote:
So what's the best way to have both a debug-enabled and a
plain vanilla lyx installed?
Don't install the debug version. You can run it from where you compiled
it. I just use a
On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:
Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is a message on the console or the
On 21/02/2009 17:49, Stefano Franchi wrote:
On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:
Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is
Neither me, under Windows XP and the last stable LyX.
2009/2/21 Stefano Franchi
> On Friday 20 February 2009 17:49:35 Vincent van Ravesteijn wrote:
> > Vincent van Ravesteijn schreef:
> > >> Before releasing 1.6.0 there were a number of bugs which depended on
> > >>
On 21/02/2009 11:21, Murat Yildizoglu wrote:
Neither me, under Windows XP and the last stable LyX.
Stefano seems to be using a debug build. In this build mode an assertion
causes a crash each time. With a release build assertions are "softer"
and, most of the time, the only visible effect is
On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
> On 21/02/2009 11:21, Murat Yildizoglu wrote:
> > Neither me, under Windows XP and the last stable LyX.
>
> Stefano seems to be using a debug build. In this build mode an assertion
> causes a crash each time. With a release build
On 21/02/2009 15:10, Stefano Franchi wrote:
On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
On 21/02/2009 11:21, Murat Yildizoglu wrote:
Neither me, under Windows XP and the last stable LyX.
Stefano seems to be using a debug build. In this build mode an assertion
causes a crash
> > Before releasing 1.6.0 there were a number of bugs
> which depended on the location of the cursor at the time of
> right-clicking. Maybe this helps you ..
> I mean, there happen strange things if you right-click on a
> certain inset A.. keep the mouse down and then release it at
> another
Marcelo Acuña schreef:
Before releasing 1.6.0 there were a number of bugs
which depended on the location of the cursor at the time of
right-clicking. Maybe this helps you ..
I mean, there happen strange things if you right-click on a
certain inset A.. keep the mouse down and then
> Stefano seems to be using a debug build. In this build mode
> an assertion causes a crash each time. With a release build
> assertions are "softer" and, most of the time, the
> only visible effect is a message on the console or the
> cursor is moving weirdly.
>
> Stefano, whenever you need to
On 21/02/2009 16:13, Marcelo Acuña wrote:
Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are "softer" and, most of the time, the
only visible effect is a message on the console or the
cursor is moving weirdly.
On Saturday 21 February 2009 08:19:16 Abdelrazak Younes wrote:
> On 21/02/2009 15:10, Stefano Franchi wrote:
> > On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
> >> On 21/02/2009 11:21, Murat Yildizoglu wrote:
> >>> Neither me, under Windows XP and the last stable LyX.
> >>
> >>
Stefano Franchi wrote:
So what's the best way to have both a debug-enabled and a
plain vanilla lyx installed?
Don't install the debug version. You can run it from where you compiled
it. I just use a little script:
#!/bin/bash
USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
if [ -e
> > excuse me. I want to say that I compiled lyx without
> any debug mode.
> > When I writing quickly, I get Lyx frozen like
> Stefano. I can press F2 key and save my work.
>
> If you can press F2 and save your work then LyX is not
> frozen, it's just that it lost the editing focus. This
>
On Saturday 21 February 2009 09:46:36 rgheck wrote:
> Stefano Franchi wrote:
> > So what's the best way to have both a debug-enabled and a
> > plain vanilla lyx installed?
>
> Don't install the debug version. You can run it from where you compiled
>
> it. I just use a little script:
> >
Stefano Franchi wrote:
On Saturday 21 February 2009 09:46:36 rgheck wrote:
Stefano Franchi wrote:
So what's the best way to have both a debug-enabled and a
plain vanilla lyx installed?
Don't install the debug version. You can run it from where you compiled
it. I just use a
On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:
> > Stefano seems to be using a debug build. In this build mode
> > an assertion causes a crash each time. With a release build
> > assertions are "softer" and, most of the time, the
> > only visible effect is a message on the console or
On 21/02/2009 17:49, Stefano Franchi wrote:
On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:
Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are "softer" and, most of the time, the
only visible effect
On Tuesday 17 February 2009 03:42:42 Abdelrazak Younes wrote:
Stefano Franchi wrote:
When I quit the application with CTRL-Q, I found this:
GuiClipboard.cpp(418): Qt Clipboard changed. We found the following mime
types:
GuiClipboard.cpp(373): We found 0 formats
okular(10266)/kio
I am attaching a backtrace below:
Could you tell me which version or revision you used for generating the
backtrace ?
Vincent
On Friday 20 February 2009 14:54:37 you wrote:
I am attaching a backtrace below:
Could you tell me which version or revision you used for generating the
backtrace ?
Vincent
If you mean which version of Lyx, I used 1.6.1 compiled from source with ---
debug-enable and run within gdb
S.
Stefano Franchi schreef:
On Friday 20 February 2009 14:54:37 you wrote:
I am attaching a backtrace below:
Could you tell me which version or revision you used for generating the
backtrace ?
Vincent
If you mean which version of Lyx, I used 1.6.1 compiled from source
with
On Friday 20 February 2009 16:36:13 Vincent van Ravesteijn wrote:
Stefano Franchi schreef:
On Friday 20 February 2009 14:54:37 you wrote:
I am attaching a backtrace below:
Could you tell me which version or revision you used for generating the
backtrace ?
Vincent
If you
So, right, I was right clicking on a comment inset that contained a
footnote when the crash happened.
I reopened the file, did it again and it crashed again.
Good.
What's worse, from that point on I could no longer reproduce the crash
on the original file.
Very frustrating.
I
Before releasing 1.6.0 there were a number of bugs which depended on
the location of the cursor at the time of right-clicking. Maybe this
helps you ..
I mean, there happen strange things if you right-click on a certain
inset A.. keep the mouse down and then release it at another inset
Vincent van Ravesteijn schreef:
Before releasing 1.6.0 there were a number of bugs which depended on
the location of the cursor at the time of right-clicking. Maybe this
helps you ..
I mean, there happen strange things if you right-click on a certain
inset A.. keep the mouse down and
On Friday 20 February 2009 17:49:35 Vincent van Ravesteijn wrote:
Vincent van Ravesteijn schreef:
Before releasing 1.6.0 there were a number of bugs which depended on
the location of the cursor at the time of right-clicking. Maybe this
helps you ..
I mean, there happen strange
On Tuesday 17 February 2009 03:42:42 Abdelrazak Younes wrote:
Stefano Franchi wrote:
When I quit the application with CTRL-Q, I found this:
GuiClipboard.cpp(418): Qt Clipboard changed. We found the following mime
types:
GuiClipboard.cpp(373): We found 0 formats
okular(10266)/kio
I am attaching a backtrace below:
Could you tell me which version or revision you used for generating the
backtrace ?
Vincent
On Friday 20 February 2009 14:54:37 you wrote:
I am attaching a backtrace below:
Could you tell me which version or revision you used for generating the
backtrace ?
Vincent
If you mean which version of Lyx, I used 1.6.1 compiled from source with ---
debug-enable and run within gdb
S.
Stefano Franchi schreef:
On Friday 20 February 2009 14:54:37 you wrote:
I am attaching a backtrace below:
Could you tell me which version or revision you used for generating the
backtrace ?
Vincent
If you mean which version of Lyx, I used 1.6.1 compiled from source
with
On Friday 20 February 2009 16:36:13 Vincent van Ravesteijn wrote:
Stefano Franchi schreef:
On Friday 20 February 2009 14:54:37 you wrote:
I am attaching a backtrace below:
Could you tell me which version or revision you used for generating the
backtrace ?
Vincent
If you
So, right, I was right clicking on a comment inset that contained a
footnote when the crash happened.
I reopened the file, did it again and it crashed again.
Good.
What's worse, from that point on I could no longer reproduce the crash
on the original file.
Very frustrating.
I
Before releasing 1.6.0 there were a number of bugs which depended on
the location of the cursor at the time of right-clicking. Maybe this
helps you ..
I mean, there happen strange things if you right-click on a certain
inset A.. keep the mouse down and then release it at another inset
Vincent van Ravesteijn schreef:
Before releasing 1.6.0 there were a number of bugs which depended on
the location of the cursor at the time of right-clicking. Maybe this
helps you ..
I mean, there happen strange things if you right-click on a certain
inset A.. keep the mouse down and
On Friday 20 February 2009 17:49:35 Vincent van Ravesteijn wrote:
Vincent van Ravesteijn schreef:
Before releasing 1.6.0 there were a number of bugs which depended on
the location of the cursor at the time of right-clicking. Maybe this
helps you ..
I mean, there happen strange
On Tuesday 17 February 2009 03:42:42 Abdelrazak Younes wrote:
> Stefano Franchi wrote:
> > When I quit the application with CTRL-Q, I found this:
> >
> > GuiClipboard.cpp(418): Qt Clipboard changed. We found the following mime
> > types:
> > GuiClipboard.cpp(373): We found 0 formats
> >
I am attaching a backtrace below:
Could you tell me which version or revision you used for generating the
backtrace ?
Vincent
On Friday 20 February 2009 14:54:37 you wrote:
> > I am attaching a backtrace below:
>
> Could you tell me which version or revision you used for generating the
> backtrace ?
>
> Vincent
If you mean which version of Lyx, I used 1.6.1 compiled from source with ---
debug-enable and run within gdb
Stefano Franchi schreef:
On Friday 20 February 2009 14:54:37 you wrote:
> > I am attaching a backtrace below:
>
> Could you tell me which version or revision you used for generating the
> backtrace ?
>
> Vincent
If you mean which version of Lyx, I used 1.6.1 compiled from source
with
On Friday 20 February 2009 16:36:13 Vincent van Ravesteijn wrote:
> Stefano Franchi schreef:
> > On Friday 20 February 2009 14:54:37 you wrote:
> > > > I am attaching a backtrace below:
> > >
> > > Could you tell me which version or revision you used for generating the
> > > backtrace ?
> > >
> >
So, right, I was right clicking on a comment inset that contained a
footnote when the crash happened.
I reopened the file, did it again and it crashed again.
Good.
What's worse, from that point on I could no longer reproduce the crash
on the original file.
Very frustrating.
I
Before releasing 1.6.0 there were a number of bugs which depended on
the location of the cursor at the time of right-clicking. Maybe this
helps you ..
I mean, there happen strange things if you right-click on a certain
inset A.. keep the mouse down and then release it at another inset
Vincent van Ravesteijn schreef:
Before releasing 1.6.0 there were a number of bugs which depended on
the location of the cursor at the time of right-clicking. Maybe this
helps you ..
I mean, there happen strange things if you right-click on a certain
inset A.. keep the mouse down and
On Friday 20 February 2009 17:49:35 Vincent van Ravesteijn wrote:
> Vincent van Ravesteijn schreef:
> >> Before releasing 1.6.0 there were a number of bugs which depended on
> >> the location of the cursor at the time of right-clicking. Maybe this
> >> helps you ..
> >
> > I mean, there happen
Stefano Franchi wrote:
When I quit the application with CTRL-Q, I found this:
GuiClipboard.cpp(418): Qt Clipboard changed. We found the following mime
types:
GuiClipboard.cpp(373): We found 0 formats
okular(10266)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added Dir /tmp for
Stefano Franchi wrote:
When I quit the application with CTRL-Q, I found this:
GuiClipboard.cpp(418): Qt Clipboard changed. We found the following mime
types:
GuiClipboard.cpp(373): We found 0 formats
okular(10266)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added Dir /tmp for
Stefano Franchi wrote:
When I quit the application with CTRL-Q, I found this:
GuiClipboard.cpp(418): Qt Clipboard changed. We found the following mime
types:
GuiClipboard.cpp(373): We found 0 formats
okular(10266)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added Dir "/tmp" for
On Sunday 01 February 2009 21:25:26 Stefano Franchi wrote:
On Sunday 01 February 2009 17:01:14 Andre Poenitz wrote:
On Sun, Feb 01, 2009 at 11:56:17AM -0600, Stefano Franchi wrote:
Hi All,
I have been experiencing some serious problems with LyX lately, after
my upgrade to 1.6.x.
On Sunday 01 February 2009 21:25:26 Stefano Franchi wrote:
On Sunday 01 February 2009 17:01:14 Andre Poenitz wrote:
On Sun, Feb 01, 2009 at 11:56:17AM -0600, Stefano Franchi wrote:
Hi All,
I have been experiencing some serious problems with LyX lately, after
my upgrade to 1.6.x.
On Sunday 01 February 2009 21:25:26 Stefano Franchi wrote:
> On Sunday 01 February 2009 17:01:14 Andre Poenitz wrote:
> > On Sun, Feb 01, 2009 at 11:56:17AM -0600, Stefano Franchi wrote:
> > > Hi All,
> > >
> > > I have been experiencing some serious problems with LyX lately, after
> > > my
Hi All,
I have been experiencing some serious problems with LyX lately, after my
upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu on the screen any
longer.
2. However, LyX is not completely crashed. I can still issue control
commands. In
Stefano Franchi wrote:
Hi All,
I have been experiencing some serious problems with LyX lately, after my
upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu on the screen any
longer.
2. However, LyX is not completely crashed. I can still
On Sunday 01 February 2009 14:49:30 rgheck wrote:
Stefano Franchi wrote:
Hi All,
I have been experiencing some serious problems with LyX lately, after my
upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu on the screen
any longer.
This sounds like bug 5501:
http://bugzilla.lyx.org/show_bug.cgi?id=5501
That seems to be caused by X getting confused. (perhaps it's related to
a qt bug?) lyx seems to operate normally (no cpu thrashing), but as you
say there is nothing being written to the window.
Cameron.
Stefano Franchi
On Sun, Feb 01, 2009 at 11:56:17AM -0600, Stefano Franchi wrote:
Hi All,
I have been experiencing some serious problems with LyX lately, after
my upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu on the
screen any longer. 2. However, LyX
Hi All,
I have been experiencing some serious problems with LyX
lately, after my
upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu
on the screen any
longer.
2. However, LyX is not completely crashed. I can still
issue control
On Sunday 01 February 2009 17:01:14 Andre Poenitz wrote:
On Sun, Feb 01, 2009 at 11:56:17AM -0600, Stefano Franchi wrote:
Hi All,
I have been experiencing some serious problems with LyX lately, after
my upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly
On Sunday 01 February 2009 16:36:08 Cameron Stone wrote:
This sounds like bug 5501:
http://bugzilla.lyx.org/show_bug.cgi?id=5501
That seems to be caused by X getting confused. (perhaps it's related to
a qt bug?) lyx seems to operate normally (no cpu thrashing), but as you
say there is
Hi All,
I have been experiencing some serious problems with LyX lately, after my
upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu on the screen any
longer.
2. However, LyX is not completely crashed. I can still issue control
commands. In
Stefano Franchi wrote:
Hi All,
I have been experiencing some serious problems with LyX lately, after my
upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu on the screen any
longer.
2. However, LyX is not completely crashed. I can still
On Sunday 01 February 2009 14:49:30 rgheck wrote:
Stefano Franchi wrote:
Hi All,
I have been experiencing some serious problems with LyX lately, after my
upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu on the screen
any longer.
This sounds like bug 5501:
http://bugzilla.lyx.org/show_bug.cgi?id=5501
That seems to be caused by X getting confused. (perhaps it's related to
a qt bug?) lyx seems to operate normally (no cpu thrashing), but as you
say there is nothing being written to the window.
Cameron.
Stefano Franchi
On Sun, Feb 01, 2009 at 11:56:17AM -0600, Stefano Franchi wrote:
Hi All,
I have been experiencing some serious problems with LyX lately, after
my upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu on the
screen any longer. 2. However, LyX
Hi All,
I have been experiencing some serious problems with LyX
lately, after my
upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu
on the screen any
longer.
2. However, LyX is not completely crashed. I can still
issue control
On Sunday 01 February 2009 17:01:14 Andre Poenitz wrote:
On Sun, Feb 01, 2009 at 11:56:17AM -0600, Stefano Franchi wrote:
Hi All,
I have been experiencing some serious problems with LyX lately, after
my upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly
On Sunday 01 February 2009 16:36:08 Cameron Stone wrote:
This sounds like bug 5501:
http://bugzilla.lyx.org/show_bug.cgi?id=5501
That seems to be caused by X getting confused. (perhaps it's related to
a qt bug?) lyx seems to operate normally (no cpu thrashing), but as you
say there is
Hi All,
I have been experiencing some serious problems with LyX lately, after my
upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu on the screen any
longer.
2. However, LyX is not completely crashed. I can still issue control
commands. In
Stefano Franchi wrote:
Hi All,
I have been experiencing some serious problems with LyX lately, after my
upgrade to 1.6.x. This is what happens:
1. I am happily typing away when suddenly there is no ouptu on the screen any
longer.
2. However, LyX is not completely crashed. I can still
On Sunday 01 February 2009 14:49:30 rgheck wrote:
> Stefano Franchi wrote:
> > Hi All,
> >
> > I have been experiencing some serious problems with LyX lately, after my
> > upgrade to 1.6.x. This is what happens:
> >
> > 1. I am happily typing away when suddenly there is no ouptu on the screen
> >
This sounds like bug 5501:
http://bugzilla.lyx.org/show_bug.cgi?id=5501
That seems to be caused by X getting confused. (perhaps it's related to
a qt bug?) lyx seems to operate normally (no cpu thrashing), but as you
say there is nothing being written to the window.
Cameron.
Stefano Franchi
On Sun, Feb 01, 2009 at 11:56:17AM -0600, Stefano Franchi wrote:
> Hi All,
>
> I have been experiencing some serious problems with LyX lately, after
> my upgrade to 1.6.x. This is what happens:
>
> 1. I am happily typing away when suddenly there is no ouptu on the
> screen any longer. 2.
> Hi All,
>
> I have been experiencing some serious problems with LyX
> lately, after my
> upgrade to 1.6.x. This is what happens:
>
> 1. I am happily typing away when suddenly there is no ouptu
> on the screen any
> longer.
> 2. However, LyX is not completely crashed. I can still
> issue
1 - 100 of 102 matches
Mail list logo