all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Sewall\, Jason" <jason.sewall@intel.com>
Cc: 15037@debbugs.gnu.org
Subject: bug#15037: Display can't be opened (display newer than emacs session)
Date: Wed, 07 Aug 2013 14:19:59 -0400	[thread overview]
Message-ID: <jwviozh4bdt.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <C64EEADE742C444EA672808682DC050459B003C3@ORSMSX104.amr.corp.intel.com> (Jason Sewall's message of "Wed, 7 Aug 2013 17:31:18 +0000")

>> What does M-: (getenv "XAUTHORITY") RET say in those two Emacs sessions?

> For the older session (in the original frame): "/var/run/gdm/auth-for-jsewall-jWCxJH/database"

> For a new session started from display :1.0, 'nil'. 

There's your problem.  You're using GDM3 which has the obnoxious habit
of putting your authorization keys in a separate file and setting
XAUTHORITY to point to it.  So your session doesn't have access to the
keys you have in your ~/.Xauthority and your other sessions don't have access
to this display.

See:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586685
https://bugzilla.gnome.org/show_bug.cgi?id=651431

Note that it's not just Emacs that suffers this way:
If M-x make-frame-on-display <RET> :1.0 <RET> fails for you, then try
(in that very same Emacs) to do M-x shell RET xterm --display :1.0 RET
it should fail in the same way.


        Stefan





      reply	other threads:[~2013-08-07 18:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06 20:52 bug#15037: Display can't be opened (display newer than emacs session) Sewall, Jason
2013-08-07  0:03 ` Glenn Morris
2013-08-07 17:39   ` Sewall, Jason
2013-08-07  8:32 ` Jan Djärv
2013-08-07 17:37   ` Sewall, Jason
2013-08-07 14:30 ` Stefan Monnier
2013-08-07 17:31   ` Sewall, Jason
2013-08-07 18:19     ` Stefan Monnier [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwviozh4bdt.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=15037@debbugs.gnu.org \
    --cc=jason.sewall@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.