unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrew Tropin <andrew@trop.in>
To: Stefan Kangas <stefankangas@gmail.com>, Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 62291@debbugs.gnu.org
Subject: bug#62291: 30.0.50; PGTK copy + paste to other app problem
Date: Tue, 12 Sep 2023 15:24:39 +0400	[thread overview]
Message-ID: <878r9bzlag.fsf@trop.in> (raw)
In-Reply-To: <CADwFkmmTJGA+9YtPgMum=Rgfb8pTozdDT=2ALj4c9XNas2zcSg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2920 bytes --]

On 2023-09-11 17:11, Stefan Kangas wrote:

> tags 62291 + moreinfo
> thanks
>
> Po Lu <luangruo@yahoo.com> writes:
>
>> Andrew Tropin <andrew@trop.in> writes:
>>
>>> I restart the debbugger every time because otherwise my clipboard is
>>> "locked", so the widget from p widget and from output_data.pgtk are the
>>> same.  Sorry for the confusion.
>>>
>>> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
>>> 0x00007ffff71b5424 in signal_emit_unlocked_R.isra.0 () from /gnu/store/96srhmpmxa20wmsck95g3iq4hb3lz4a0-glib-2.70.2/lib/libgobject-2.0.so.0
>>> (gdb) bt
>>> #0  0x00007ffff71b5424 in signal_emit_unlocked_R.isra.0 () from /gnu/store/96srhmpmxa20wmsck95g3iq4hb3lz4a0-glib-2.70.2/lib/libgobject-2.0.so.0
>>> #1  0x00007ffff71bb21b in g_signal_emit_valist () from /gnu/store/96srhmpmxa20wmsck95g3iq4hb3lz4a0-glib-2.70.2/lib/libgobject-2.0.so.0
>>> #2  0x00007ffff71bb722 in g_signal_emit () from /gnu/store/96srhmpmxa20wmsck95g3iq4hb3lz4a0-glib-2.70.2/lib/libgobject-2.0.so.0
>>> #3  0x00007ffff71a7884 in g_object_dispatch_properties_changed () from /gnu/store/96srhmpmxa20wmsck95g3iq4hb3lz4a0-glib-2.70.2/lib/libgobject-2.0.so.0
>>> #4  0x00007ffff71a9834 in g_object_notify_by_pspec () from /gnu/store/96srhmpmxa20wmsck95g3iq4hb3lz4a0-glib-2.70.2/lib/libgobject-2.0.so.0
>>> #5  0x00007ffff79afbcd in gtk_window_focus_in_event (event=<optimized out>, widget=0x109a500) at gtkwindow.c:8503
>>> #6  gtk_window_focus_in_event (widget=widget@entry=0x109a500, event=<optimized out>) at gtkwindow.c:8491
>>> #7 0x00007ffff79de357 in _gtk_marshal_BOOLEAN__BOXED (closure=0x10b73e0,
>>> return_value=0x7fffffffb570, n_param_values=<optimized out>,
>>> param_values=0x7fffffffb620,
>>>     invocation_hint=<optimized out>, marshal_data=<optimized out>) at gtkmarshalers.c:83
>>> #8  0x00007ffff71a34af in g_closure_invoke () from /gnu/store/96srhmpmxa20wmsck95g3iq4hb3lz4a0-glib-2.70.2/lib/libgobject-2.0.so.0
>>> #9  0x00007ffff71b49e9 in signal_emit_unlocked_R.isra.0 () from /gnu/store/96srhmpmxa20wmsck95g3iq4hb3lz4a0-glib-2.70.2/lib/libgobject-2.0.so.0
>>
>> Right, thanks for clarifying that.
>> Perhaps this crash is not related to the widget being destroyed.
>> If you install debuginfo and debug source for libgobject, then type `l',
>> where does it show the crash occurs?
>
> Ping.  Andrew, did you get any further with this?

I couldn't get debug symbols for libgobject, probably cause of grafts
and kinda gave up on this issue, sorry.

For the whole time we were using this fix in rde:
https://git.sr.ht/~abcdw/rde/tree/8d6a6b47/src/rde/features/emacs.scm#L217

And recently (a few minutes ago) I found out that the problem
dissapeared, so I don't need this fix anymore.  IDK, if it is due to
chromium version update or emacs.

Thank you very much for pinging! :)

I will report further in case it reappears.

-- 
Best regards,
Andrew Tropin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2023-09-12 11:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 10:33 bug#62291: 30.0.50; PGTK copy + paste to other app problem Andrew Tropin
2023-03-20 11:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-20 11:17   ` Andrew Tropin
2023-03-20 12:36     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-21  9:10       ` Andrew Tropin
2023-03-21 10:30         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-21 13:25           ` Andrew Tropin
2023-03-21 16:13           ` Andrew Tropin
2023-03-22  0:39             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-22  4:42               ` Andrew Tropin
2023-03-22  6:11                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-22  7:28                   ` Andrew Tropin
2023-03-22 10:33                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-22 11:02                       ` Andrew Tropin
2023-03-23  0:44                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-23  5:18                           ` Andrew Tropin
2023-03-23  7:16                             ` Eli Zaretskii
2023-03-23 18:22                               ` Andrew Tropin
2023-03-24  1:00                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-24  4:31                                   ` Andrew Tropin
2023-03-24  7:51                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-24 10:39                                       ` Andrew Tropin
2023-03-24 11:40                                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12  0:11                                           ` Stefan Kangas
2023-09-12 11:24                                             ` Andrew Tropin [this message]
2023-09-12 14:50                                               ` Stefan Kangas

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=878r9bzlag.fsf@trop.in \
    --to=andrew@trop.in \
    --cc=62291@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=stefankangas@gmail.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 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).