Ubuntu

about ubuntu incorrect version number

Bug #692314 reported by dennygoot@gmail.com on 2010-12-19

This bug report is a duplicate of: Bug #690248: In Maverick 'About Ubuntu' displays Natty info. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu	New	Undecided	Unassigned

Bug Description

on my ubuntu 10.10 netbook version, clicking on about ununtu under the system menu reports this:

Ubuntu - Linux for Human Beings!

You are using Ubuntu 11.04
- the Natty Narwhal - released in April 2011 and supported until October 2012.

but lsb_release -a reports this:

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.10
Release: 10.10
Codename: maverick

this is not a bug, but i was uncertain where else this should be posted, since if anything it's a jump of the gun, i think.

unless about ubuntu somehow reports it's information based on system info.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic i686
Architecture: i386
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1024x600
edid-base64: AP///////wAGr9IwAAAAAAESAQOAFg14CrmllllXkSgfUFQAAAABAQEBAQEBAQEBAQEBAQEBUBQAQEFYLCAYiDEA330AAAAYAAAADwAAAAAAAAAAAAAAAAAgAAAA/gBBVU8KICAgICAgICAgAAAA/gBCMTAxQVcwMyBWMCAKADw=
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: On
modes:
edid-base64:
Date: Sun Dec 19 13:40:25 2010
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Acer AO531h
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=7a012604-3f19-4bc2-a169-b3ba6c25a1ba ro quiet splash
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 08/25/2009
dmi.bios.vendor: Acer
dmi.bios.version: v0.3206
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrv0.3206:bd08/25/2009:svnAcer:pnAO531h:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AO531h
dmi.product.version: 1
dmi.sys.vendor: Acer
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-23-generic

Tags:

Revision history for this message

dennygoot@gmail.com (dennygoot) wrote on 2010-12-19:

BootDmesg.txt Edit (48.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (5.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (16.3 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (16.4 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (18.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (10.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (447 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (1.9 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (246 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (96.8 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (215.8 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (24.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (25.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (1.9 KiB, text/plain; charset="utf-8")
peripherals.txt Edit (1.5 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (9.7 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (54.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2010-12-20:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #690248, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.