[gm45] Okular with intel graphics driver does not draw view in page thumbnail

[David Benjamin]

Binary package hint: xserver-xorg-video-intel

Okular using default (hardware-backed) graphics engine does not draw the grey box in the thumbnail panel that shows where the current view is.

Running okular -graphicssystem raster causes it to display properly, so this isn't a problem with Okular telling Qt to draw the box. Downloading the Qt 4.6 RC and using LD_LIBRARY_PATH to force that shared library likewise does not cause a problem, so it is unlikely this is a bug in Qt or Ubuntu's package of it. That leaves a regression in the intel driver.

The version of xserver-xorg-video-intel on my machine is 2.9.0-1ubuntu2, arch amd64.

My graphics card is

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
        Subsystem: Lenovo Device [17aa:20e4]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 30
        Region 0: Memory at f4400000 (64-bit, non-prefetchable) [size=4M]
        Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at 1800 [size=8]
        Capabilities: <access denied>
        Kernel driver in use: i915
        Kernel modules: i915

00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07)
        Subsystem: Lenovo Device [17aa:20e4]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Region 0: Memory at f4200000 (64-bit, non-prefetchable) [size=1M]
        Capabilities: <access denied>

This is a Lenovo Thinkpad T400.

[David Benjamin (davidben)]

Taken with okular -graphicssystem raster

[David Benjamin (davidben)]

Taken with default arguments

[David Benjamin (davidben)]

This also occurs with ksnapshot's region capture mode feature. As both these involve transparent overlays of things, I imagine this is in fact the same bug.

Steps to reproduce for ksnapshot:
1. Run ksnapshot
2. Set Capture Mode to Region
3. Press New Snapshot
4. Drag some region of the screen

Expected: Screen gets slightly darker with the region in question left undarkened and a little resize widget on the border.

This, also, works properly (with some flicker) without hardware acceleration (ksnapshot -graphicssystem raster)

[Miguel (muchochini)]

This happens to me also. I am using Ubuntu Karmic 9.10 with Intel graphics video card. Ksnapshot doesn't draw region capture in light blue.

[Miguel (muchochini)]

Adding some more useful information. My graphic card:

00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
 Subsystem: Dell Device 024f
 Flags: bus master, fast devsel, latency 0, IRQ 30
 Memory at f6c00000 (64-bit, non-prefetchable) [size=4M]
 Memory at e0000000 (64-bit, prefetchable) [size=256M]
 I/O ports at ef98 [size=8]
 Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
 Capabilities: [d0] Power Management version 3
 Kernel driver in use: i915
 Kernel modules: i915

Version of xserver-xorg-video-intel:
               2:2.9.0-1ubuntu2 X.Org X server -- Intel i8xx, i9xx display driver

Using Ubuntu Karmic 9.10 64 bits.

I can reproduce both bugs: okular and ksnapshot.

[Vikram Dhillon (dhillon-v10)]

This issue was reported against karmic, so can you confirm if this issue exists with the most recent Lucid Lynx 10.04 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/lucid/ . Thanks in advance.

[David Benjamin (davidben)]

I have not tested against Lucid, but the issue appears fixed when running with a custom compiled 2.6.32.8 kernel (was seeing if newer kernel fixed broken wireless problems).

[Vikram Dhillon (dhillon-v10)]

@David: I'd say from the link I gave above, get a live-cd and check if the problem still exists, we can't really fix customized kernel based problems here, so if you could check if the problem exists in lucid alpha, we can fix it in the Ubuntu kernel :) Thanks in advance.

[David Benjamin (davidben)]

I believe you misunderstand me. The problem *did* occur in the stock Ubuntu Karmic kernel. For unrelated reasons, I compiled a vanilla 2.6.32.8 kernel to test other things and noticed that it was *fixed* in 2.6.32.8. As such, assuming Lucid ships a sufficiently new kernel from the 2.6.32 and assuming Ubuntu does not reintroduce the bug with a patch, the bug should be fixed in Lucid. I will verify this later when I have time.

[Vikram Dhillon (dhillon-v10)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/24/2010 10:56 PM, David Benjamin wrote:
> I believe you misunderstand me. The problem *did* occur in the stock
> Ubuntu Karmic kernel. For unrelated reasons, I compiled a vanilla
> 2.6.32.8 kernel to test other things and noticed that it was *fixed* in
> 2.6.32.8. As such, assuming Lucid ships a sufficiently new kernel from
> the 2.6.32 and assuming Ubuntu does not reintroduce the bug with a
> patch, the bug should be fixed in Lucid. I will verify this later when I
> have time.
>

Apologies David :) I see what you are saying, adding a lucid tag because
this problem might show up in lucid release.

 status new

 tag lucid

- --
Regards,
Vikram Dhillon

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuItZAACgkQcoBavQdRHcwc1wCgnxtYtlZZviTC5HSSxbYITunQ
JXAAnAgqRdCqqPaV6eCrgh62rv5S2DJX
=flNk
-----END PGP SIGNATURE-----

[Bryce Harrington (bryce)]

Since it was tested against a .32 kernel and found fixed, and we have no indications that it is not fixed, we'll close the bug at this point. You can always re-open it (or file a new one) if it proves to still exist.