bug#65829: 29.1; pgtk build invalid clickable area in window

bug#65829: 29.1; pgtk build invalid clickable area in window

[Johann Höchtl]

Using the pgtk build. When I click with the mouse (or touchpad) into
the edit area to set point, I receive the following error message:

<tool-bar> <mouse-1> is undefined

This error does not appear for all areas of the edit window but
especially happens at the first two text lines in the edit window.

This behaviour exposes wih emacs -Q


In GNU Emacs 29.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.38,
cairo version 1.17.8)
System Description: EndeavourOS

Configured using:
 'configure --with-pgtk --with-native-compilation=aot --sysconfdir=/etc
 --prefix=/usr --libexecdir=/usr/lib --with-tree-sitter
 --localstatedir=/var --with-cairo --disable-build-details
 --with-harfbuzz --with-libsystemd --with-modules 'CFLAGS=-march=x86-64
 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2
 -Wformat -Werror=format-security -fstack-clash-protection
 -fcf-protection -g
 -ffile-prefix-map=/build/emacs/src=/usr/src/debug/emacs -flto=auto'
 'LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -flto=auto'
 'CXXFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions
 -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security
 -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -g
 -ffile-prefix-map=/build/emacs/src=/usr/src/debug/emacs -flto=auto''

Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ JPEG
JSON LCMS2 LIBOTF LIBSYSTEMD LIBXML2 MODULES NATIVE_COMP NOTIFY INOTIFY
PDUMPER PGTK PNG RSVG SECCOMP SOUND SQLITE3 THREADS TIFF
TOOLKIT_SCROLL_BARS TREE_SITTER WEBP XIM GTK3 ZLIB

Important settings:
  value of $LC_MONETARY: de_AT.UTF-8
  value of $LC_NUMERIC: de_AT.UTF-8
  value of $LC_TIME: de_AT.UTF-8
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  show-paren-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  line-number-mode: t
  indent-tabs-mode: t
  transient-mark-mode: (only . t)
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message mailcap yank-media puny dired
dired-loaddefs rfc822 mml mml-sec password-cache epa derived epg
rfc6068
epg-config gnus-util text-property-search mm-decode mm-bodies mm-encode
mail-parse rfc2231 mailabbrev gmm-utils mailheader sendmail rfc2047
rfc2045 ietf-drums mm-util mail-prsvr mail-utils time-date cl-loaddefs
comp comp-cstr warnings icons subr-x rx cl-seq cl-macs gv cl-extra
help-mode bytecomp byte-compile cl-lib rmc iso-transl tooltip cconv
eldoc paren electric uniquify ediff-hook vc-hooks lisp-float-type
elisp-mode mwheel term/pgtk-win pgtk-win term/common-win pgtk-dnd
tool-bar dnd fontset image regexp-opt fringe tabulated-list replace
newcomment text-mode lisp-mode prog-mode register page tab-bar menu-bar
rfn-eshadow isearch easymenu timer select scroll-bar mouse jit-lock
font-lock syntax font-core term/tty-colors frame minibuffer nadvice seq
simple cl-generic indonesian philippine cham georgian utf-8-lang
misc-lang vietnamese tibetan thai tai-viet lao korean japanese eucjp-ms
cp51932 hebrew greek romanian slovak czech european ethiopic indian
cyrillic chinese composite emoji-zwj charscript charprop case-table
epa-hook jka-cmpr-hook help abbrev obarray oclosure cl-preloaded button
loaddefs theme-loaddefs faces cus-face macroexp files window
text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget keymap hashtable-print-readable backquote threads
dbusbind
inotify dynamic-setting system-font-setting font-render-setting cairo
gtk pgtk lcms2 multi-tty make-network-process native-compile emacs)

Memory information:
((conses 16 78362 5926)
 (symbols 48 7109 0)
 (strings 32 19537 2163)
 (string-bytes 1 571192)
 (vectors 16 15657)
 (vector-slots 8 327228 13186)
 (floats 8 27 48)
 (intervals 56 261 0)
 (buffers 984 11))

bug#65829: 29.1; pgtk build invalid clickable area in window

