Which graphics driver are you using?

Qt3 has a bug that is manifesting in certain graphics drivers with exactly the same symptoms as you describe.

(In reply to comment #1)
> Which graphics driver are you using?
> 
> Qt3 has a bug that is manifesting in certain graphics drivers with exactly the
> same symptoms as you describe.

Problem does not exist in Debian Lenny w/ nvidia-kernel-2.6.26-2-686
version 173.14.09+3+lenny1.

Problem exists in Debian Squeeze Trinity w/ nvidia-kernel-dkms
version, 195.36.31-6.

Problem also existed in the non-dkms nvidia driver which I was
using in Squeeze until two days ago, which I believe was
nvidia-kernel-2.6.32-5-686 version 95.36.31+2+4+2.6.32-24.

Both the nVidia and ATI binary drivers seem to exhibit this problem.  The Intel drivers, among others, do not.

(In reply to comment #3)
> Both the nVidia and ATI binary drivers seem to exhibit this problem.  The Intel
> drivers, among others, do not.

There's not a lot of difference between the libqt3-mt in Lenny (3:3.3.8b-5+b1) and in Squeeze (3:3.3.8b-7+b1).

Would you happen to have the Nokia bug number handy or any other kind of pointer to it?  I can't find it at http://bugreports.qt.nokia.com/

Thanks!

(In reply to comment #4)
> (In reply to comment #3)
> > Both the nVidia and ATI binary drivers seem to exhibit this problem.  The Intel
> > drivers, among others, do not.
> 
> There's not a lot of difference between the libqt3-mt in Lenny (3:3.3.8b-5+b1)
> and in Squeeze (3:3.3.8b-7+b1).
> 
> Would you happen to have the Nokia bug number handy or any other kind of
> pointer to it?  I can't find it at http://bugreports.qt.nokia.com/
> 
> Thanks!

It's not there as no one has reported it to Nokia.  I believe it to be a
regression within the proprietary drivers themselves, not Qt3.  

This is just something I have noticed over time with both my systems and
those of other users, especially in tree view widgets; if you can, try switching temporarily to a VESA or other non-accelerated (both 2D and 3D) driver to see if the bug goes away.

If you would like to file a bug at Nokia you may certainly do so, but I am pretty sure they will mark it invalid as Qt3 is no longer developed.

Tim

Problem just occurred with VESA driver.  I think it happened this time when I switched desktops and then back to KMail while it was updating the tree view.

# lsmod | grep -i nvi
# grep -i driver /var/log/Xorg.0.log
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
        X.Org Video Driver: 6.0
        X.Org XInput driver : 7.0
(II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 6.0
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 7.0
(II) VESA: driver for VESA chipsets: vesa
        ABI class: X.Org Video Driver, version 6.0
        ABI class: X.Org Video Driver, version 6.0
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
(II) Synaptics touchpad driver version 1.2.2
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 7.0
(II) No input driver/identifier specified (ignoring)
(II) No input driver/identifier specified (ignoring)
(II) No input driver/identifier specified (ignoring)
(II) Synaptics touchpad driver version 1.2.2
(II) Synaptics touchpad driver version 1.2.2
(II) No input driver/identifier specified (ignoring)
(II) No input driver/identifier specified (ignoring)

Sometimes I also observe this behavior - in connection with this I always see in .xsession-errors:

QGArray::at: Absolute index _number_ out of range