Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
This bug report refers to releases which have been 'end of life'
for many years now. It did not expire due to assignment.
There was no reply to comment #3 made over 11 years ago so closing
this now as being 'Invalid'.
** Changed in: xorg-server (Ubuntu)
Assignee: Tormod Volden (tormodvolden) => (unassigned)
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/669002
Title:
[prosavage8] Only root can start X at a reasonable resolution
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
Binary package hint: xorg
After upgrading from 10.04 to 10.10 on 2010-10-29, I've experienced
the following show-stopper a problem: I'm using gdm. However, upon
entering the correct password at gdm, the screen blinks and the gdm
login screen is built up again.
In order to start investigating the problem, I have booted into
"recovery mode" from the grub menu, then chosen "netroot" in the
Reciovery menu.
If I type 'startx' as root, it works.
If I 'su - nb' first, the type 'startx', the screen goes dark with an
"Input Not Supported" box from the monitor.
The Xorg log file from the case that doesn't work (attached) is very similar
to the case that does work.
The only possibly-significant difference is the final line
[ 2295.773] (--) SAVAGE(0): Chose mode 14f at 85Hz.
which doesn't have an equivalent in the Xorg log file for the case
that works.
I'm using the SAVAGE driver, but the problem is not specific to this driver:
It occurs also when forcing use of the VESA driver.
Through manual xorg.conf configuration it is possible to create a
configuration which allows successfully starting Xorg by running
'startx' as a non-root user, although at an unacceptably low
resolution.
The problem is not specific to Ubuntu: It also occurs with Arch Linux
10.05
I have a fresh install of Ubuntu 10.04 (which does not exhibit the
problem) now which I'm using for reporting this issue. So the
automatically provided information from the 'ubuntu-bug' script should
be referred to only for information on the hardware where the problem
occurs.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
Architecture: i386
Date: Sun Oct 31 08:00:59 2010
DkmsStatus: Error: [Errno 2] No such file or directory
EcryptfsInUse: Yes
GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat',
'/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2:
No such file or directory
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
MachineType: ECS P4VMM2
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-generic
root=UUID=6dc1af4e-b1fb-426b-8b22-ffe1004ddf4e ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=de_CH.utf8
SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 04/02/01
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 07.00T
dmi.board.name: P4VMM2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr07.00T:bd04/02/01:svnECS:pnP4VMM2:pvr1.0:rvnECS:rnP4VMM2:rvr1.0:cvnECS:ct3:cvr1.0:
dmi.product.name: P4VMM2
dmi.product.version: 1.0
dmi.sys.vendor: ECS
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-25-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/669002/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
