Hi,
I’ve noticed a bug when I run X application (based on Qt-2.2.3)
using the SMP kernel on a dual CPU system. It works OK with the
uniprocessor kernel.
Many standard Qt widgets such as buttons, toolbars, etc. don’t
get repainted properly. E.g. the toolbar in the Qt-designer is
totally messed up. Moving another window over it will sometimes
correctly repaint the messed up widgets.
I have reported the bug to Trolltech also but from my standpoint,
I can not tell if it’s a Qt or Xphoton bug. I use QNX RTP public
beta version. Has anyone else noticed similar bugs?
Mats
In article <9345o0$slm$1@inn.qnx.com>,
Mats Byggmastar <mats.byggmastar@mulfi.NOJUNK.fi> wrote:
Hi,
I’ve noticed a bug when I run X application (based on Qt-2.2.3)
using the SMP kernel on a dual CPU system. It works OK with the
uniprocessor kernel.
Many standard Qt widgets such as buttons, toolbars, etc. don’t
get repainted properly. E.g. the toolbar in the Qt-designer is
totally messed up. Moving another window over it will sometimes
correctly repaint the messed up widgets.
I have reported the bug to Trolltech also but from my standpoint,
I can not tell if it’s a Qt or Xphoton bug. I use QNX RTP public
beta version. Has anyone else noticed similar bugs?
Try running Xphoton with -noshmem on the commandline and
let me know if it fixes it.
My guess is that it’s a synchronization problem with the
grafx driver. Xphoton thinks the driver has rendered
something from shared memory, and reuses it before it
gets on the screen.
Sounds like an Xphoton bug (and maybe justification for
me to get a dual on my desk 
–
Garry Turcotte (R&D)
QNX Software Systems, Ltd.
I’ve noticed a bug when I run X application (based on Qt-2.2.3)
using the SMP kernel on a dual CPU system. It works OK with the
uniprocessor kernel.
Many standard Qt widgets such as buttons, toolbars, etc. don’t
get repainted properly. E.g. the toolbar in the Qt-designer is
totally messed up. Moving another window over it will sometimes
correctly repaint the messed up widgets.
Try running Xphoton with -noshmem on the commandline and
let me know if it fixes it.
Yes, the problem goes away with -noshmem, and comes back when
restarting Xphoton without it.
My guess is that it’s a synchronization problem with the
grafx driver. Xphoton thinks the driver has rendered
something from shared memory, and reuses it before it
gets on the screen.
OK.
If it is of any help, my system consist of a Soltek dual
intel 440BX motherboard, 2 x P-III 600 MHz, Creative GeForce2 MX.
Mats