[Eli Zaretskii]

> From: Johann Höchtl <johann.hoechtl@gmail.com>
> Date: Fri, 08 Sep 2023 20:48:07 +0200
> 
> Using the pgtk build. When I click with the mouse (or touchpad) into
> the edit area to set point, I receive the following error message:
> 
> <tool-bar> <mouse-1> is undefined
> 
> This error does not appear for all areas of the edit window but
> especially happens at the first two text lines in the edit window.

What is this "edit window" you mention in this context?  can you
explain what you mean by that in more detail?

According to the error message, Emacs thinks that you click on the
tool bar.

bug#65829: 29.1; pgtk build invalid clickable area in window

[Eli Zaretskii]

[Please use Reply All to reply, to keep the bug tracker on the CC list.]

> From: Johann Höchtl <johann.hoechtl@gmail.com>
> Date: Fri, 8 Sep 2023 22:29:02 +0200
> 
> The scratch buffer in its associated window ready to be edited. It is impossible to use the mouse and
> set point as the mentioned error message appears.
> 
> If I enter some text, press a few times Enter and thus have some text further down the buffer, clicks
> further down the buffer (more precise: further down from the top window border) work. It seems as
> emacs thinks there is a tab-bar while there is none.
> 
> This behaviour is not just with the scratch buffer but any regular file associated buffer.

You are basically saying that, wherever you click mouse-1, Emacs in
your PGTK build thinks the click was on the tool bar?

Po Lu, do we know about such problems in the PGTK build?

bug#65829: 29.1; pgtk build invalid clickable area in window

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Eli Zaretskii <eliz@gnu.org> writes:

> You are basically saying that, wherever you click mouse-1, Emacs in
> your PGTK build thinks the click was on the tool bar?
>
> Po Lu, do we know about such problems in the PGTK build?

No, we don't.  Johann, have you enabled tool-bar-mode or tab-bar-mode?
Which pertinent variables have you customized?

bug#65829: 29.1; pgtk build invalid clickable area in window

[Johann Höchtl]

On Sat, 2023-09-09 at 14:35 +0800, Po Lu wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > You are basically saying that, wherever you click mouse-1, Emacs in
> > your PGTK build thinks the click was on the tool bar?
> > 
> > Po Lu, do we know about such problems in the PGTK build?
> 
> No, we don't.  Johann, have you enabled tool-bar-mode or tab-bar-
> mode?
> Which pertinent variables have you customized?

While I am aware of tool-bar-mode or tab-bar-mode, the behaviour shows
when starting as emacs -Q, so it shows without any configuration
walking astray from the defaults.

bug#65829: 29.1; pgtk build invalid clickable area in window

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Johann Höchtl <johann.hoechtl@gmail.com> writes:

> On Sat, 2023-09-09 at 14:35 +0800, Po Lu wrote:
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > You are basically saying that, wherever you click mouse-1, Emacs in
>> > your PGTK build thinks the click was on the tool bar?
>> > 
>> > Po Lu, do we know about such problems in the PGTK build?
>> 
>> No, we don't.  Johann, have you enabled tool-bar-mode or tab-bar-
>> mode?
>> Which pertinent variables have you customized?
>
> While I am aware of tool-bar-mode or tab-bar-mode, the behaviour shows
> when starting as emacs -Q, so it shows without any configuration
> walking astray from the defaults.

Thanks.  What if you delete the body of the function
`pgtk_toolkit_position' within pgtkterm.c?

bug#65829: 29.1; pgtk build invalid clickable area in window

[Johann Höchtl]

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

Building Emacs from source is beyond my abilities, I am sorry.

Maybe it is of help that I have fractional scaling enabled - that's the
primary reason for me to use Wayland and the pgtk-build.

 Also note that I did use An Emacs 30.0.50 pgtk-build with aot for maybe
more than a year and did not have this issue. I have this issue after
switching to the officially released Emacs 29.1.

Best, Johann

Am So., 10. Sept. 2023 um 03:02 Uhr schrieb Po Lu <luangruo@yahoo.com>:

> Johann Höchtl <johann.hoechtl@gmail.com> writes:
>
> > On Sat, 2023-09-09 at 14:35 +0800, Po Lu wrote:
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >> > You are basically saying that, wherever you click mouse-1, Emacs in
> >> > your PGTK build thinks the click was on the tool bar?
> >> >
> >> > Po Lu, do we know about such problems in the PGTK build?
> >>
> >> No, we don't.  Johann, have you enabled tool-bar-mode or tab-bar-
> >> mode?
> >> Which pertinent variables have you customized?
> >
> > While I am aware of tool-bar-mode or tab-bar-mode, the behaviour shows
> > when starting as emacs -Q, so it shows without any configuration
> > walking astray from the defaults.
>
> Thanks.  What if you delete the body of the function
> `pgtk_toolkit_position' within pgtkterm.c?
>

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

