From: Joshua Branson via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 58606@debbugs.gnu.org
Cc: andrew@trop.in
Subject: bug#58606: Emacs next pgtk crashes when pasting to other app
Date: Sun, 23 Oct 2022 15:12:52 -0400 [thread overview]
Message-ID: <87o7u2icaz.fsf@dismail.de> (raw)
In-Reply-To: <87fsfixwf1.fsf@dismail.de> (Joshua Branson via Bug reports for's message of "Thu, 20 Oct 2022 13:00:18 -0400")
Joshua Branson via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> Andrew Tropin <andrew@trop.in> writes:
>
>> Recently discovered a problem, which reproduces this way:
>> - Open a new emacs instance.
>> - Yank anything with M-w or select with mouse.
>> - Paste yanked text to chromium/icecat.
>>
>> Both browser and emacs are hanging up for a while and after that Emacs
>> crashes with:
>>
>> Fatal error 11: Segmentation fault
>>
>>
>> sway, emacs-next-pgtk, ungoogled-chromium
>
> I was unable to reproduce this bug. I am also using sway. Also thanks
> for the tip about emacs-next-pgtk. I didn't know that was packaged!
>
So I did just reconfigure, and I am now running a wayland only sway
session.
I did notice that I cannot seem to copy text from inside emacs and paste
into chromium or icecat... Chromium seemed to lock up after I tried to
paste into its url bar. Icecat did not accept the paste, but continued
working...
next prev parent reply other threads:[~2022-10-24 4:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 6:52 bug#58606: Emacs next pgtk crashes when pasting to other app Andrew Tropin
2022-10-20 17:00 ` Joshua Branson via Bug reports for GNU Guix
2022-10-23 19:12 ` Joshua Branson via Bug reports for GNU Guix [this message]
2022-10-22 10:40 ` Declan Tsien
2022-11-16 15:34 ` Joshua Branson via Bug reports for GNU Guix
2022-12-01 8:56 ` Andrew Tropin
2022-12-01 16:56 ` Joshua Branson via Bug reports for GNU Guix
2022-10-25 4:45 ` Andrew Tropin
2022-10-25 14:27 ` Joshua Branson via Bug reports for GNU Guix
2022-10-26 13:37 ` bokr
2023-03-20 10:39 ` Andrew Tropin
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7u2icaz.fsf@dismail.de \
--to=bug-guix@gnu.org \
--cc=58606@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=jbranso@dismail.de \
/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/guix.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).