Discussion:
severe problem with shaded boxes
(too old to reply)
Jürgen Spitzmüller
2011-03-19 07:46:08 UTC
Permalink
I still can't reproduce it here, unfortunately, or I'd try to help. I
set the French locale, created a document with a shaded box, changed the
color of the box, and applied, but nothing bad happened. Any other advice?
No, that's a safe way for me to get it (if I run an installed binary, that
is).

I also get it if I insert an note inset and change a color in preferences (so
it's no genuine problem of the document dialog).

Jürgen
Jürgen Spitzmüller
2011-03-19 07:49:18 UTC
Permalink
No. I was unable to reproduce the problem (as Pavel, with the same qt
version 4.6.3). The strange thing is that the background colors are only
used for LaTeX output, so changing them should not influence any GUI color
(actually it should, but it is not implemented. Uwe reported a bug about
this, but I can't find it right now).
I browsed a bit through the code, but did not find anything obvious
(besides an unrelated bug with a color reset button).
Thanks for fixing this. My bad.
The attached patch
is a shot in the dark.
Unfortunately, it does not help.
1) Maybe your qt does not like the invalid QPalette::ColorRole value -1?
2) The GuiDocument uses some static variables. Maybe they get corrupted by
some other memory error? If yes, then the second part of the patch should
make a difference.
I also notice a lot of uninitialised value warnings for
QTransform::fromTranslate() in your valgrind log. When I run with valgrind
I get only two of these warnings, both times in libz when loading an
image. Which qt version do you use? Maybe that qt code gives a hint.
Qt 4.7.2.

Jürgen
José Matos
2011-03-19 09:23:33 UTC
Permalink
Post by Jürgen Spitzmüller
Qt 4.7.2.
Jürgen
FWIW that is also the version I have used in my tests.
--
José Abílio
Jürgen Spitzmüller
2011-03-19 09:33:35 UTC
Permalink
Post by José Matos
Post by Jürgen Spitzmüller
Qt 4.7.2.
Jürgen
FWIW that is also the version I have used in my tests.
It might explain why this bug shows up only now (also in branch).

Jürgen
Stephan Witt
2011-03-19 09:53:46 UTC
Permalink
Post by Jürgen Spitzmüller
Post by José Matos
Post by Jürgen Spitzmüller
Qt 4.7.2.
Jürgen
FWIW that is also the version I have used in my tests.
It might explain why this bug shows up only now (also in branch).
This and the fact it has the potential to crash your X-Server might be
an indication for bad interaction between Qt and Xlib. For sure it might
triggered by some odd calls from LyX - but nevertheless this shouldn't happen.
The amount of valgrind errors in the log points in that direction too.

Stephan
Richard Heck
2011-03-19 12:59:29 UTC
Permalink
Post by Jürgen Spitzmüller
Post by José Matos
Post by Jürgen Spitzmüller
Qt 4.7.2.
Jürgen
FWIW that is also the version I have used in my tests.
It might explain why this bug shows up only now (also in branch).
FWIW, I'm using 4.7.1, and can't reproduce.

rh
Jürgen Spitzmüller
2011-03-19 13:18:01 UTC
Permalink
Post by Richard Heck
Post by Jürgen Spitzmüller
Post by José Matos
FWIW that is also the version I have used in my tests.
It might explain why this bug shows up only now (also in branch).
FWIW, I'm using 4.7.1, and can't reproduce.
Do you have the possibility to check with 4.7.2 as well?

Jürgen
Stephan Witt
2011-03-20 11:48:12 UTC
Permalink
Post by Jürgen Spitzmüller
Post by Richard Heck
Post by Jürgen Spitzmüller
Post by José Matos
FWIW that is also the version I have used in my tests.
It might explain why this bug shows up only now (also in branch).
FWIW, I'm using 4.7.1, and can't reproduce.
Do you have the possibility to check with 4.7.2 as well?
Now I've built the 4.7.2 frameworks and produced a bundled app for mac os x with it.
If I start it the interface is german and I cannot reproduce the problem.
But I have no X11 lib - I'm using Carbon interface. Cocoa I haven't tried until now.

Stephan
Georg Baum
2011-03-20 16:26:45 UTC
Permalink
Post by Jürgen Spitzmüller
The attached patch
is a shot in the dark.
Unfortunately, it does not help.
I suspected that, but there was a tiny chance...
Post by Jürgen Spitzmüller
I also notice a lot of uninitialised value warnings for
QTransform::fromTranslate() in your valgrind log. When I run with valgrind
I get only two of these warnings, both times in libz when loading an
image. Which qt version do you use? Maybe that qt code gives a hint.
Qt 4.7.2.
I tried to reproduce the problem with a self compiled Qt 4.7.2, but it still
works fine, and the valgrind report shows only some erors like the attached.
I don't believe that they are related, but one never knows.

Can you rerun valgrind with

--track-origins=yes

? That should give us a hint where the initialization is missing in your
case.


Georg

Pavel Sanda
2011-03-19 10:53:10 UTC
Permalink
Post by Jürgen Spitzmüller
No, that's a safe way for me to get it (if I run an installed binary, that
is).
I also get it if I insert an note inset and change a color in preferences (so
it's no genuine problem of the document dialog).
maybe another dataloss problem in dialog (#7349) is related to this.

pavel
Loading...