bug#67341: 29.1.90; Open frame on display doesn't work in wayland

bug#67341: 29.1.90; Open frame on display doesn't work in wayland

[phill]

Select File => New frame on display server from the menu.  You are
prompted for the display server to connect to.  Enter some value other
than the default.  Emacs ignores the value you entered and instead
creates a new frame on your current display server.


In GNU Emacs 29.1.90 (build 1, x86_64-pc-linux-gnu, GTK+ Version
 3.24.38, cairo version 1.17.8) of 2023-10-19 built on localhost
System Description: Gentoo Linux

Configured using:
 'configure --prefix=/usr --build=x86_64-pc-linux-gnu
 --host=x86_64-pc-linux-gnu --mandir=/usr/share/man
 --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
 --localstatedir=/var/lib --datarootdir=/usr/share
 --disable-silent-rules --docdir=/usr/share/doc/emacs-29.1.90
 --htmldir=/usr/share/doc/emacs-29.1.90/html --libdir=/usr/lib64
 --program-suffix=-emacs-29-vcs --includedir=/usr/include/emacs-29-vcs
 --infodir=/usr/share/info/emacs-29-vcs --localstatedir=/var
 --enable-locallisppath=/etc/emacs:/usr/share/emacs/site-lisp
 --without-compress-install --without-hesiod --without-pop
 --with-file-notification=inotify --with-pdumper --enable-acl
 --with-dbus --with-modules --without-gameuser --with-libgmp --with-gpm
 --with-native-compilation=aot --without-json --without-kerberos
 --without-kerberos5 --with-lcms2 --without-xml2 --without-mailutils
 --without-selinux --without-small-ja-dic --without-sqlite3
 --with-gnutls --with-libsystemd --with-threads --with-tree-sitter
 --without-wide-int --with-sound=alsa --with-zlib --with-pgtk
 --without-x --without-ns --with-toolkit-scroll-bars --without-gconf
 --without-gsettings --without-harfbuzz --without-libotf
 --without-m17n-flt --without-xwidgets --with-gif --with-jpeg --with-png
 --with-rsvg --with-tiff --without-webp --without-imagemagick
 --with-dumping=pdumper 'CFLAGS=-march=native -O2 -pipe'
 'LDFLAGS=-Wl,-O1 -Wl,--as-needed''

Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM JPEG LCMS2 LIBSYSTEMD
MODULES NATIVE_COMP NOTIFY INOTIFY PDUMPER PGTK PNG RSVG SECCOMP SOUND
THREADS TIFF TOOLKIT_SCROLL_BARS TREE_SITTER XIM GTK3 ZLIB

Important settings:
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Info

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  show-paren-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  isearch-fold-quotes-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  buffer-read-only: t
  line-number-mode: t
  indent-tabs-mode: t
  transient-mark-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message yank-media puny dired
dired-loaddefs rfc822 mml mml-sec epa derived epg rfc6068 epg-config
gnus-util text-property-search mm-decode mm-bodies mm-encode mail-parse
rfc2231 mailabbrev gmm-utils mailheader sendmail rfc2047 rfc2045
ietf-drums mm-util mail-prsvr mail-utils misearch multi-isearch
goto-addr thingatpt view finder finder-inf find-func lisp-mnt mule-util
jka-compr info noutline outline kmacro facemenu two-column time-date
comp comp-cstr warnings icons rx cl-extra help-mode manoj-dark-theme
site-gentoo ranger-autoloads scopeline-autoloads package browse-url url
url-proxy url-privacy url-expand url-methods url-history url-cookie
generate-lisp-file url-domsuf url-util mailcap url-handlers url-parse
auth-source cl-seq eieio eieio-core cl-macs password-cache json subr-x
map byte-opt gv bytecomp byte-compile url-vars cl-loaddefs cl-lib rmc
iso-transl tooltip cconv eldoc paren electric uniquify ediff-hook
vc-hooks lisp-float-type elisp-mode mwheel term/pgtk-win pgtk-win
term/common-win pgtk-dnd tool-bar dnd fontset image regexp-opt fringe
tabulated-list replace newcomment text-mode lisp-mode prog-mode register
page tab-bar menu-bar rfn-eshadow isearch easymenu timer select
scroll-bar mouse jit-lock font-lock syntax font-core term/tty-colors
frame minibuffer nadvice seq simple cl-generic indonesian philippine
cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech
european ethiopic indian cyrillic chinese composite emoji-zwj charscript
charprop case-table epa-hook jka-cmpr-hook help abbrev obarray oclosure
cl-preloaded button loaddefs theme-loaddefs faces cus-face macroexp
files window text-properties overlay sha1 md5 base64 format env
code-pages mule custom widget keymap hashtable-print-readable backquote
threads dbusbind inotify dynamic-setting font-render-setting cairo gtk
pgtk lcms2 multi-tty make-network-process native-compile emacs)

