[q35] gnome-terminal slow to start

[Gilles Gagniard]

Binary package hint: xorg

Starting up gnome-terminal is slow (around half a second), even when hot-starting, while it was immediate in 10.04.

I did some strace-ing (logs attached below) and the culprit is a 400ms long read() on the X socket. I file this bug in xorg because it's probably caused by the intel Q35 (GMA3100) driver which is known to be particularly broken in maverick in dual screen setups (missing secondary screen #619663, regular freezes #628556, various graphical corruptions, ...)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic x86_64
Architecture: amd64
DRM.card0.DVI.D.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400
 edid-base64: AP///////wAQrE5ATUg5MRMUAQOALx547u6Vo1RMmSYPUFSlSwBxT4GAswABAQEBAQEBAQEBfC6QoGAaHkAwIDYA2igRAAAaAAAA/wBXNDE2SzA1MzE5SE0KAAAA/ABERUxMIFAyMjEwCiAgAAAA/QA4Sx5TEAAKICAgICAgABA=
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400
 edid-base64: AP///////wAQrExATTFBMRMUAQMKLx547u6Vo1RMmSYPUFSlSwBxT4GAswABAQEBAQEBAQEBITmQMGIaJ0BosDYA2igRAAAcAAAA/wBXNDE2SzA1MzFBMU0KAAAA/ABERUxMIFAyMjEwCiAgAAAA/QA4Sx5TEAAKICAgICAgAJE=
Date: Mon Feb 7 15:43:07 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Hewlett-Packard HP Compaq dc7800 Small Form Factor
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic root=UUID=8c6887da-db4d-4728-9588-2d35a79a9cf5 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 07/18/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786F1 v01.04
dmi.board.asset.tag: CZC82405X5
dmi.board.name: 0AA8h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC82405X5
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr786F1v01.04:bd07/18/2007:svnHewlett-Packard:pnHPCompaqdc7800SmallFormFactor:pvr:rvnHewlett-Packard:rn0AA8h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.name: HP Compaq dc7800 Small Form Factor
dmi.sys.vendor: Hewlett-Packard
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-25-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:2818]

[Gilles Gagniard (gilles-gagniard)]

Interesting lines in strace log :

     0.000130 poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
     0.000062 writev(3, [{"+\0\1\0", 4}, {NULL, 0}, {"", 0}], 3) = 4
     0.000048 poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}])
     0.398729 read(3, "\1\2}\0\0\0\0\0c\3\300\5\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 4096) = 32
     0.000058 read(3, 0xfb47f4, 4096) = -1 EAGAIN (Resource temporarily unavailable)
     0.000057 poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
     0.000036 writev(3, [{"+\0\1\0", 4}, {NULL, 0}, {"", 0}], 3) = 4
     0.000042 poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}])
     0.000061 read(3, "\1\2~\0\0\0\0\0c\3\300\5\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 4096) = 32
     0.000041 read(3, 0xfb47f4, 4096) = -1 EAGAIN (Resource temporarily unavailable)

the first read() is very long ... the #3 fd is the X socket as can be seen above in the log.

[Gilles Gagniard (gilles-gagniard)]

I confirm this is linked to dual screen setup, since when I disable the secondary screen, the issue disappears and gnome-terminal startup time are back to normal. Mirroring mode is also fine ... So this is definitely caused by large framebuffers.

[bugbot (bugbot)]

Hey Gilles,

Thanks for your interest in Ubuntu.

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.