unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Po Lu <luangruo@yahoo.com>
Cc: 57476@debbugs.gnu.org
Subject: bug#57476: 29.0.50; Mouse wheel event ignored on Lucid build
Date: Tue, 30 Aug 2022 14:58:05 +0200	[thread overview]
Message-ID: <871qsxx50i.fsf@gmx.net> (raw)
In-Reply-To: <87tu5toq20.fsf@yahoo.com> (Po Lu's message of "Tue, 30 Aug 2022 20:48:23 +0800")

On Tue, 30 Aug 2022 20:48:23 +0800 Po Lu <luangruo@yahoo.com> wrote:

> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> This failed to build; I assume you meant leave->detail, which did build.
>
> Yes, that's what I meant, sorry.
>
>> The shell output looks like this:
>>
>> Enter 0 3
>> Leave 1 0
>> Enter 2 0
>> Leave 1 0
>> Enter 2 0
>> Leave 1 0
>> Enter 2 0
>> Leave 1 0
>> ... (and so on)
>
> [...]
>
>> After applying the patch and rebuilding, scrolling the mouse wheel is
>> still a no-op.
>
> What window manager are you using?
> Is it xfwm4 by any chance?

Yes:

$ xfwm4 --version
	This is xfwm4 version 4.16.1 (revision 5f61a84ad) for Xfce 4.16
	Released under the terms of the GNU General Public License.
	Compiled against GTK+-3.24.31, using GTK+-3.24.33.

	Build configuration and supported features:
	- Startup notification support:                 Yes
	- XSync support:                                Yes
	- Render support:                               Yes
	- Xrandr support:                               Yes
	- Xpresent support:                             No
	- X Input 2 support:                            No
	- Embedded compositor:                          Yes
	- Epoxy support:                                Yes
	- KDE systray proxy (deprecated):               No

Perhaps the missing XInput2 support is causing the problem?

Steve Berman





  reply	other threads:[~2022-08-30 12:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 11:51 bug#57476: 29.0.50; Mouse wheel event ignored on Lucid build Stephen Berman
2022-08-30  1:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30  1:29   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30  8:20   ` Stephen Berman
2022-08-30 10:15     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 10:41       ` Stephen Berman
2022-08-30 12:48         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 12:58           ` Stephen Berman [this message]
2022-08-30 13:44             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 15:15               ` Stephen Berman
2022-08-31  2:19                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-31 18:17                   ` Stephen Berman
2022-09-01 13:21                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-01 22:41                       ` Stephen Berman
2022-09-02  1:08                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-03 11:25                           ` 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

  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=871qsxx50i.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=57476@debbugs.gnu.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).