Memory information:
((conses 16 146676 11311)
 (symbols 48 10243 0)
 (strings 32 33280 2928)
 (string-bytes 1 941076)
 (vectors 16 21909)
 (vector-slots 8 432823 19920)
 (floats 8 68 114)
 (intervals 56 9470 0)
 (buffers 984 15))

bug#67341: 29.1.90; Open frame on display doesn't work in wayland

[Eli Zaretskii]

> From: phill@thesusis.net
> Date: Tue, 21 Nov 2023 14:44:36 -0500
> 
> 
> Select File => New frame on display server from the menu.  You are
> prompted for the display server to connect to.  Enter some value other
> than the default.  Emacs ignores the value you entered and instead
> creates a new frame on your current display server.

Does your user have access to the X server on that display?

What does the below yield if you type it in the new frame:

  M-: (frame-parameter nil 'display) RET

bug#67341: 29.1.90; Open frame on display doesn't work in wayland

[Phillip Susi]

Eli Zaretskii <eliz@gnu.org> writes:

> Does your user have access to the X server on that display?

Wayland, not X.  And yes.  I also tried running emacsclient -c from
another wayland session and emacs opened the frame in the first one.

> What does the below yield if you type it in the new frame:
>
>   M-: (frame-parameter nil 'display) RET

I'm home for the holidays so I'll have to check that next Monday.

bug#67341: 29.1.90; Open frame on display doesn't work in wayland

[Phillip Susi]

Phillip Susi <phill@thesusis.net> writes:

>> What does the below yield if you type it in the new frame:
>>
>>   M-: (frame-parameter nil 'display) RET
>
> I'm home for the holidays so I'll have to check that next Monday.

After asking it to create a new frame on wayland-2, running that command
in the new frame that appeared in wayland-1 of course, says wayland-1.

bug#67341: 29.1.90; Open frame on display doesn't work in wayland

[Eli Zaretskii]

> From: Phillip Susi <phill@thesusis.net>
> Cc: 67341@debbugs.gnu.org
> Date: Tue, 28 Nov 2023 13:34:31 -0500
> 
> Phillip Susi <phill@thesusis.net> writes:
> 
> >> What does the below yield if you type it in the new frame:
> >>
> >>   M-: (frame-parameter nil 'display) RET
> >
> > I'm home for the holidays so I'll have to check that next Monday.
> 
> After asking it to create a new frame on wayland-2, running that command
> in the new frame that appeared in wayland-1 of course, says wayland-1.

Can you step in Edebug through make-frame-on-display and make-frame,
and try to figure out how come wayland-2 becomes wayland-1, during the
processing of the command?

bug#67341: 29.1.90; Open frame on display doesn't work in wayland

[Phillip Susi]

Eli Zaretskii <eliz@gnu.org> writes:

> Can you step in Edebug through make-frame-on-display and make-frame,
> and try to figure out how come wayland-2 becomes wayland-1, during the
> processing of the command?

I've never tried using the emacs debugger before, but I managed to get
it to enter debug on entry to make-frame-on-display, and had to hit 'd'
to step through it a LOT.  I only ever saw "wayland-2", never
"wayland-1".  There were a bunch of window on "Minibuf-0".

bug#67341: 29.1.90; Open frame on display doesn't work in wayland

[Eli Zaretskii]

> From: Phillip Susi <phill@thesusis.net>
> Cc: 67341@debbugs.gnu.org
> Date: Wed, 29 Nov 2023 15:42:02 -0500
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Can you step in Edebug through make-frame-on-display and make-frame,
> > and try to figure out how come wayland-2 becomes wayland-1, during the
> > processing of the command?
> 
> I've never tried using the emacs debugger before, but I managed to get
> it to enter debug on entry to make-frame-on-display, and had to hit 'd'
> to step through it a LOT.  I only ever saw "wayland-2", never
> "wayland-1".  There were a bunch of window on "Minibuf-0".

I meant Edebug, not the basic debugger.  Edebug is easier to use, and
it is fully documented in the ELisp manual.

Something like the below should get you started:

  emacs -Q
  M-x load-library RET frame.el RET
  C-x C-f /path/to/lisp/frame.el RET
  C-s defun make-frame ( RET
  M-x edebug-defun RET
  M-x make-frame-on-display RET wayland-2 RET

Now you should see Edebug kick in: Emacs will show the make-frame
function with a little arrow on the fringe to the left of the
beginning of its code.  You can press SPC to step through the code.
Step like that until you get to this part:

    (setq frame (let ((window-system w)) ; Hack attack!
                  (frame-creation-function params)))

and tell the value of 'params' passed to frame-creation-function (the
value will be shown in the echo-area when the cursor is just after
"params").

Let me know if you need more help with Edebug.

Thanks.