From: Po Lu <luangruo@yahoo.com>
To: Tassilo Horn <tsdh@gnu.org>
Cc: eliz@gnu.org, emacs-devel@gnu.org, "T.V Raman" <raman@google.com>
Subject: Re: --with-pgtk crashes
Date: Fri, 07 Jan 2022 14:51:48 +0800 [thread overview]
Message-ID: <87ee5kyr5n.fsf@yahoo.com> (raw)
In-Reply-To: <87mtk883n5.fsf@gnu.org> (Tassilo Horn's message of "Fri, 07 Jan 2022 07:13:21 +0100")
Tassilo Horn <tsdh@gnu.org> writes:
> Po Lu <luangruo@yahoo.com> writes:
>
>>> It doesn't yield a backtrace -- even if started with --dbug-init ---
>>> basically emacs launches, then the window disappears -- it dumps some
>>> debug addresses in .xsession-errors but they dont look meaningful.
>>
>> Please run Emacs under GDB, and show a backtrace from that.
>
> FWIW, I'm on wayland with PGTK enabled and it's working just fine. When
> I explicitly state that it should run unter xwayland instead using
>
> env -u WAYLAND_DISPLAY emacs -Q
>
> I get no crash but except for the mode-line and menu-bar nothing is
> displayed/rendered, that is, the scratch buffer is and stays empty and
> so is the echo area. There's also no tool-bar. I can see that emacs
> reacts, e.g., `C-h i' will open info which I can see because the frame
> changes its title.
>
> Oh, well, when I resize the emacs frame a bit (I'm using a tiling
> compositior), out of sudden all those missing things appear. :-)
> So I guess that's a separate issue. I'll submit a bug report later.
Thanks, one question though: does this happen with other GTK programs
running inside Xwayland?
next prev parent reply other threads:[~2022-01-07 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 18:03 --with-pgtk crashes T.V Raman
2022-01-06 20:08 ` Eli Zaretskii
2022-01-06 21:10 ` T.V Raman
2022-01-07 0:43 ` Po Lu
2022-01-07 6:13 ` Tassilo Horn
2022-01-07 6:51 ` Po Lu [this message]
2022-01-07 7:58 ` Tassilo Horn
2022-01-07 15:15 ` T.V Raman
2022-01-07 7:07 ` Eli Zaretskii
2022-01-07 14:59 ` T.V Raman
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=87ee5kyr5n.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=raman@google.com \
--cc=tsdh@gnu.org \
/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.