unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
Cc: 53957@debbugs.gnu.org
Subject: bug#53957: 29.0.50; pgtk: starting emacsclient from thunar breaks X clipboard access
Date: Sun, 13 Feb 2022 09:17:00 +0800	[thread overview]
Message-ID: <878rufo99v.fsf@yahoo.com> (raw)
In-Reply-To: <4f4f9e9a-e88c-d63b-f836-d3af9c8602df@posteo.eu> ("Sébastien Miquel"'s message of "Sat, 12 Feb 2022 12:46:31 +0000")

Sébastien Miquel <sebastien.miquel@posteo.eu> writes:

> Hi,
>
> To reproduce :
>  1. Start `emacs -q --daemon`
>  2. Start a frame with `emacsclient -c`. At this point, X clipboard
>  access works fine and I can copy/paste between emacs and other
> applications.
>  3. From Thunar (file manager from xfce), right click a file and `Open
>  with` emacsclient (/usr/bin/emacsclient), creating another frame.
>     At this point, X clipboard access is broken: I cannot copy/paste
>  between emacs and other applications.
>
> In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
> 3.24.31, cairo version 1.17.4)
>  of 2022-02-05
> Repository revision: 224aeb2877fffc894e9d1b31f7f44db0e55160c3
> Repository branch: master
> System Description: Arch Linux

If you're using X, you shouldn't be using PGTK.  The support provided by
the real X port is miles ahead of what GTK can offer.

That aside, I suspect emacsclient is causing Emacs to open a second
display connection, which causes clipboard access in PGTK to be disabled
due to a GTK bug.

What does (x-display-list) evaluate to in the buggy Emacs, after you
create the other frame which causes the bug?

Thanks.





  reply	other threads:[~2022-02-13  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12 12:46 bug#53957: 29.0.50; pgtk: starting emacsclient from thunar breaks X clipboard access Sébastien Miquel
2022-02-13  1:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-13  8:08   ` Sébastien Miquel
2022-02-13  8:17     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-13  8:39       ` Sébastien Miquel
2022-02-13  9:44         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=878rufo99v.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53957@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=sebastien.miquel@posteo.eu \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).