Xorg restarted after logging back into the user

[Vadim Peretokin]

Binary package hint: xorg

Re-logged back in as the logged in user, it was loading, then Xorg restarted.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-power+18.24~lucid-generic 2.6.35.3
Uname: Linux 2.6.35-power+18-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.06 Mon Sep 13 04:29:19 PDT 2010
 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: amd64
Date: Sat Oct 30 13:18:44 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1)
MachineType: - N/A
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-power+18-generic root=UUID=806cccc5-0fc1-4114-b9ab-5f01ea5524c4 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.utf8
 SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 09/27/2007
dmi.bios.vendor: COMPAL
dmi.bios.version: 1.13
dmi.board.name: IFL90
dmi.board.vendor: -
dmi.board.version: IFT00
dmi.chassis.asset.tag: -
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnCOMPAL:bvr1.13:bd09/27/2007:svn-:pnN/A:pvrN/A:rvn-:rnIFL90:rvrIFT00:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: N/A
dmi.product.version: N/A
dmi.sys.vendor: -
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-power+18-generic

[bugbot (bugbot)]

Hey Vadim,

Hi, have you had a chance to test if this bug is still present in natty?

If it does (and if you're the original reporter), please boot into natty
and run the command:

  apport-collect <bug-number>

which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)

[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.