suspend to ram; 5 minute wakeup time; unable to open display localhost:0.0, no guis could be launched (gkrellm)

[BrianP]

root@trex:/home/brianp# uname -a
Linux trex 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux
root@trex:/home/brianp# cat /proc/version_signature
Ubuntu 2.6.31-14.48-generic

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: brianp 2077 F.... pulseaudio
 /dev/snd/controlC1: brianp 2077 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe6f8000 irq 22'
   Mixer name : 'Analog Devices AD1989B'
   Components : 'HDA:11d4989b,10438311,00100300'
   Controls : 47
   Simple ctrls : 26
Card1.Amixer.info:
 Card hw:1 'Headset'/'Plantronics CS50/CS60-USB Headset at usb-0000:00:1d.2-1, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB047f:0410'
   Controls : 6
   Simple ctrls : 4
Card2.Amixer.info:
 Card hw:2 'HDMI'/'HDA ATI HDMI at 0xfe7fc000 irq 17'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100100'
   Controls : 4
   Simple ctrls : 1
Card2.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [off]
Date: Fri Oct 23 08:26:41 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=e356bde9-0241-4f96-9115-695fea8f3e67
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
MachineType: System manufacturer P5Q3 DELUXE
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=7bf6a638-b9c3-4d21-a25b-84603b5685e5 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:

SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80()
Uname: Linux 2.6.31-14-generic x86_64
dmi.bios.date: 03/17/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2004
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q3 DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd03/17/2009:svnSystemmanufacturer:pnP5Q3DELUXE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q3 DELUXE
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[BrianP (brianp-austin)]

unable to open display "localhost:0.0" persists.

Google "localhost:0.0" and you get 358,000 hits. Other than permission problems, this may be the most stumbled over mis-over-engineered feature is all of Linux. This is a severe and perennial usability problem.

In a clean Ubuntu 9.10 install, I can find zero tools to address the problem. If a third of a million people had enough of a problem with it to actually write to a news group, one could argue that millions have tripped over the same issue. Does this not scream out for an install option or some type of system tool like Applications->System->Fixed_FUBARred_LOCOHOST?

I found a bug report, Bug #370607, "X applications won't run under sudo", with similar results, but this problem has existed for years.
Bryce Harrington wrote on 2009-06-10:
I would first check gdm.conf... Next I would check what options are being specified on the X binary. Here's mine:
  /usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7

`locate gdm.conf` -> /etc/init/gdm.conf. I have no line anything like this. Where is "-nolisten" being specified in this release? Is there any tool to configure the x server? Where?

When people have to spend many hours tracking down the latest implementation of these type of bugs, they get severely turned off on Linux.

    BrianP

[BrianP (brianp-austin)]

What's the difference between the GDM in 9.04 and 9.10?

While grasping at straws and editing /usr/bin/startx, I noticed that it had:
    defaultdisplay=":0"
In my mostly working 9.04 ~/.bashrc, I had the line:
    export DISPLAY=localhost:0.0
Changing my broken 9.10 ~/.bashrc to:
    export DISPLAY=:0
and running:
    brianp@trex:/etc/X11$ xhost +
    access control disabled, clients can connect from any host
I can now run gvim. Why does one display work in 9.04 while breaking 9.10? Which one is correct? More correct? I have read accounts of people stating that this is a "really bad idea". Am I shooing myself in the foot here?

There must be a system tool for exactly this problem. I have been all over the only App->Sys tool which looks at all promising, the Configuration_Editor. Desktop -> Gnome -> Session looked interesting, but no sign of TCP, NOLISTEN GDM, KDM, ... Then, there is Apps -> GDM -> Simple-Greeter (the only item) -> settings-manager-plugins -> XSettings (!!!) This has to be it. No, just active and priority.

What am I missing here?

Thank you,
    BrianP

[Leann Ogasawara (leannogasawara)]

Hi BrianP,

The warning reported here typically indicates that it took longer for your system to resume from suspend than expected. I believe there is a 5 sec barrier which your system likely exceeded. Typically you'll see something similar to "PM: resume devices took 8.664 seconds" in your dmesg output when this happens. I'm setting this to traiged for further investigation. Thanks!

[This is an automated message. Apologies if it has reached you inappropriately.]

[Brian Murray (brian-murray)]

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 417842, 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. Please continue to report any other bugs you may find.