From: Eli Zaretskii <eliz@gnu.org>
To: sergio.callegari@gmail.com, Po Lu <luangruo@yahoo.com>
Cc: 72549@debbugs.gnu.org
Subject: bug#72549: 29.4; menus do not work properly on wayland (pgtk)
Date: Sat, 24 Aug 2024 11:27:34 +0300 [thread overview]
Message-ID: <86msl2nx55.fsf@gnu.org> (raw)
In-Reply-To: <87y154lr44.fsf@yahoo.com> (message from Po Lu on Sat, 10 Aug 2024 16:27:39 +0800)
Ping! Sergio, can you please answer Po Lu's question?
> From: Po Lu <luangruo@yahoo.com>
> Cc: Sergio Callegari <sergio.callegari@gmail.com>, 72549@debbugs.gnu.org
> Date: Sat, 10 Aug 2024 16:27:39 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Date: Fri, 9 Aug 2024 13:42:54 +0200
> >> From: Sergio Callegari <sergio.callegari@gmail.com>
> >>
> >> Using emacs in KDE wayland, with the pgtk build. On a low spec machine,
> >> emacs is hardly usable in this configuration. The menu system (file,
> >> edit, options, etc.) misbehaves. For instance, you position the mouse on
> >> "buffers", but the buffers menu does not open. To get it, you need to go
> >> on File and then slowly move right through edit and options.
> >>
> >> On a high spec machine emacs is usable with exactly the same config (Amd
> >> ryzen 9 with amd graphics).
> >>
> >> in X11 mode, emacs is fine on both.
> >
> > Po Lu, any ideas or suggestions?
>
> Is this specific to KWin and Emacs, or reproducible on other compositors
> and with other GTK 3 programs also?
>
next prev parent reply other threads:[~2024-08-24 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 11:42 bug#72549: 29.4; menus do not work properly on wayland (pgtk) Sergio Callegari
2024-08-10 5:54 ` Eli Zaretskii
2024-08-10 8:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-24 8:27 ` Eli Zaretskii [this message]
2024-08-24 14:17 ` Sergio Callegari
2024-09-07 7:24 ` Eli Zaretskii
2024-09-07 9:15 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86msl2nx55.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72549@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=sergio.callegari@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 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.