From: "Jan Djärv" <jan.h.d@swipnet.se>
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, 7 Aug 2013 10:32:47 +0200 [thread overview]
Message-ID: <A56114DC-2944-4E8F-BF01-F9F680FDF85A@swipnet.se> (raw)
In-Reply-To: <C64EEADE742C444EA672808682DC050459B00173@ORSMSX104.amr.corp.intel.com>
Hello.
6 aug 2013 kl. 22:52 skrev "Sewall, Jason" <jason.sewall@intel.com>:
> I have a long-running emacs session with a server running on it (24.2.1, on Fedora 18). I have started up a new VNC session on the host, creating DISPLAY :1.0, but emacs refuses to let me create a frame on it:
>
> M-x make-frame-on-display <RET> :1.0 <RET>
> Display :1.0 can't be opened
>
> If I start a new emacs session with emacs (with -Q or not) and run the above, the frame is created.
>
> I am not an expert in emacs frame handling nor in X, but it seems like emacs is reading the available displays when it starts up and refuses to connect to anything that started up after it. I'm happy to provide more info as needed.
That is not what Emacs does. "Reading available displays" is not possible. Emacs just tries to connect when you do open display.
Did you kill the old server and start a new server in the same shell as you started the first? My guess is that you did not, and so the second server either gets the correct authentication and thus can connect.
To really see what is going on you would need to debug Emacs with gdb when the make-frame-on-display fails.
Jan D.
next prev parent reply other threads:[~2013-08-07 8:32 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 [this message]
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
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=A56114DC-2944-4E8F-BF01-F9F680FDF85A@swipnet.se \
--to=jan.h.d@swipnet.se \
--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.