Aspect ratio issue under Ubuntu 10.10 Netbook Edition (kernel 2.6.35)

[Fabrício Puppi]

Binary package hint: xorg

As in Question #130683:

"Upon updating my Ubuntu Netbook Edition to 10.10, when logging in under kernel vesion 2.6.35 the aspect ratio is displayed incorrectly on the screen. The ratio should be 4:3, and under System>Preferences>Monitors it is the selected option (and the only ratio available for my netbook), however the width of the display effectively shown is shortened, with black vertical bars at both sides (the display is centralized, at least).
When logging in under kernel 2.6.32 everything works fine, and I have no issue whatsoever on my desktop PC (running Ubuntu 10.10 desktop edition under kernel 2.6.35).

My netbook is Samsung's NC10, and its graphic card is Mobile 945GME Express Integrated Grahics Controller."

As additional information:
The issue is xsession independent, and is presented as soon as GDM starts, up from the login screen.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1024x600
 edid-base64: AP///////wAOFMQEAAAAAAQUAQOAFw54ClB1klhWkicfUFQAAAABAQEBAQEBAQEBAQEBAQEBlBEAsEBYGSAwIDYA3oIAAAAZAAAADwAAAAAAAAAAACBuBQ8AAAAA/gBDUFQgICAgICAgICAgAAAA/gBDTEFBMTAyTkEwQSAgAGs=
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1024x768 800x600 800x600 848x480 640x480
 edid-base64:
Date: Fri Oct 22 10:52:29 2010
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=ca63d666-ba3b-4107-976b-f6a980006d00 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 09/08/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 11CA.M015.20090908.RHU
dmi.board.name: NC10
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr11CA.M015.20090908.RHU:bd09/08/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: NC10
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic

[bugbot (bugbot)]

Hey Fabrício,

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.

[Fabrício Puppi (puppi)]

The bug still persisted, so I was still using kernel 2.6.32 (while keeping an updated image along, checking if the problem had been fixed whenever there was a kernel or X update). But the netbook has not been in my possession for about 2 months, and I'm not sure when I'll have it back. When I do, if the issue persists, I'll report it again. I won't trouble you with something that I can't surely say hasn't been fixed in the latest patches or in the distro upgrade.