Wolfgang Engelmann wrote:
Is this type of error known and cured in the new Lyx version?
might be related to http://www.lyx.org/trac/ticket/5501
pavel
Am Tuesday 30 March 2010 14:12:32 schrieb Pavel Sanda:
Wolfgang Engelmann wrote:
Is this type of error known and cured in the new Lyx version?
might be related to http://www.lyx.org/trac/ticket/5501
pavel
Hi, Pavel,
yes, I think I have the same problem as described there. Is it useful to
Wolfgang Engelmann wrote:
Is it useful to collect more data? And were do I report it?
add it to that bug in case you have something interesting.
Let me know whether I should watch this more carefully and to what I should
pay attention to.
two things are interesting in particular:
1.
Wolfgang Engelmann wrote:
Is this type of error known and cured in the new Lyx version?
might be related to http://www.lyx.org/trac/ticket/5501
pavel
Am Tuesday 30 March 2010 14:12:32 schrieb Pavel Sanda:
Wolfgang Engelmann wrote:
Is this type of error known and cured in the new Lyx version?
might be related to http://www.lyx.org/trac/ticket/5501
pavel
Hi, Pavel,
yes, I think I have the same problem as described there. Is it useful to
Wolfgang Engelmann wrote:
Is it useful to collect more data? And were do I report it?
add it to that bug in case you have something interesting.
Let me know whether I should watch this more carefully and to what I should
pay attention to.
two things are interesting in particular:
1.
Wolfgang Engelmann wrote:
> Is this type of error known and cured in the new Lyx version?
might be related to http://www.lyx.org/trac/ticket/5501
pavel
Am Tuesday 30 March 2010 14:12:32 schrieb Pavel Sanda:
> Wolfgang Engelmann wrote:
> > Is this type of error known and cured in the new Lyx version?
>
> might be related to http://www.lyx.org/trac/ticket/5501
>
> pavel
Hi, Pavel,
yes, I think I have the same problem as described there. Is it
Wolfgang Engelmann wrote:
> Is it useful to collect more data? And were do I report it?
add it to that bug in case you have something interesting.
> Let me know whether I should watch this more carefully and to what I should
> pay attention to.
two things are interesting in particular:
1.
started
lyx)
X Error: BadGC (invalid GC parameter) 13
Major opcode: 56 (X_ChangeGC)
Resource id: 0x460319f
I have to kill the job and start anew. The changes were saved, fortunately.
It has probably to do with QT, since I found In the Internet:
The first line means that the error was of type
started
lyx)
X Error: BadGC (invalid GC parameter) 13
Major opcode: 56 (X_ChangeGC)
Resource id: 0x460319f
I have to kill the job and start anew. The changes were saved, fortunately.
It has probably to do with QT, since I found In the Internet:
The first line means that the error was of type
started
lyx)
X Error: BadGC (invalid GC parameter) 13
Major opcode: 56 (X_ChangeGC)
Resource id: 0x460319f
I have to kill the job and start anew. The changes were saved, fortunately.
It has probably to do with QT, since I found In the Internet:
The first line means that the error was of type
12 matches
Mail list logo
