unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Urban Duh <urby.duh@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 54436@debbugs.gnu.org
Subject: bug#54436: 28.0.91; Only every second mouse wheel scroll is registered
Date: Mon, 21 Mar 2022 10:20:19 +0100	[thread overview]
Message-ID: <CAC4YYwYOd45Dc1pj8ZTupT0ns1MJPiHjmhwvKAi10Umk0=O6jw@mail.gmail.com> (raw)
In-Reply-To: <87h77skq71.fsf@yahoo.com>

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

> On the other hand, I don't see why that would happen on Wayland.  Do you
> see a similar problem with a different mouse?  And can you verify that
> your build is actually running in Wayland and not Xwayland?

I have the same issue with two different mouses (Logitech MX Master 3 and
a cheap off-brand mouse). My build is running Wayland (tested with xeyes
and by disabling Xwayland on gnome via gnome-shell --no-x11).


On Mon, 21 Mar 2022 at 03:14, Po Lu <luangruo@yahoo.com> wrote:

> Urban Duh <urby.duh@gmail.com> writes:
>
> > Thanks for the insightful answers. The issue was indeed PGTK, the
> > official build of Emacs 28 works fine. I didn't realize that the
> > version I used was not official, sorry.  However, the same issue still
> > exists in Emacs 29 on Wayland and X (tested on GNOME on both X and
> > Wayland, using emacs-git with PGTK from AUR, which compiles from
> > development master branch), where PGTK is officially supported. Based
> > on your responses, it seems that this is a known issue
>
> The PGTK build is not supported on X Windows even in Emacs 29.  It just
> doesn't work well enough.
>
> On the other hand, I don't see why that would happen on Wayland.  Do you
> see a similar problem with a different mouse?  And can you verify that
> your build is actually running in Wayland and not Xwayland?
>
> Thanks.
>
> > but I cannot find any corresponding bug report (I could have missed it
> > though, I'm a bit clumsy with GNU's bug report logs). Should this bug
> > report be moved to Emacs version 29? Or should I report the issue
> > again for Emacs 29?
>
> You should leave it as-is, I think.
>

[-- Attachment #2: Type: text/html, Size: 2200 bytes --]

  reply	other threads:[~2022-03-21  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 10:47 bug#54436: 28.0.91; Only every second mouse wheel scroll is registered Urban Duh
2022-03-19  0:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-19 14:18   ` Lars Ingebrigtsen
2022-03-20 16:55     ` Urban Duh
2022-03-21  2:13       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-21  9:20         ` Urban Duh [this message]
2022-03-21 11:05           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-22 13:59             ` Urban Duh

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='CAC4YYwYOd45Dc1pj8ZTupT0ns1MJPiHjmhwvKAi10Umk0=O6jw@mail.gmail.com' \
    --to=urby.duh@gmail.com \
    --cc=54436@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.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).