bug#65829: 29.1; pgtk build invalid clickable area in window

[Eli Zaretskii]

> From: Johann Höchtl <johann.hoechtl@gmail.com>
> Date: Sun, 10 Sep 2023 18:55:23 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, 65829@debbugs.gnu.org
> 
>  Also note that I did use An Emacs 30.0.50 pgtk-build with aot for maybe more than a year and did
> not have this issue. I have this issue after switching to the officially released Emacs 29.1.

I don't understand how you could be using Emacs 30.050 for more than a
year, when Emacs 30 didn't exist before 28 Nov 2022.  And almost all
the changes installed in Emacs 29 are also present in Emacs 30.  Are
you sure you aren't misremembering?  Could it be that the cause was
some update in one of the system components used to build Emacs?

bug#65829: 29.1; pgtk build invalid clickable area in window

[Stefan Kangas]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Johann Höchtl <johann.hoechtl@gmail.com>
>> Date: Sun, 10 Sep 2023 18:55:23 +0200
>> Cc: Eli Zaretskii <eliz@gnu.org>, 65829@debbugs.gnu.org
>>
>>  Also note that I did use An Emacs 30.0.50 pgtk-build with aot for maybe more than a year and did
>> not have this issue. I have this issue after switching to the officially released Emacs 29.1.
>
> I don't understand how you could be using Emacs 30.050 for more than a
> year, when Emacs 30 didn't exist before 28 Nov 2022.  And almost all
> the changes installed in Emacs 29 are also present in Emacs 30.  Are
> you sure you aren't misremembering?  Could it be that the cause was
> some update in one of the system components used to build Emacs?

More information was requested, but none was given within 6 weeks, so
I'm closing this bug.  If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.

bug#65829: 29.1; pgtk build invalid clickable area in window

[Johann Höchtl]

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

I keep this report open as I am still affected by the issue.

There was one question specifically targeting me:

> What if you delete the body of the function

> `pgtk_toolkit_position' within pgtkterm.c?

Sorry, I can't build Emacs myself.

However I can only ascertain that:

I am on Gnome 45 (as of recent) using Wayland and pgtk-build of Emacs
29.1 by Arch distribution. The issue shows also when running emacs -Q.



Am Mo., 23. Okt. 2023 um 22:04 Uhr schrieb Stefan Kangas <
stefankangas@gmail.com>:

> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Johann Höchtl <johann.hoechtl@gmail.com>
> >> Date: Sun, 10 Sep 2023 18:55:23 +0200
> >> Cc: Eli Zaretskii <eliz@gnu.org>, 65829@debbugs.gnu.org
> >>
> >>  Also note that I did use An Emacs 30.0.50 pgtk-build with aot for
> maybe more than a year and did
> >> not have this issue. I have this issue after switching to the
> officially released Emacs 29.1.
> >
> > I don't understand how you could be using Emacs 30.050 for more than a
> > year, when Emacs 30 didn't exist before 28 Nov 2022.  And almost all
> > the changes installed in Emacs 29 are also present in Emacs 30.  Are
> > you sure you aren't misremembering?  Could it be that the cause was
> > some update in one of the system components used to build Emacs?
>
> More information was requested, but none was given within 6 weeks, so
> I'm closing this bug.  If this is still an issue, please reply to this
> email (use "Reply to all" in your email client) and we can reopen the
> bug report.
>

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