GNU bug report logs -
#57020
29.0.50; Mouse wheel stops working
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 57020 in the body.
You can then email your comments to 57020 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57020
; Package
emacs
.
(Sat, 06 Aug 2022 22:54:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Michael Heerdegen <michael_heerdegen <at> web.de>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sat, 06 Aug 2022 22:54:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello,
I have been seeing this for a while now (maybe two weeks or a bit more,
not sure when it started exactly):
After starting Emacs everything is good. But after a while, the mouse
wheel stops working. That is, mouse-4 and mouse-5, with and without
modifiers, are not recognized. In all buffers and windows, scroll-bar,
mode line, everywhere. C-h k shows nothing because no event is
registered.
When that happens the mouse wheel still works normally in other X
windows or the window manager or in a newly started Emacs session.
This is under X and Openbox.
TIA,
Michael.
In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0)
of 2022-08-06 built on drachen
Repository revision: fe801e359f71f12843c8d0ce545473815840dc89
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12011000
System Description: Debian GNU/Linux 11 (bullseye)
Configured features:
CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GSETTINGS HARFBUZZ JPEG JSON
LCMS2 LIBSELINUX LIBXML2 MODULES NOTIFY INOTIFY PDUMPER PNG RSVG SECCOMP
SOUND SQLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS WEBP X11 XDBE XIM XINPUT2
XPM GTK3 ZLIB
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57020
; Package
emacs
.
(Sun, 07 Aug 2022 01:58:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 57020 <at> debbugs.gnu.org (full text, mbox):
Michael Heerdegen <michael_heerdegen <at> web.de> writes:
> Hello,
>
> I have been seeing this for a while now (maybe two weeks or a bit more,
> not sure when it started exactly):
>
> After starting Emacs everything is good. But after a while, the mouse
> wheel stops working. That is, mouse-4 and mouse-5, with and without
> modifiers, are not recognized. In all buffers and windows, scroll-bar,
> mode line, everywhere. C-h k shows nothing because no event is
> registered.
>
> When that happens the mouse wheel still works normally in other X
> windows or the window manager or in a newly started Emacs session.
>
> This is under X and Openbox.
mouse-4/mouse-5 or wheel-up/wheel-down?
Please be clear here, since they are handled separately under XInput 2.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57020
; Package
emacs
.
(Sun, 07 Aug 2022 02:08:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 57020 <at> debbugs.gnu.org (full text, mbox):
Po Lu <luangruo <at> yahoo.com> writes:
> mouse-4/mouse-5 or wheel-up/wheel-down?
>
> Please be clear here, since they are handled separately under XInput
> 2.
You are right, the force of habit: When the events are considered they
are named "wheel-up/wheel-down" - I'm sorry.
Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57020
; Package
emacs
.
(Sun, 07 Aug 2022 02:48:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 57020 <at> debbugs.gnu.org (full text, mbox):
Michael Heerdegen <michael_heerdegen <at> web.de> writes:
> Po Lu <luangruo <at> yahoo.com> writes:
>
>> mouse-4/mouse-5 or wheel-up/wheel-down?
>>
>> Please be clear here, since they are handled separately under XInput
>> 2.
>
> You are right, the force of habit: When the events are considered they
> are named "wheel-up/wheel-down" - I'm sorry.
>
> Michael.
Could you instrument this chunk of xterm.c:
/* See the comment on top of x_cache_xi_devices
for more details on how scroll wheel movement
is reported on XInput 2. */
delta = x_get_scroll_valuator_delta (dpyinfo, device,
i, *values, &val);
values++;
by adding:
printf ("%g\n", delta);
afterwards? Then, please see if any (and what) values are printed once
the mouse wheel stops working.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57020
; Package
emacs
.
(Mon, 08 Aug 2022 01:59:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 57020 <at> debbugs.gnu.org (full text, mbox):
Po Lu <luangruo <at> yahoo.com> writes:
> printf ("%g\n", delta);
>
> afterwards? Then, please see if any (and what) values are printed once
> the mouse wheel stops working.
Short answer: nothing is printed.
Before the issue starts happening, I see -1 and +1 for each wheel
"click" and lots of 1.79769e+308 values when moving the mouse.
Once scrolling stopped working, mouse wheel turning leads to no output
any more (but the 1.79769e+308 values are still printed).
What I was also noticing: when turning the mouse wheel over the scroll
bar, there is a visual feedback: it looks like the scroll bar would lead
to a scroll (the bar moves), but scrolling is not happening, the buffer
text stands still. Also that is happening without output for DELTA.
Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57020
; Package
emacs
.
(Mon, 08 Aug 2022 02:37:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 57020 <at> debbugs.gnu.org (full text, mbox):
Michael Heerdegen <michael_heerdegen <at> web.de> writes:
> Po Lu <luangruo <at> yahoo.com> writes:
>
>> printf ("%g\n", delta);
>>
>> afterwards? Then, please see if any (and what) values are printed once
>> the mouse wheel stops working.
>
> Short answer: nothing is printed.
>
> Before the issue starts happening, I see -1 and +1 for each wheel
> "click" and lots of 1.79769e+308 values when moving the mouse.
>
> Once scrolling stopped working, mouse wheel turning leads to no output
> any more (but the 1.79769e+308 values are still printed).
>
> What I was also noticing: when turning the mouse wheel over the scroll
> bar, there is a visual feedback: it looks like the scroll bar would lead
> to a scroll (the bar moves), but scrolling is not happening, the buffer
> text stands still. Also that is happening without output for DELTA.
>
> Michael.
Hmm, thanks. Could you also add the following instrumentation to that
code, like such:
device = xi_device_from_id (dpyinfo, xev->deviceid);
if (!device)
{
fprintf (stderr, "device not found, %d\n", xev->deviceid);
goto XI_OTHER;
}
and see if that is ever printed when wheel movement stops working?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57020
; Package
emacs
.
(Tue, 09 Aug 2022 00:14:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 57020 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Po Lu <luangruo <at> yahoo.com> writes:
> Hmm, thanks. Could you also add the following instrumentation to that
> code, like such: [...]
You mean like this?
[0001-Instrument-xterm.c.patch (text/x-diff, inline)]
diff --git a/src/xterm.c b/src/xterm.c
index 36797bc0ab..88cd566cd3 100644
--- a/src/xterm.c
+++ b/src/xterm.c
@@ -20465,7 +20465,10 @@ handle_one_xevent (struct x_display_info *dpyinfo,
device = xi_device_from_id (dpyinfo, xev->deviceid);
if (!device)
- goto XI_OTHER;
+ {
+ fprintf (stderr, "device not found, %d\n", xev->deviceid);
+ goto XI_OTHER;
+ }
#ifdef HAVE_XINPUT2_2
if (xev->flags & XIPointerEmulated)
--
2.30.2
[Message part 3 (text/plain, inline)]
No, I got no output after the mouse wheel had stopped working.
But I have a new data point: there seems to be a relation with switching
to the X session of a different user. I sometimes have several X
sessions running a the same time. Some minutes ago the wheel had
stopped working. I switched to the X session at C-M-f2 and then back to
here (i.e. C-M-f1) and the mouse wheel started to work again.
I'm not saying that there is a connection between the failure and other
X sessions, however. AFAIR, when the mouse wheel stopped working
yesterday there was only one X session running. Maybe closing the
laptop (suspend to RAM) sometimes triggers this, but that's just
guessing. That switching X sessions healed the issue didn't seem
incidental, however. I had the feeling that I should try that, and I
had been using the mouse wheel as first action after switching the X
session back.
But I had been playing stuntrally with the joystick before I noticed the
mouse wheel stopped working. Maybe plugging in the Joystick is related
again....dunno if that guessing helps you, if not, I'm sorry for the
noise.
Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57020
; Package
emacs
.
(Tue, 09 Aug 2022 00:26:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 57020 <at> debbugs.gnu.org (full text, mbox):
Michael Heerdegen <michael_heerdegen <at> web.de> writes:
> again....dunno if that guessing helps you, if not, I'm sorry for the
> noise.
I tested it a bit, and it's really that simple: plugging in or out the
Joystick reliably breaks the mouse wheel in Emacs, and C-M-f2 and back
reliably unbreaks it (this time there was only the tty2 Linux console,
no second X session).
HTH,
Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57020
; Package
emacs
.
(Tue, 09 Aug 2022 00:49:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 57020 <at> debbugs.gnu.org (full text, mbox):
Michael Heerdegen <michael_heerdegen <at> web.de> writes:
> I tested it a bit, and it's really that simple: plugging in or out the
> Joystick reliably breaks the mouse wheel in Emacs, and C-M-f2 and back
> reliably unbreaks it (this time there was only the tty2 Linux console,
> no second X session).
Hmm, very odd. I will try to figure out why this is, thanks.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57020
; Package
emacs
.
(Tue, 09 Aug 2022 03:08:02 GMT)
Full text and
rfc822 format available.
Message #32 received at 57020 <at> debbugs.gnu.org (full text, mbox):
Po Lu <luangruo <at> yahoo.com> writes:
> Hmm, very odd. I will try to figure out why this is, thanks.
Should be fixed now.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57020
; Package
emacs
.
(Tue, 09 Aug 2022 03:49:02 GMT)
Full text and
rfc822 format available.
Message #35 received at 57020 <at> debbugs.gnu.org (full text, mbox):
Po Lu <luangruo <at> yahoo.com> writes:
> > Hmm, very odd. I will try to figure out why this is, thanks.
>
> Should be fixed now.
Indeed, thank you very much!
I quickly tested the recipe with the joystick, and it works as expected
now. No new problems as well (but I tested only one minute so far).
Thanks again,
Michael.
Reply sent
to
Po Lu <luangruo <at> yahoo.com>
:
You have taken responsibility.
(Tue, 09 Aug 2022 05:12:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Michael Heerdegen <michael_heerdegen <at> web.de>
:
bug acknowledged by developer.
(Tue, 09 Aug 2022 05:12:02 GMT)
Full text and
rfc822 format available.
Message #40 received at 57020-done <at> debbugs.gnu.org (full text, mbox):
Michael Heerdegen <michael_heerdegen <at> web.de> writes:
> Indeed, thank you very much!
>
> I quickly tested the recipe with the joystick, and it works as expected
> now. No new problems as well (but I tested only one minute so far).
>
> Thanks again,
>
> Michael.
Any time, thanks for testing. I'm closing this bug.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 06 Sep 2022 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 281 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.