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 17:15:46 +0200 [thread overview]
Message-ID: <878rn5kbj1.fsf@gmx.net> (raw)
In-Reply-To: <87bks1ongm.fsf@yahoo.com> (Po Lu's message of "Tue, 30 Aug 2022 21:44:25 +0800")
On Tue, 30 Aug 2022 21:44:25 +0800 Po Lu <luangruo@yahoo.com> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> 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?
>
> Please try enabling that, but we should work around the bug in xfwm
> builds without XInput 2 anyway.
I rebuilt xfwm4 with --enable-xi2, logged out and back in, but still the
Lucid build does not respond to mouse wheel scrolling. (I also tried
rebuilding Lucid without --with-xinput2, but that also made no difference.)
> In fact, this bug was fixed several months ago, but the fix disappeared
> sometime during the following cleanups to the scroll valuator management
> code.
Well, here's hoping you find it again!
Steve Berman
next prev parent reply other threads:[~2022-08-30 15:15 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
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 [this message]
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=878rn5kbj1.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).