Ubuntu
xorg package

apport sometimes prints "Cannot open display" when run over ssh

Bug #368282 reported by Martin Olsson
2
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

repro:
Try to login to a machine which is standing at GDM and then run apport-collect.

Doing exactly that is a critically important use case for xorg crashes because if you login the xorg.log gets reset and whatever was in xorg.log.old is permanently lost.

Maybe this bug only affects the xorg hook for apport (not sure?)

mnemo@zueco:~$ apport-collect 368049
Logging into Launchpad...
The authorization page (https://edge.launchpad.net/+authorize-token?oauth_token=8Bwts9Lrkwnz8M5TqtZf) should be opening in your browser. After you have authorized this program to access Launchpad on your behalf you should come back here and press <Enter> to finish the authentication process.

Downloading bug...
Bug title: compiz crashes gnome desktop using default ati driver (radeon X600)
Collecting apport information for source package xserver-xorg-video-ati...
Can't open display
xdpyinfo: unable to open display "".
Error: unable to open display
Cannot open display "default display"
No protocol specified
Error: Cannot open display ":0"
                  Exiting
Uploading additional information to Launchpad bug...
   short text data...
   attachment: Dependencies.txt...
   attachment: LsHal.txt...
   attachment: LsMod.txt...
   attachment: LsPci.txt...
   attachment: XorgConf.txt...
   attachment: XorgLog.txt...
   attachment: XorgLogOld.txt...
   attachment: system.txt...

Revision history for this message
Martin Pitt (pitti) wrote :

This actually comes from xorg's package hook. I guess there's no way around having $DISPLAY set for some commands, but maybe it can be quiesced a bit. Something like this, perhaps:

  if os.environ.get('DISPLAY'):
      # do commands which need $DISPLAY
  # do commands which don't need $DISPLAY

affects: apport (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg - 1:7.5+1ubuntu2

---------------
xorg (1:7.5+1ubuntu2) lucid; urgency=low

  [ David Planella ]
  * Completed internationalisation support for failsafeXinit (LP: #335678)

  [ Didier Roche ]
  * debian/local/Xsession.d/20x11-common_process-args: Add support for
    session command containing args (LP: #512235)

  [ Bryce Harrington ]
  * debian/local/Failsafe/failsafeXinit: Remove all use of dexconf, as it
    no longer does anything interesting. Instead, to restore a system to
    default configuration, just remove the xorg.conf after backing it up.
  * debian/local/Failsafe/failsafeDexconf: Drop script since it is no
    longer needed by failsafe.
  * debian/apport/source_xorg.py: Update info apport collects on X issues
    - Include make.log and dkms status info for proprietary drivers
    - Collect -nouveau version
    - Don't expect xorg.conf or Xorg.0.log.old to always be present
    - Don't run commands that need X if X is not available (LP: #368282)

  [ Timo Aaltonen ]
  * Add wacom back to -input-all.
 -- Bryce Harrington <email address hidden> Mon, 25 Jan 2010 15:33:13 -0800

Changed in xorg (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.