22 Sep
2010
22 Sep
'10
10:16 p.m.
I'm seeing a whole bunch of these messages now. The [systemtray] tells me you added
the messages, but the messages don't tell me much.
What area is being cleared and why do users need to know?
Darrell
22 Sep
22 Sep
10:36 p.m.
New subject: [trinity-devel] [systemtray] Clearing area to set background
I'm seeing a whole bunch of these messages now.
The [systemtray] tells me
you added the messages, but the messages don't tell me much.
What area is being cleared and why do users need to know?
Darrell
That is for debug only; are those messages at all linked with the
BadWindow messages? If not they will be removed in the next SVN commit.
Tim
10:59 p.m.
New subject: [trinity-devel] [systemtray] Clearing area to set background
That is for debug only; are those messages at all
linked
with the
BadWindow messages? If not they will be removed in
the next SVN commit.
They appear many times successively and not associated with any BadWindow messages.
They appear only after I log out and exit X.
Perhaps such messages should look something like this:
[systemtray] Debug test: Clearing area to set background
As much as I hate those messages, I would vote to place that item at the top of the to-do
list for 3.5.13. I'll submit a priority 1 bug report if you want. Your call.
23 Sep
23 Sep
10:09 a.m.
New subject: [trinity-devel] [systemtray] Clearing area to set background
That is for
debug only; are those messages at all linked
with the
BadWindow messages? If not they will be removed in
the next SVN commit.
They appear many times successively and not associated with any BadWindow
messages.
They appear only after I log out and exit X.
Perhaps such messages should look something like this:
[systemtray] Debug test: Clearing area to set background
As much as I hate those messages, I would vote to place that item at the
top of the to-do list for 3.5.13. I'll submit a priority 1 bug report if
you want. Your call.
10:24 a.m.
New subject: [trinity-devel] [systemtray] Clearing area to set background
The [systemtray] message has been removed. I am
thinking that the
BadWindow errors may actually be caused by Qt, as Trinity
uses XClearArea
very sparingly and you just helped rule out the only
section of code that
could have been causing the repeating BadWindow errors.
I don't pretend to be a developer, but that seems to make sense only from the amount
of those messages seen. As I mentioned previously, I see the messages only with KDE and
not Xfce or window managers. That indicates something peculiar to KDE/Qt.
Qt probably needs patching eventually. At least, that is the opinion of a few people who
questioned whether proceeding with updating 3.5.10 is worthwhile. If patching is required
then sounds like a project for 3.5.13 and not 3.5.12?
7:34 p.m.
New subject: [trinity-devel] [systemtray] Clearing area to set background
The
[systemtray] message has been removed. I am
thinking that the
BadWindow errors may actually be caused by Qt, as Trinity
uses XClearArea
very sparingly and you just helped rule out the only
section of code that
could have been causing the repeating BadWindow errors.
I don't pretend to be a developer, but that seems to make sense only from
the amount of those messages seen. As I mentioned previously, I see the
messages only with KDE and not Xfce or window managers. That indicates
something peculiar to KDE/Qt.
Qt probably needs patching eventually. At least, that is the opinion of a
few people who questioned whether proceeding with updating 3.5.10 is
worthwhile. If patching is required then sounds like a project for 3.5.13
and not 3.5.12?
9:36 p.m.
New subject: [trinity-devel] [systemtray] Clearing area to set background
Definitely. And as far as Qt3 is concerned, if it
isn't broken I probably
won't be fixing it. ;-) Effort would be better spent
getting the TQT
interface up and running to allow Trinity to run under
Qt4...
I understand.
Other than old releases such as Lenny and Slackware 12.2, end-users have to build the
qt-3.38b package. Would be nice to get that one error solved (qt-3.3.8c). :)
5176
days inactive
5177
days old
6 comments
2 participants
participants (2)
-
Darrell Anderson -
Timothy Pearson