* bug#54436: 28.0.91; Only every second mouse wheel scroll is registered @ 2022-03-17 10:47 Urban Duh 2022-03-19 0:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors 0 siblings, 1 reply; 8+ messages in thread From: Urban Duh @ 2022-03-17 10:47 UTC (permalink / raw) To: 54436 [-- Attachment #1: Type: text/plain, Size: 939 bytes --] Only every second mouse wheel scroll move is registered, instead of all of them. This happens when scrolling the text and also when using keybindings (i. e. C-h <wheel-up> is activated only after scrolling twice). The two scrolls do not need to be in quick succession, I can scroll once (and nothing happens), wait for a long time and then the next scroll is registered. Currently using Doom Emacs on Emacs 28.0.91 with native compilation on Arch Linux running GNOME on Xorg, but the same thing can be reproduced in Emacs 29.0.50, on Wayland and in other WMs (I tried Qtile). The same issue exists on Emacs without any customizations (just installing emacs-git or emacs-gcc-wayland-devel-bin from AUR without Doom). Emacs 27 (package emacs from Arch Extra repository) does not have this issue and works fine. I am new to Emacs, so I'm not completely sure what other info I should provide, so do not hesitate to contact me for more info. [-- Attachment #2: Type: text/html, Size: 1019 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#54436: 28.0.91; Only every second mouse wheel scroll is registered 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 0 siblings, 1 reply; 8+ messages in thread From: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-03-19 0:52 UTC (permalink / raw) To: Urban Duh; +Cc: 54436 Urban Duh <urby.duh@gmail.com> writes: > Only every second mouse wheel scroll move is registered, instead of all of > them. This happens when scrolling the text and also when using > keybindings (i. e. C-h <wheel-up> is activated only after scrolling > twice). The two scrolls do not need to be in quick succession, I can > scroll once (and nothing happens), wait for a long time and then the > next scroll is registered. > > Currently using Doom Emacs on Emacs 28.0.91 with native compilation on > Arch Linux running GNOME on Xorg, but the same thing can be reproduced > in Emacs 29.0.50, on Wayland and in other WMs (I tried Qtile). The same > issue exists on Emacs without any customizations (just installing > emacs-git or emacs-gcc-wayland-devel-bin from AUR without Doom). Emacs > 27 (package emacs from Arch Extra repository) does not have this issue > and works fine. > > I am new to Emacs, so I'm not completely sure what other info I should > provide, so do not hesitate to contact me for more info. Are you running PGTK? It's not present in the official pretests of Emacs 28, but several very irresponsible individuals are haphazardly merging the code from Emacs 29 into Emacs 28, and then distributing packages labeled "enhanced or "wayland" on platforms such as the AUR. If you're running X, don't use PGTK. Here's the problem in this specific case: GTK uses the X input extension to detect mouse wheel movement, which relies on keeping the mouse wheel "valuators" in synch with the X server, and calculating the difference between GTK's own record of the valuator values and the X server's reported values every time a valuator changes. This is made complicated by the fact that an X window does not get events to update the valuators unless it has the grab, or the mouse pointer is on top of it. So, every time the mouse enters a window, GTK marks the valuator as invalid, after which two consecutive wheel events are required before any more wheel movement will be recorded: one to obtain the current value of the valuator, and another one so that the distance the wheel has moved can be calculated. Selecting for input extension events results in the corresponding core event mask being deactivated on the window. Some very smart window managers select for core wheel events (which are just button events) on the WM frame window, or the root window, and since there is no core button event mask on the Emacs frame window when GTK is using the input extension, the button events representing wheel movement get propagated up to the frame (or root) window, and that causes a grab to be activated and then deactivated, generating incorrect entry events, which then cause GTK to invalidate its own record of the scroll valuators, and causes wheel movement to be ignored at random. The solution is to use the official build of Emacs 28, and to not use PGTK on X Windows if you want to run Emacs 29. ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#54436: 28.0.91; Only every second mouse wheel scroll is registered 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 0 siblings, 1 reply; 8+ messages in thread From: Lars Ingebrigtsen @ 2022-03-19 14:18 UTC (permalink / raw) To: Po Lu; +Cc: Urban Duh, 54436 Po Lu <luangruo@yahoo.com> writes: > Are you running PGTK? It's not present in the official pretests of > Emacs 28, but several very irresponsible individuals are haphazardly > merging the code from Emacs 29 into Emacs 28, and then distributing > packages labeled "enhanced or "wayland" on platforms such as the AUR. Well, it's free software, so people can do what they want. But bugs in these Frankenstein Emacs versions should be reported to the people that distribute them, which in this case is Arch Linux. > The solution is to use the official build of Emacs 28, and to not use > PGTK on X Windows if you want to run Emacs 29. So there doesn't seem to be anything to be done on the Emacs side here, and I'm therefore closing this bug report. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#54436: 28.0.91; Only every second mouse wheel scroll is registered 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 0 siblings, 1 reply; 8+ messages in thread From: Urban Duh @ 2022-03-20 16:55 UTC (permalink / raw) To: Lars Ingebrigtsen; +Cc: Po Lu, 54436 [-- Attachment #1: Type: text/plain, Size: 1653 bytes --] 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, 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? On Sat, 19 Mar 2022 at 15:18, Lars Ingebrigtsen <larsi@gnus.org> wrote: > Po Lu <luangruo@yahoo.com> writes: > > > Are you running PGTK? It's not present in the official pretests of > > Emacs 28, but several very irresponsible individuals are haphazardly > > merging the code from Emacs 29 into Emacs 28, and then distributing > > packages labeled "enhanced or "wayland" on platforms such as the AUR. > > Well, it's free software, so people can do what they want. But bugs in > these Frankenstein Emacs versions should be reported to the people that > distribute them, which in this case is Arch Linux. > > > The solution is to use the official build of Emacs 28, and to not use > > PGTK on X Windows if you want to run Emacs 29. > > So there doesn't seem to be anything to be done on the Emacs side here, > and I'm therefore closing this bug report. > > -- > (domestic pets only, the antidote for overdose, milk.) > bloggy blog: http://lars.ingebrigtsen.no > [-- Attachment #2: Type: text/html, Size: 2218 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#54436: 28.0.91; Only every second mouse wheel scroll is registered 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 0 siblings, 1 reply; 8+ messages in thread From: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-03-21 2:13 UTC (permalink / raw) To: Urban Duh; +Cc: Lars Ingebrigtsen, 54436 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. ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#54436: 28.0.91; Only every second mouse wheel scroll is registered 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 2022-03-21 11:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors 0 siblings, 1 reply; 8+ messages in thread From: Urban Duh @ 2022-03-21 9:20 UTC (permalink / raw) To: Po Lu; +Cc: Lars Ingebrigtsen, 54436 [-- 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 --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#54436: 28.0.91; Only every second mouse wheel scroll is registered 2022-03-21 9:20 ` Urban Duh @ 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 0 siblings, 1 reply; 8+ messages in thread From: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-03-21 11:05 UTC (permalink / raw) To: Urban Duh; +Cc: Lars Ingebrigtsen, 54436 Urban Duh <urby.duh@gmail.com> writes: >> 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). What happens if you set mwheel-coalesce-scroll-events to nil? ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#54436: 28.0.91; Only every second mouse wheel scroll is registered 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 0 siblings, 0 replies; 8+ messages in thread From: Urban Duh @ 2022-03-22 13:59 UTC (permalink / raw) To: Po Lu; +Cc: Lars Ingebrigtsen, 54436 [-- Attachment #1: Type: text/plain, Size: 1095 bytes --] This makes scrolling behave as it should on Wayland. On X however, Emacs now receives too many scroll events per scroll on certain mouses. On Logitech MX master 3, every mouse wheel scroll is registered as a double or triple scroll. I would guess this has something to do with its scroll wheel, since it has an electromagnetic scroll wheel. Such issues do not exists on Emacs 28 though, but I guess I could probably make it usable by binding triple scroll to normal scroll. On Mon, 21 Mar 2022 at 12:05, Po Lu <luangruo@yahoo.com> wrote: > Urban Duh <urby.duh@gmail.com> writes: > > >> 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). > > What happens if you set mwheel-coalesce-scroll-events to nil? > [-- Attachment #2: Type: text/html, Size: 1637 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2022-03-22 13:59 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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
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.