bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[John Hurst]

Sorry if this is the wrong place to post a bug, but I tried the M-x report-emacs-bug, and it just said "Cannot open load file: No such file or directory, emacs-19"??

The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
   Emacs*geometry: 100x40+1900+0
end a default-frame-alist of
  Value:
  ((font . "Monospace-10")
   (height . 42)
   (width . 90)
   (tool-bar-lines . 0)
   (menu-bar-lines . 1)
   (top . 0)
   (left . 1200))
  Original value was nil
set up by my .emacs file.

Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.

I can send the .emacs file if needed, but note that "emacs -D' also gives the same default size of 20 x 9, so I don't think it is a problem with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.

Any insights gratefully received.

cheers,
-- John Hurst
--
-- ajh AT ajhurst DOT org                       ~ ~~~&#:
--  (mob 0407 569 292)              _..___  ---____@___H__
-- (local)  ajh.co                  |_____[_|_________[__]_
-- (global) ajhurst.org              oo oo  oo O--O--O o=o
--
-- Hurst's Third Law of telecommunications: 
--    ISPs are not as smart as spammers

bug#73245: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[John Hurst]

Sorry, forgot to add, in case it is relevant, that when run from the command line, emacs gives many messages of the form:
  (emacs:1556302): Gtk-CRITICAL **: 12:40:47.974: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed

This means nothing to me, but presumably is important?

cheers,
-- John Hurst
--
-- ajh AT ajhurst DOT org                       ~ ~~~&#:
--  (mob 0407 569 292)              _..___  ---____@___H__
-- (local)  ajh.co                  |_____[_|_________[__]_
-- (global) ajhurst.org              oo oo  oo O--O--O o=o
--
-- Hurst's Third Law of telecommunications: 
--    ISPs are not as smart as spammers

On Sat, 14 Sep 2024, at 12:42, John Hurst wrote:
> Sorry if this is the wrong place to post a bug, but I tried the M-x 
> report-emacs-bug, and it just said "Cannot open load file: No such file 
> or directory, emacs-19"??
>
> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is 
> that the initial frame has width x height of 20 x 9, even though I have 
> a .Xresources file containing
>    Emacs*geometry: 100x40+1900+0
> end a default-frame-alist of
>   Value:
>   ((font . "Monospace-10")
>    (height . 42)
>    (width . 90)
>    (tool-bar-lines . 0)
>    (menu-bar-lines . 1)
>    (top . 0)
>    (left . 1200))
>   Original value was nil
> set up by my .emacs file.
>
> Using either the pull-down File->New Frame, or C-x 5 2, both generate 
> new frames of the 20 x 9 size.
>
> I can send the .emacs file if needed, but note that "emacs -D' also 
> gives the same default size of 20 x 9, so I don't think it is a problem 
> with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.
>
> Any insights gratefully received.
>
> cheers,
> -- John Hurst
> --
> -- ajh AT ajhurst DOT org                       ~ ~~~&#:
> --  (mob 0407 569 292)              _..___  ---____@___H__
> -- (local)  ajh.co                  |_____[_|_________[__]_
> -- (global) ajhurst.org              oo oo  oo O--O--O o=o
> --
> -- Hurst's Third Law of telecommunications: 
> --    ISPs are not as smart as spammers

bug#73245: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[Eli Zaretskii]

merge 73245 73244
thanks

> Date: Sat, 14 Sep 2024 12:45:08 +1000
> From: "John Hurst" <ajh@ajhurst.org>
> 
> Sorry, forgot to add, in case it is relevant, that when run from the command line, emacs gives many messages of the form:
>   (emacs:1556302): Gtk-CRITICAL **: 12:40:47.974: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed
> 
> This means nothing to me, but presumably is important?

For some reason, debbugs created a new bug from this, so I'm now
merging them.

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[Eli Zaretskii]

> Date: Sat, 14 Sep 2024 12:42:50 +1000
> From: "John Hurst" <ajh@ajhurst.org>
> 
> Sorry if this is the wrong place to post a bug, but I tried the M-x report-emacs-bug, and it just said "Cannot open load file: No such file or directory, emacs-19"??

Probably some of your customizations point to such a file or
directory.  Please take a good look at your init files.

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[Eli Zaretskii]

> Date: Sat, 14 Sep 2024 12:42:50 +1000
> From: "John Hurst" <ajh@ajhurst.org>
> 
> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
>    Emacs*geometry: 100x40+1900+0
> end a default-frame-alist of
>   Value:
>   ((font . "Monospace-10")
>    (height . 42)
>    (width . 90)
>    (tool-bar-lines . 0)
>    (menu-bar-lines . 1)
>    (top . 0)
>    (left . 1200))
>   Original value was nil
> set up by my .emacs file.
> 
> Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.
> 
> I can send the .emacs file if needed, but note that "emacs -D' also gives the same default size of 20 x 9, so I don't think it is a problem with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.

Po Lu, any comments or suggestions?

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

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

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Sat, 14 Sep 2024 12:42:50 +1000
>> From: "John Hurst" <ajh@ajhurst.org>
>> 
>> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
>>    Emacs*geometry: 100x40+1900+0
>> end a default-frame-alist of
>>   Value:
>>   ((font . "Monospace-10")
>>    (height . 42)
>>    (width . 90)
>>    (tool-bar-lines . 0)
>>    (menu-bar-lines . 1)
>>    (top . 0)
>>    (left . 1200))
>>   Original value was nil
>> set up by my .emacs file.
>> 
>> Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.
>> 
>> I can send the .emacs file if needed, but note that "emacs -D' also gives the same default size of 20 x 9, so I don't think it is a problem with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.
>
> Po Lu, any comments or suggestions?

From what I've heard, the culprit is rather the upgrade to Ubuntu 24.04
than to Emacs 29, and the problem will disappear if Emacs is configured
with another toolkit than GTK.

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[Eli Zaretskii]

> From: Po Lu <luangruo@yahoo.com>
> Cc: "John Hurst" <ajh@ajhurst.org>,  73244@debbugs.gnu.org
> Date: Sat, 21 Sep 2024 17:58:00 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Date: Sat, 14 Sep 2024 12:42:50 +1000
> >> From: "John Hurst" <ajh@ajhurst.org>
> >> 
> >> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
> >>    Emacs*geometry: 100x40+1900+0
> >> end a default-frame-alist of
> >>   Value:
> >>   ((font . "Monospace-10")
> >>    (height . 42)
> >>    (width . 90)
> >>    (tool-bar-lines . 0)
> >>    (menu-bar-lines . 1)
> >>    (top . 0)
> >>    (left . 1200))
> >>   Original value was nil
> >> set up by my .emacs file.
> >> 
> >> Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.
> >> 
> >> I can send the .emacs file if needed, but note that "emacs -D' also gives the same default size of 20 x 9, so I don't think it is a problem with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.
> >
> > Po Lu, any comments or suggestions?
> 
> >From what I've heard, the culprit is rather the upgrade to Ubuntu 24.04
> than to Emacs 29, and the problem will disappear if Emacs is configured
> with another toolkit than GTK.

Does it mean that GTK which comes with Ubuntu 24.04 is unusable with
Emacs?  What exactly in GTK causes this?

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[Eli Zaretskii]

Ping!

> Cc: ajh@ajhurst.org, 73244@debbugs.gnu.org
> Date: Sat, 21 Sep 2024 14:19:12 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: Po Lu <luangruo@yahoo.com>
> > Cc: "John Hurst" <ajh@ajhurst.org>,  73244@debbugs.gnu.org
> > Date: Sat, 21 Sep 2024 17:58:00 +0800
> > 
> > Eli Zaretskii <eliz@gnu.org> writes:
> > 
> > >> Date: Sat, 14 Sep 2024 12:42:50 +1000
> > >> From: "John Hurst" <ajh@ajhurst.org>
> > >> 
> > >> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
> > >>    Emacs*geometry: 100x40+1900+0
> > >> end a default-frame-alist of
> > >>   Value:
> > >>   ((font . "Monospace-10")
> > >>    (height . 42)
> > >>    (width . 90)
> > >>    (tool-bar-lines . 0)
> > >>    (menu-bar-lines . 1)
> > >>    (top . 0)
> > >>    (left . 1200))
> > >>   Original value was nil
> > >> set up by my .emacs file.
> > >> 
> > >> Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.
> > >> 
> > >> I can send the .emacs file if needed, but note that "emacs -D' also gives the same default size of 20 x 9, so I don't think it is a problem with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.
> > >
> > > Po Lu, any comments or suggestions?
> > 
> > >From what I've heard, the culprit is rather the upgrade to Ubuntu 24.04
> > than to Emacs 29, and the problem will disappear if Emacs is configured
> > with another toolkit than GTK.
> 
> Does it mean that GTK which comes with Ubuntu 24.04 is unusable with
> Emacs?  What exactly in GTK causes this?
> 
> 
> 
> 

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

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

Eli Zaretskii <eliz@gnu.org> writes:

> Ping!
>
>> Cc: ajh@ajhurst.org, 73244@debbugs.gnu.org
>> Date: Sat, 21 Sep 2024 14:19:12 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> 
>> > From: Po Lu <luangruo@yahoo.com>
>> > Cc: "John Hurst" <ajh@ajhurst.org>,  73244@debbugs.gnu.org
>> > Date: Sat, 21 Sep 2024 17:58:00 +0800
>> > 
>> > Eli Zaretskii <eliz@gnu.org> writes:
>> > 
>> > >> Date: Sat, 14 Sep 2024 12:42:50 +1000
>> > >> From: "John Hurst" <ajh@ajhurst.org>
>> > >> 
>> > >> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
>> > >>    Emacs*geometry: 100x40+1900+0
>> > >> end a default-frame-alist of
>> > >>   Value:
>> > >>   ((font . "Monospace-10")
>> > >>    (height . 42)
>> > >>    (width . 90)
>> > >>    (tool-bar-lines . 0)
>> > >>    (menu-bar-lines . 1)
>> > >>    (top . 0)
>> > >>    (left . 1200))
>> > >>   Original value was nil
>> > >> set up by my .emacs file.
>> > >> 
>> > >> Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.
>> > >> 
>> > >> I can send the .emacs file if needed, but note that "emacs -D' also gives the same default size of 20 x 9, so I don't think it is a problem with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.
>> > >
>> > > Po Lu, any comments or suggestions?
>> > 
>> > >From what I've heard, the culprit is rather the upgrade to Ubuntu 24.04
>> > than to Emacs 29, and the problem will disappear if Emacs is configured
>> > with another toolkit than GTK.
>> 
>> Does it mean that GTK which comes with Ubuntu 24.04 is unusable with
>> Emacs?  What exactly in GTK causes this?

Sorry for the belated response.  We don't know yet, and it's not an
issue with GTK, but with some past update to the window manager.

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[Eli Zaretskii]

> From: Po Lu <luangruo@yahoo.com>
> Cc: ajh@ajhurst.org,  73244@debbugs.gnu.org
> Date: Sat, 05 Oct 2024 19:05:30 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Ping!
> >
> >> Cc: ajh@ajhurst.org, 73244@debbugs.gnu.org
> >> Date: Sat, 21 Sep 2024 14:19:12 +0300
> >> From: Eli Zaretskii <eliz@gnu.org>
> >> 
> >> > From: Po Lu <luangruo@yahoo.com>
> >> > Cc: "John Hurst" <ajh@ajhurst.org>,  73244@debbugs.gnu.org
> >> > Date: Sat, 21 Sep 2024 17:58:00 +0800
> >> > 
> >> > Eli Zaretskii <eliz@gnu.org> writes:
> >> > 
> >> > >> Date: Sat, 14 Sep 2024 12:42:50 +1000
> >> > >> From: "John Hurst" <ajh@ajhurst.org>
> >> > >> 
> >> > >> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
> >> > >>    Emacs*geometry: 100x40+1900+0
> >> > >> end a default-frame-alist of
> >> > >>   Value:
> >> > >>   ((font . "Monospace-10")
> >> > >>    (height . 42)
> >> > >>    (width . 90)
> >> > >>    (tool-bar-lines . 0)
> >> > >>    (menu-bar-lines . 1)
> >> > >>    (top . 0)
> >> > >>    (left . 1200))
> >> > >>   Original value was nil
> >> > >> set up by my .emacs file.
> >> > >> 
> >> > >> Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.
> >> > >> 
> >> > >> I can send the .emacs file if needed, but note that "emacs -D' also gives the same default size of 20 x 9, so I don't think it is a problem with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.
> >> > >
> >> > > Po Lu, any comments or suggestions?
> >> > 
> >> > >From what I've heard, the culprit is rather the upgrade to Ubuntu 24.04
> >> > than to Emacs 29, and the problem will disappear if Emacs is configured
> >> > with another toolkit than GTK.
> >> 
> >> Does it mean that GTK which comes with Ubuntu 24.04 is unusable with
> >> Emacs?  What exactly in GTK causes this?
> 
> Sorry for the belated response.  We don't know yet, and it's not an
> issue with GTK, but with some past update to the window manager.

How should we proceed with this bug, then?

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[John Hurst]

Do you need any more input from me?

I have noticed a few other reports of similar bugs, so I would be surprised if it was only me.

cheers,
-- John Hurst
--
-- ajh AT ajhurst DOT org                       ~ ~~~&#:
--  (mob 0407 569 292)              _..___  ---____@___H__
-- (local)  ajh.co                  |_____[_|_________[__]_
-- (global) ajhurst.org              oo oo  oo O--O--O o=o
--
-- Hurst's Third Law of telecommunications: 
--    ISPs are not as smart as spammers

On Sat, 12 Oct 2024, at 22:48, Eli Zaretskii wrote:
>> From: Po Lu <luangruo@yahoo.com>
>> Cc: ajh@ajhurst.org,  73244@debbugs.gnu.org
>> Date: Sat, 05 Oct 2024 19:05:30 +0800
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > Ping!
>> >
>> >> Cc: ajh@ajhurst.org, 73244@debbugs.gnu.org
>> >> Date: Sat, 21 Sep 2024 14:19:12 +0300
>> >> From: Eli Zaretskii <eliz@gnu.org>
>> >> 
>> >> > From: Po Lu <luangruo@yahoo.com>
>> >> > Cc: "John Hurst" <ajh@ajhurst.org>,  73244@debbugs.gnu.org
>> >> > Date: Sat, 21 Sep 2024 17:58:00 +0800
>> >> > 
>> >> > Eli Zaretskii <eliz@gnu.org> writes:
>> >> > 
>> >> > >> Date: Sat, 14 Sep 2024 12:42:50 +1000
>> >> > >> From: "John Hurst" <ajh@ajhurst.org>
>> >> > >> 
>> >> > >> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
>> >> > >>    Emacs*geometry: 100x40+1900+0
>> >> > >> end a default-frame-alist of
>> >> > >>   Value:
>> >> > >>   ((font . "Monospace-10")
>> >> > >>    (height . 42)
>> >> > >>    (width . 90)
>> >> > >>    (tool-bar-lines . 0)
>> >> > >>    (menu-bar-lines . 1)
>> >> > >>    (top . 0)
>> >> > >>    (left . 1200))
>> >> > >>   Original value was nil
>> >> > >> set up by my .emacs file.
>> >> > >> 
>> >> > >> Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.
>> >> > >> 
>> >> > >> I can send the .emacs file if needed, but note that "emacs -D' also gives the same default size of 20 x 9, so I don't think it is a problem with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.
>> >> > >
>> >> > > Po Lu, any comments or suggestions?
>> >> > 
>> >> > >From what I've heard, the culprit is rather the upgrade to Ubuntu 24.04
>> >> > than to Emacs 29, and the problem will disappear if Emacs is configured
>> >> > with another toolkit than GTK.
>> >> 
>> >> Does it mean that GTK which comes with Ubuntu 24.04 is unusable with
>> >> Emacs?  What exactly in GTK causes this?
>> 
>> Sorry for the belated response.  We don't know yet, and it's not an
>> issue with GTK, but with some past update to the window manager.
>
> How should we proceed with this bug, then?

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

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

"John Hurst" <ajh@ajhurst.org> writes:

> Do you need any more input from me?
>
> I have noticed a few other reports of similar bugs, so I would be
> surprised if it was only me.
>
> cheers,
> -- John Hurst
> --
> -- ajh AT ajhurst DOT org                       ~ ~~~&#:
> --  (mob 0407 569 292)              _..___  ---____@___H__
> -- (local)  ajh.co                  |_____[_|_________[__]_
> -- (global) ajhurst.org              oo oo  oo O--O--O o=o
> --
> -- Hurst's Third Law of telecommunications: 
> --    ISPs are not as smart as spammers
>
> On Sat, 12 Oct 2024, at 22:48, Eli Zaretskii wrote:
>>> From: Po Lu <luangruo@yahoo.com>
>>> Cc: ajh@ajhurst.org,  73244@debbugs.gnu.org
>>> Date: Sat, 05 Oct 2024 19:05:30 +0800
>>> 
>>> Eli Zaretskii <eliz@gnu.org> writes:
>>> 
>>> > Ping!
>>> >
>>> >> Cc: ajh@ajhurst.org, 73244@debbugs.gnu.org
>>> >> Date: Sat, 21 Sep 2024 14:19:12 +0300
>>> >> From: Eli Zaretskii <eliz@gnu.org>
>>> >> 
>>> >> > From: Po Lu <luangruo@yahoo.com>
>>> >> > Cc: "John Hurst" <ajh@ajhurst.org>,  73244@debbugs.gnu.org
>>> >> > Date: Sat, 21 Sep 2024 17:58:00 +0800
>>> >> > 
>>> >> > Eli Zaretskii <eliz@gnu.org> writes:
>>> >> > 
>>> >> > >> Date: Sat, 14 Sep 2024 12:42:50 +1000
>>> >> > >> From: "John Hurst" <ajh@ajhurst.org>
>>> >> > >> 
>>> >> > >> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
>>> >> > >>    Emacs*geometry: 100x40+1900+0
>>> >> > >> end a default-frame-alist of
>>> >> > >>   Value:
>>> >> > >>   ((font . "Monospace-10")
>>> >> > >>    (height . 42)
>>> >> > >>    (width . 90)
>>> >> > >>    (tool-bar-lines . 0)
>>> >> > >>    (menu-bar-lines . 1)
>>> >> > >>    (top . 0)
>>> >> > >>    (left . 1200))
>>> >> > >>   Original value was nil
>>> >> > >> set up by my .emacs file.
>>> >> > >> 
>>> >> > >> Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.
>>> >> > >> 
>>> >> > >> I can send the .emacs file if needed, but note that "emacs -D' also gives the same default size of 20 x 9, so I don't think it is a problem with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.
>>> >> > >
>>> >> > > Po Lu, any comments or suggestions?
>>> >> > 
>>> >> > >From what I've heard, the culprit is rather the upgrade to Ubuntu 24.04
>>> >> > than to Emacs 29, and the problem will disappear if Emacs is configured
>>> >> > with another toolkit than GTK.
>>> >> 
>>> >> Does it mean that GTK which comes with Ubuntu 24.04 is unusable with
>>> >> Emacs?  What exactly in GTK causes this?
>>> 
>>> Sorry for the belated response.  We don't know yet, and it's not an
>>> issue with GTK, but with some past update to the window manager.
>>
>> How should we proceed with this bug, then?

No, I think the right person to contact is Martin, who devoted many
weeks to investigating the matter on emacs-devel.

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[Eli Zaretskii]

> From: Po Lu <luangruo@yahoo.com>
> Cc: "Eli Zaretskii" <eliz@gnu.org>,  73244@debbugs.gnu.org
> Date: Mon, 14 Oct 2024 07:33:44 +0800
> 
> "John Hurst" <ajh@ajhurst.org> writes:
> 
> > Do you need any more input from me?
> >
> > I have noticed a few other reports of similar bugs, so I would be
> > surprised if it was only me.
> >
> > cheers,
> > -- John Hurst
> > --
> > -- ajh AT ajhurst DOT org                       ~ ~~~&#:
> > --  (mob 0407 569 292)              _..___  ---____@___H__
> > -- (local)  ajh.co                  |_____[_|_________[__]_
> > -- (global) ajhurst.org              oo oo  oo O--O--O o=o
> > --
> > -- Hurst's Third Law of telecommunications: 
> > --    ISPs are not as smart as spammers
> >
> > On Sat, 12 Oct 2024, at 22:48, Eli Zaretskii wrote:
> >>> From: Po Lu <luangruo@yahoo.com>
> >>> Cc: ajh@ajhurst.org,  73244@debbugs.gnu.org
> >>> Date: Sat, 05 Oct 2024 19:05:30 +0800
> >>> 
> >>> Eli Zaretskii <eliz@gnu.org> writes:
> >>> 
> >>> > Ping!
> >>> >
> >>> >> Cc: ajh@ajhurst.org, 73244@debbugs.gnu.org
> >>> >> Date: Sat, 21 Sep 2024 14:19:12 +0300
> >>> >> From: Eli Zaretskii <eliz@gnu.org>
> >>> >> 
> >>> >> > From: Po Lu <luangruo@yahoo.com>
> >>> >> > Cc: "John Hurst" <ajh@ajhurst.org>,  73244@debbugs.gnu.org
> >>> >> > Date: Sat, 21 Sep 2024 17:58:00 +0800
> >>> >> > 
> >>> >> > Eli Zaretskii <eliz@gnu.org> writes:
> >>> >> > 
> >>> >> > >> Date: Sat, 14 Sep 2024 12:42:50 +1000
> >>> >> > >> From: "John Hurst" <ajh@ajhurst.org>
> >>> >> > >> 
> >>> >> > >> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
> >>> >> > >>    Emacs*geometry: 100x40+1900+0
> >>> >> > >> end a default-frame-alist of
> >>> >> > >>   Value:
> >>> >> > >>   ((font . "Monospace-10")
> >>> >> > >>    (height . 42)
> >>> >> > >>    (width . 90)
> >>> >> > >>    (tool-bar-lines . 0)
> >>> >> > >>    (menu-bar-lines . 1)
> >>> >> > >>    (top . 0)
> >>> >> > >>    (left . 1200))
> >>> >> > >>   Original value was nil
> >>> >> > >> set up by my .emacs file.
> >>> >> > >> 
> >>> >> > >> Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.
> >>> >> > >> 
> >>> >> > >> I can send the .emacs file if needed, but note that "emacs -D' also gives the same default size of 20 x 9, so I don't think it is a problem with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.
> >>> >> > >
> >>> >> > > Po Lu, any comments or suggestions?
> >>> >> > 
> >>> >> > >From what I've heard, the culprit is rather the upgrade to Ubuntu 24.04
> >>> >> > than to Emacs 29, and the problem will disappear if Emacs is configured
> >>> >> > with another toolkit than GTK.
> >>> >> 
> >>> >> Does it mean that GTK which comes with Ubuntu 24.04 is unusable with
> >>> >> Emacs?  What exactly in GTK causes this?
> >>> 
> >>> Sorry for the belated response.  We don't know yet, and it's not an
> >>> issue with GTK, but with some past update to the window manager.
> >>
> >> How should we proceed with this bug, then?
> 
> No, I think the right person to contact is Martin, who devoted many
> weeks to investigating the matter on emacs-devel.

Martin, any suggestions or ideas?

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

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

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

 >>>>>>>>>> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
 >>>>>>>>>>     Emacs*geometry: 100x40+1900+0
 >>>>>>>>>> end a default-frame-alist of
 >>>>>>>>>>    Value:
 >>>>>>>>>>    ((font . "Monospace-10")
 >>>>>>>>>>     (height . 42)
 >>>>>>>>>>     (width . 90)
 >>>>>>>>>>     (tool-bar-lines . 0)
 >>>>>>>>>>     (menu-bar-lines . 1)
 >>>>>>>>>>     (top . 0)
 >>>>>>>>>>     (left . 1200))
 >>>>>>>>>>    Original value was nil
 >>>>>>>>>> set up by my .emacs file.
 >>>>>>>>>>
 >>>>>>>>>> Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.
...
 > Martin, any suggestions or ideas?

Welcome to the club, John.  Some standard questions:

- You're using GNOME desktop and the mutter window manager.  Right?  If
   so, what does mutter --version tell?  Can you try setting the
   environment variable MUTTER_DEBUG="geometry" and then look into stderr
   whether anything shows up there at all?  If so, we could try to
   investigate further.

- Is your screen scaled?

- What does evaluating (frame-geometry) tell for the first frame?  What
   do (frame-char-height) and (frame-char-width) evaluate too?

- Can you build with other toolkits?  GTK2, Lucid, Motif or with the
   --with-x-toolkit=no option?

- Can you build with the attached patch?  If so, please evaluate the
   form (frame--size-history) and post the contents of the the buffer
   *frame-size-history* here.

Thanks, martin

[-- Attachment #2: gtkutil-reject-2024-10-01.diff --]
[-- Type: text/x-patch, Size: 3891 bytes --]

diff --git a/src/frame.c b/src/frame.c
index 7f4bf274ad9..6b6f6aa3c5c 100644
--- a/src/frame.c
+++ b/src/frame.c
@@ -6769,7 +6769,7 @@ focus (where a frame immediately loses focus when it's left by the mouse
 
 The function `frame--size-history' displays the value of this variable
 in a more readable form.  */);
-    frame_size_history = Qnil;
+  frame_size_history = Fcons (make_fixnum (100), Qnil);
 
   DEFVAR_BOOL ("tooltip-reuse-hidden-frame", tooltip_reuse_hidden_frame,
 	       doc: /* Non-nil means reuse hidden tooltip frames.
diff --git a/src/gtkutil.c b/src/gtkutil.c
index d57627f152f..a02be51600e 100644
--- a/src/gtkutil.c
+++ b/src/gtkutil.c
@@ -1129,11 +1129,48 @@ xg_set_geometry (struct frame *f)
     }
 }
 
+static struct frame *last_resize_frame = NULL;
+static int last_resize_height = -1;
+static int last_resize_width = -1;
+static int last_resize_count = 0;
+
 /** Function to handle resize of native frame F to WIDTH and HEIGHT
     pixels after we got a ConfigureNotify event.  */
 void
 xg_frame_resized (struct frame *f, int width, int height)
 {
+#ifndef HAVE_PGTK
+  if (f == last_resize_frame
+      && (width != ((last_resize_width * xg_get_scale (f))
+		    - FRAME_TOOLBAR_WIDTH (f))
+	  || height != ((last_resize_height * xg_get_scale (f))
+			- FRAME_MENUBAR_HEIGHT (f)
+			- FRAME_TOOLBAR_HEIGHT (f)))
+      && last_resize_count <= 3)
+    /* We did not get what we wanted, retry.  */
+    {
+      if (CONSP (frame_size_history))
+	frame_size_history_extra
+	  (f, build_string ("xg_frame_resized, rejected"),
+	   FRAME_PIXEL_WIDTH (f), FRAME_PIXEL_HEIGHT (f), width, height,
+	   last_resize_width, last_resize_height);
+
+      gtk_window_resize (GTK_WINDOW (FRAME_GTK_OUTER_WIDGET (f)),
+			 last_resize_width, last_resize_height);
+
+      last_resize_count++;
+
+      return;
+    }
+  else
+    /* We either got what we asked for or lost the battle.  */
+    {
+      last_resize_frame = NULL;
+      last_resize_height = -1;
+      last_resize_width = -1;
+      last_resize_count = 0;
+    }
+#endif
   /* Ignore case where size of native rectangle didn't change.  */
   if (width != FRAME_PIXEL_WIDTH (f)
       || height != FRAME_PIXEL_HEIGHT (f)
@@ -1297,19 +1334,20 @@ xg_frame_set_char_size (struct frame *f, int width, int height)
   else
     {
 #ifndef HAVE_PGTK
+      last_resize_frame = f;
+      last_resize_width = outer_width;
+      last_resize_height = outer_height;
+      last_resize_count = 0;
+
       gtk_window_resize (GTK_WINDOW (FRAME_GTK_OUTER_WIDGET (f)),
 			 outer_width, outer_height);
 #else
       if (FRAME_GTK_OUTER_WIDGET (f))
-	{
-	  gtk_window_resize (GTK_WINDOW (FRAME_GTK_OUTER_WIDGET (f)),
-			     outer_width, outer_height);
-	}
+	gtk_window_resize (GTK_WINDOW (FRAME_GTK_OUTER_WIDGET (f)),
+			   outer_width, outer_height);
       else
-	{
-	  gtk_widget_set_size_request (FRAME_GTK_WIDGET (f),
-				       outer_width, outer_height);
-	}
+	gtk_widget_set_size_request (FRAME_GTK_WIDGET (f),
+				     outer_width, outer_height);
 #endif
       fullscreen = Qnil;
     }
@@ -1327,10 +1365,17 @@ xg_frame_set_char_size (struct frame *f, int width, int height)
   if (FRAME_VISIBLE_P (f) && !was_visible)
     {
       if (CONSP (frame_size_history))
-	frame_size_history_extra
-	  (f, build_string ("xg_frame_set_char_size, visible"),
-	   FRAME_PIXEL_WIDTH (f), FRAME_PIXEL_HEIGHT (f), width, height,
-	   f->new_width, f->new_height);
+	{
+	  frame_size_history_extra
+	    (f, build_string ("xg_frame_set_char_size, visible"),
+	     FRAME_PIXEL_WIDTH (f), FRAME_PIXEL_HEIGHT (f), width, height,
+	     f->new_width, f->new_height);
+
+	  if (gwidth > 0 || gheight > 0)
+	    frame_size_history_extra
+	      (f, build_string (" +values"), gwidth, gheight,
+	       outer_width, outer_height, -1, -1);
+	}
 
       /* Must call this to flush out events */
       (void)gtk_events_pending ();

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

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

 > As requested, from
 >
 > (progn
 >     (frame--size-history)
 >     (switch-to-buffer "*frame-size-history*"))
 >
 > (But I did have to resize the frame to access what it generated.

I suppose you used the mouse to make the frame wider.  For example in this
excerpt

 > ConfigureNotify, PS=232x168, XS=282x168
 > xg_frame_resized, changed, PS=232x168, XS=282x168
 > change_frame_size_1, delayed, PS=232x168, XS=282x168
 > change_frame_size (5), TS=200x168~>250x168, TC=20x8~>25x8, NS=232x168~>282x168, IS=232x168~>282x168, MS=20x42 IH IV

you changed the width of the frame from 232 to 282 pixels leaving the
height at 168 pixels.  The next time you try it's probably simpler to
just maximize the frame.

 > And it did generate lots of "(emacs:228038): Gtk-CRITICAL **: 08:54:29.914: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed" messages.)

These come from GTK which cannot accommodate the Emacs menubar within
the 192 pixels you get initially.  It might need some 400 to 600 pixels
to stop complaining.  But I wonder how comes that you see "lots" of
them.  Below there is only one

 > xg_frame_set_char_size, visible, PS=192x168, XS=192x168

call that Emacs issues itself.  It probably means that GTK also
complains about the sizes mutter allots to the Emacs frame, something I
didn't really expect looking at the GTK code.  I must have been wrong.

 > ===============================================
 > Frame size history of #<frame  *Minibuf-1* 0x5babfd021e10>
 > x_create_frame_1 (5), TS=80x25~>800x525, NS=80x25~>816x525, IS=80x25~>816x525, MS=20x42 IH IV
 > gui_figure_window_size (5), TS=800x525~>800x756, TC=80x25~>80x36, NS=816x525~>816x756, IS=816x525~>816x756, MS=20x42 IH IV
 > scroll-bar-width (3), NS=816x756~>832x756, IS=816x756~>832x756, MS=100x105
 > scroll-bar-height (3), MS=100x105
 > menu-bar-lines (2), MS=100x105
 > x_create_frame_2 (0), MS=100x105

The crucial steps are these: Here we ask for a frame size of 832x756
pixels ...

 > xg_frame_set_char_size, invisible, PS=832x756, XS=832x756, DS=832x756
 > xg_frame_set_char_size (5), MS=20x42 IH IV
 > x_make_frame_visible
 > MapNotify, not hidden & not iconified, PS=832x756, DS=832x756
 > ConfigureNotify, PS=832x756, XS=192x168, DS=832x756

.. here mutter tells us that we get 192x168 pixels only ...

 > xg_frame_resized, changed, PS=832x756, XS=192x168
 > change_frame_size_1, delayed, PS=832x756, XS=192x168, DS=832x756
 > change_frame_size (5), TS=800x756~>160x168, TC=80x36~>16x8, NS=832x756~>192x168, IS=832x756~>192x168, MS=20x42 IH IV

... and here we accept what mutter tells us and orderly shrink our frame
to 16x8 columns and lines.  Yours is an exceptionally small frame.

 > tool-bar-lines (2), MS=100x105
 > xg_frame_set_char_size, visible, PS=192x168, XS=192x168
 > ConfigureNotify, PS=192x168, XS=192x168
 > xg_frame_resized, unchanged, PS=192x168, XS=192x168
 > ConfigureNotify, PS=192x168, XS=202x168

This is the initial configuration you see after adding the toolbar.
What follows are your manual resizings.

 > xg_frame_resized, changed, PS=192x168, XS=202x168
 > change_frame_size_1, delayed, PS=192x168, XS=202x168
 > change_frame_size (5), TS=160x168~>170x168, TC=16x8~>17x8, NS=192x168~>202x168, IS=192x168~>202x168, MS=20x42 IH IV
...

Thanks for the work, martin

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

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

 >> As a workaround you can also make an early init file (a file named
 >> ‘early-init.el’ in your ‘~/.emacs.d’ directory, see section 43.1.2 of
 >> the Elisp manual) containing
 >>
 >> (defun resize-me (frame)
 >>     (set-frame-size frame 42 90))
 >>
 >> (add-hook 'after-make-frame-functions 'resize-me)
 >>
 >> and see what happens.
 >
 > I did this.  There was already an early-init.el file present, and it
 > had just '(setq byte-compile-warnings '(cl-functions))' in it, which I
 > didn't think would matter.  I added the code you mention, and ran
 > emacs - still the same small window.

This is somewhat surprising because ISTR that some people used it to fix
the problem (they still see the small frame for a short moment).  Let's
try the following: In your early-init.el file put

(setq frame-size-history '(100))

(defun resize-me (frame)
   (set-frame-size frame 42 90))

(add-hook 'after-make-frame-functions 'resize-me)

start emacs -Q, then maximize the frame, do

(progn
   (frame--size-history)
   (switch-to-buffer "*frame-size-history*"))

and post the contents of that buffer.

 > I should mention that the small window only appears when emacs is
 > started from the launch bar.  If I run emacs directly from a terminal
 > window, a more normal size window appears.  (height 54, width 51) Not
 > what I'd call "exactly" normal, but better than the minuscule window I
 > was getting from the launch icon.

Interesting find.  Please put just

(setq frame-size-history '(100))

in your early-init.el file, start emacs -Q from the terminal window,
then maximize the frame, do

(progn
   (frame--size-history)
   (switch-to-buffer "*frame-size-history*"))

and post the contents of that buffer.

Many thanks, martin

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[John Hurst]

G'day Martin,

I've added the buffer outputs that you request in the context below.

They don't seem to be that informative?  Have I misinterpreted your instructions?

cheers,
-- John Hurst
--
-- ajh AT ajhurst DOT org                       ~ ~~~&#:
--  (mob 0407 569 292)              _..___  ---____@___H__
-- (local)  ajh.co                  |_____[_|_________[__]_
-- (global) ajhurst.org              oo oo  oo O--O--O o=o
--
-- Hurst's Third Law of telecommunications: 
--    ISPs are not as smart as spammers

On Mon, 21 Oct 2024, at 19:19, martin rudalics wrote:
>>> As a workaround you can also make an early init file (a file named
>  >> ‘early-init.el’ in your ‘~/.emacs.d’ directory, see section 43.1.2 of
>  >> the Elisp manual) containing
>  >>
>  >> (defun resize-me (frame)
>  >>     (set-frame-size frame 42 90))
>  >>
>  >> (add-hook 'after-make-frame-functions 'resize-me)
>  >>
>  >> and see what happens.
>  >
>  > I did this.  There was already an early-init.el file present, and it
>  > had just '(setq byte-compile-warnings '(cl-functions))' in it, which I
>  > didn't think would matter.  I added the code you mention, and ran
>  > emacs - still the same small window.
>
> This is somewhat surprising because ISTR that some people used it to fix
> the problem (they still see the small frame for a short moment).  Let's
> try the following: In your early-init.el file put
>
> (setq frame-size-history '(100))
>
> (defun resize-me (frame)
>    (set-frame-size frame 42 90))
>
> 
>
> start emacs -Q, then maximize the frame, do
>
> (progn
>    (frame--size-history)
>    (switch-to-buffer "*frame-size-history*"))
>
> and post the contents of that buffer.

Frame size history of #<frame  *Minibuf-1* - GNU Emacs at newport 0x6433d870ba00>

>
>  > I should mention that the small window only appears when emacs is
>  > started from the launch bar.  If I run emacs directly from a terminal
>  > window, a more normal size window appears.  (height 54, width 51) Not
>  > what I'd call "exactly" normal, but better than the minuscule window I
>  > was getting from the launch icon.
>
> Interesting find.  Please put just
>
> (setq frame-size-history '(100))
>
> in your early-init.el file, start emacs -Q from the terminal window,
> then maximize the frame, do
>
> (progn
>    (frame--size-history)
>    (switch-to-buffer "*frame-size-history*"))
>
> and post the contents of that buffer.

Frame size history of #<frame  *Minibuf-1* - GNU Emacs at newport 0x61089900b5b0>



>
> Many thanks, martin

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

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

 > I've added the buffer outputs that you request in the context below.
 >
 > They don't seem to be that informative?  Have I misinterpreted your instructions?

No.  I gave you silly instructions - emacs -Q ignores the early-init.el
file as well.  So please do the following:

(1) Rename your early-init.el file and your .emacs to something else.

(2) Make an early-init.el file that contains

(setq frame-size-history '(100))
(defun resize-me (frame)
    (set-frame-size frame 42 90))

(3) Run emacs without the -Q option so it reads your early-init.el file
and nothing else.

(4) You should now see the splash screen.  Maximize the frame, switch to
the *scratch* buffer and there do

(progn
     (frame--size-history)
     (switch-to-buffer "*frame-size-history*"))

(5) Copy the contents of the buffer *frame-size-history* so you can post
them here.

(6) In your early-init.el file remove everything but the

(setq frame-size-history '(100))

line.

(7) Start emacs without the -Q option from the terminal window.

(8) Repeat steps (4)-(5).

(9) Re-rename your early-init.el and your .emacs files to what they were
before step (1).  In particular, make sure that your early-init.el just
contains the

(setq byte-compile-warnings '(cl-functions))

line you mentioned earlier.

Thanks and sorry for the inconvenience, martin

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[John Hurst]

The two frame-size history files are

1) ---------------------------------------------------------------------
Frame size history of #<frame  *Minibuf-1* - GNU Emacs at newport 0x5a939cd6fe78>
x_create_frame_1 (5), TS=80x25~>800x525, NS=80x25~>816x525, IS=80x25~>816x525, MS=20x42 IH IV
gui_figure_window_size (5), TS=800x525~>1000x840, TC=80x25~>100x40, NS=816x525~>1016x840, IS=816x525~>1016x840, MS=20x42 IH IV
scroll-bar-width (3), NS=1016x840~>1032x840, IS=1016x840~>1032x840, MS=100x105
scroll-bar-height (3), MS=100x105
menu-bar-lines (2), MS=100x105
x_create_frame_2 (0), MS=100x105
xg_frame_set_char_size, invisible, PS=1032x840, XS=1032x840, DS=1032x840
xg_frame_set_char_size (5), MS=20x42 IH IV
x_make_frame_visible
MapNotify, not hidden & not iconified, PS=1032x840, DS=1032x840
ConfigureNotify, PS=1032x840, XS=1032x840, DS=1032x840
xg_frame_resized, unchanged, PS=1032x840, XS=1032x840
tool-bar-lines (2), MS=100x105
xg_frame_set_char_size, visible, PS=1032x840, XS=1032x840, DS=1032x840
ConfigureNotify, PS=1032x840, XS=1032x840, DS=1032x840
xg_frame_resized, unchanged, PS=1032x840, XS=1032x840
ConfigureNotify, PS=1032x840, XS=1920x977, DS=1032x840
xg_frame_resized, changed, PS=1032x840, XS=1920x977
change_frame_size_1, delayed, PS=1032x840, XS=1920x977, DS=1032x840
change_frame_size (5), TS=1000x840~>1888x977, TC=100x40~>188x46, NS=1032x840~>1920x977, IS=1032x840~>1920x977, MS=20x42 IH IV
set_window_configuration (4), MS=100x105 IH IV

2) -----------------------------------------------------------------------
Frame size history of #<frame  *Minibuf-1* - GNU Emacs at newport 0x5abd0a28b818>
x_create_frame_1 (5), TS=80x25~>800x525, NS=80x25~>816x525, IS=80x25~>816x525, MS=20x42 IH IV
gui_figure_window_size (5), TS=800x525~>1000x840, TC=80x25~>100x40, NS=816x525~>1016x840, IS=816x525~>1016x840, MS=20x42 IH IV
scroll-bar-width (3), NS=1016x840~>1032x840, IS=1016x840~>1032x840, MS=100x105
scroll-bar-height (3), MS=100x105
menu-bar-lines (2), MS=100x105
x_create_frame_2 (0), MS=100x105
xg_frame_set_char_size, invisible, PS=1032x840, XS=1032x840, DS=1032x840
xg_frame_set_char_size (5), MS=20x42 IH IV
x_make_frame_visible
MapNotify, not hidden & not iconified, PS=1032x840, DS=1032x840
ConfigureNotify, PS=1032x840, XS=200x175, DS=1032x840
xg_frame_resized, changed, PS=1032x840, XS=200x175
change_frame_size_1, delayed, PS=1032x840, XS=200x175, DS=1032x840
change_frame_size (5), TS=1000x840~>168x175, TC=100x40~>16x8, NS=1032x840~>200x175, IS=1032x840~>200x175, MS=20x42 IH IV
ConfigureNotify, PS=200x175, XS=192x168
xg_frame_resized, changed, PS=200x175, XS=192x168
change_frame_size_1, delayed, PS=200x175, XS=192x168
change_frame_size (5), TS=168x175~>160x168, NS=200x175~>192x168, IS=200x175~>192x168, MS=20x42 IH IV
tool-bar-lines (2), MS=100x105
xg_frame_set_char_size, visible, PS=192x168, XS=192x168
ConfigureNotify, PS=192x168, XS=192x168
xg_frame_resized, unchanged, PS=192x168, XS=192x168
ConfigureNotify, PS=192x168, XS=1920x977
xg_frame_resized, changed, PS=192x168, XS=1920x977
change_frame_size_1, delayed, PS=192x168, XS=1920x977
change_frame_size (5), TS=160x168~>1888x977, TC=16x8~>188x46, NS=192x168~>1920x977, IS=192x168~>1920x977, MS=20x42 IH IV
set_window_configuration (4), MS=100x105 IH IV
---------------------------------------------------------------------------

Now emacs still starts up with a small window (15x7), but it does seem to have read more of the .emacs file than before (perhaps all?).  But the GNU Emacs splash screen does not appear.


cheers,
-- John Hurst
--
-- ajh AT ajhurst DOT org                       ~ ~~~&#:
--  (mob 0407 569 292)              _..___  ---____@___H__
-- (local)  ajh.co                  |_____[_|_________[__]_
-- (global) ajhurst.org              oo oo  oo O--O--O o=o
--
-- Hurst's Third Law of telecommunications: 
--    ISPs are not as smart as spammers

On Wed, 23 Oct 2024, at 19:15, martin rudalics wrote:
>> I've added the buffer outputs that you request in the context below.
>  >
>  > They don't seem to be that informative?  Have I misinterpreted your 
> instructions?
>
> No.  I gave you silly instructions - emacs -Q ignores the early-init.el
> file as well.  So please do the following:
>
> (1) Rename your early-init.el file and your .emacs to something else.
>
> (2) Make an early-init.el file that contains
>
> (setq frame-size-history '(100))
> (defun resize-me (frame)
>     (set-frame-size frame 42 90))
>
> (3) Run emacs without the -Q option so it reads your early-init.el file
> and nothing else.
>
> (4) You should now see the splash screen.  Maximize the frame, switch to
> the *scratch* buffer and there do
>
> (progn
>      (frame--size-history)
>      (switch-to-buffer "*frame-size-history*"))
>
> (5) Copy the contents of the buffer *frame-size-history* so you can post
> them here.
>
> (6) In your early-init.el file remove everything but the
>
> (setq frame-size-history '(100))
>
> line.
>
> (7) Start emacs without the -Q option from the terminal window.
>
> (8) Repeat steps (4)-(5).
>
> (9) Re-rename your early-init.el and your .emacs files to what they were
> before step (1).  In particular, make sure that your early-init.el just
> contains the
>
> (setq byte-compile-warnings '(cl-functions))
>
> line you mentioned earlier.
>
> Thanks and sorry for the inconvenience, martin

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

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

 > The two frame-size history files are
 >
 > 1) ---------------------------------------------------------------------
 > Frame size history of #<frame  *Minibuf-1* - GNU Emacs at newport 0x5a939cd6fe78>

This should be the history for running emacs from the launch bar with an
early-init.el file and no .emacs file.

 > ConfigureNotify, PS=1032x840, XS=1032x840, DS=1032x840
[...]
 > ConfigureNotify, PS=1032x840, XS=1920x977, DS=1032x840
[...]
 > change_frame_size (5), TS=1000x840~>1888x977, TC=100x40~>188x46, NS=1032x840~>1920x977, IS=1032x840~>1920x977, MS=20x42 IH IV
 > set_window_configuration (4), MS=100x105 IH IV

This history is remarkable because I nowhere see that small frame size
in the ConfigureNotify events you got.  Hence, you should not have seen
any strange resizings and no GTK warnings either.  Am I right?

At the very end it makes a frame that is 188x46 characters large so IIUC
more than you asked for.  Does this size figure anywhere in one of your
resources?  Do you have some .emacs files around that emacs could have
read (it may look into several directories)?  What does

(frame-geometry)

tell for the frame you created here?

Obviously my suggestion to put

(setq frame-size-history '(100))
(defun resize-me (frame)
    (set-frame-size frame 42 90))

into the early-init.el file was silly again - a NOOP and nothing else.
What I should have asked you for was to put there

(setq frame-size-history '(100))
(defun resize-me (frame)
    (set-frame-size frame 90 42))
(add-hook 'after-make-frame-functions 'resize-me)

instead.  Can you try with that again?  In either case, it seems that
putting something in the early-init.el file might change things to the
better and we should pursue that.

 > 2) -----------------------------------------------------------------------
 > Frame size history of #<frame  *Minibuf-1* - GNU Emacs at newport 0x5abd0a28b818>

Now this should be the history for running emacs from a terminal window
reading your usual .emacs.

 > ConfigureNotify, PS=1032x840, XS=200x175, DS=1032x840

This is the usual unpleasant ConfigureNotify event ...

 > xg_frame_resized, changed, PS=1032x840, XS=200x175
 > change_frame_size_1, delayed, PS=1032x840, XS=200x175, DS=1032x840
 > change_frame_size (5), TS=1000x840~>168x175, TC=100x40~>16x8, NS=1032x840~>200x175, IS=1032x840~>200x175, MS=20x42 IH IV

... that allots us a 16x8 window ...

 > ConfigureNotify, PS=200x175, XS=192x168

... here we get another ConfigureNotify with about the same size ...

 > xg_frame_resized, changed, PS=200x175, XS=192x168
 > change_frame_size_1, delayed, PS=200x175, XS=192x168
 > change_frame_size (5), TS=168x175~>160x168, NS=200x175~>192x168, IS=200x175~>192x168, MS=20x42 IH IV
 > tool-bar-lines (2), MS=100x105
 > xg_frame_set_char_size, visible, PS=192x168, XS=192x168

... which we here use in our own request (this one should cause the
usual GTK warnings) ...

 > ConfigureNotify, PS=192x168, XS=192x168
 > xg_frame_resized, unchanged, PS=192x168, XS=192x168
 > ConfigureNotify, PS=192x168, XS=1920x977

... but here we miraculously get a ConfigureNotify event ...

 > xg_frame_resized, changed, PS=192x168, XS=1920x977
 > change_frame_size_1, delayed, PS=192x168, XS=1920x977
 > change_frame_size (5), TS=160x168~>1888x977, TC=16x8~>188x46, NS=192x168~>1920x977, IS=192x168~>1920x977, MS=20x42 IH IV

... that makes us resize the frame to 188x46 characters as above.  You
seem to confirm that here ...

 > Now emacs still starts up with a small window (15x7), but it does seem
 > to have read more of the .emacs file than before (perhaps all?).

... but can you explain the 188x46 size from your .emacs?

 > But
 > the GNU Emacs splash screen does not appear.

Do you see it normally when starting emacs?

martin

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[John Hurst]

G'day Martin,

I have to admit that I am getting out of my depth here.  I have written lots of emacs lisp programs, but not using many of the features that you talk about.  Hence I may get confused at times (:-(

Comments in text ...

On Sat, 26 Oct 2024, at 19:43, martin rudalics wrote:
>> The two frame-size history files are
>  >
>  > 1) 
> ---------------------------------------------------------------------
>  > Frame size history of #<frame  *Minibuf-1* - GNU Emacs at newport 
> 0x5a939cd6fe78>
>
> This should be the history for running emacs from the launch bar with an
> early-init.el file and no .emacs file.
>
>  > ConfigureNotify, PS=1032x840, XS=1032x840, DS=1032x840
> [...]
>  > ConfigureNotify, PS=1032x840, XS=1920x977, DS=1032x840
> [...]
>  > change_frame_size (5), TS=1000x840~>1888x977, TC=100x40~>188x46, 
> NS=1032x840~>1920x977, IS=1032x840~>1920x977, MS=20x42 IH IV
>  > set_window_configuration (4), MS=100x105 IH IV
>
> This history is remarkable because I nowhere see that small frame size
> in the ConfigureNotify events you got.  Hence, you should not have seen
> any strange resizings and no GTK warnings either.  Am I right?

Unfortunately, no.  Still same small window, and 4 GTK warnings

>
> At the very end it makes a frame that is 188x46 characters large so IIUC
> more than you asked for.  Does this size figure anywhere in one of your
> resources?  

No.  

> Do you have some .emacs files around that emacs could have
> read (it may look into several directories)?  

Not at the top level of $HOME.  There are backups in a directory $HOME/Archives, and in my Pictures and Videos directories.  But they are only minor variations on the $HOME/.emacs, and when I delete them, the behaviour remains.

> What does
>
> (frame-geometry)
>
> tell for the frame you created here?

I think it was
((outer-position 1214 . 79) (outer-size 220 . 300) (external-border-size 14 . 17) (outer-border-width . 0) (title-bar-size 0 . 32) (menu-bar-external . t) (menu-bar-size 192 . 25) (tab-bar-size 0 . 0) (tool-bar-external . t) (tool-bar-position . top) (tool-bar-size 192 . 41) (internal-border-width . 0))
but I had to resize the window to read it!
>
> Obviously my suggestion to put
>
> (setq frame-size-history '(100))
> (defun resize-me (frame)
>     (set-frame-size frame 42 90))
>
> into the early-init.el file was silly again - a NOOP and nothing else.
> What I should have asked you for was to put there
>
> (setq frame-size-history '(100))
> (defun resize-me (frame)
>     (set-frame-size frame 90 42))
> (add-hook 'after-make-frame-functions 'resize-me)
>
> instead.  Can you try with that again?  In either case, it seems that
> putting something in the early-init.el file might change things to the
> better and we should pursue that.

I presume I should make another frame after running 'emacs -Q'?  In any case, it made another frame the same small size.


>
>  > 2) 
> -----------------------------------------------------------------------
>  > Frame size history of #<frame  *Minibuf-1* - GNU Emacs at newport 
> 0x5abd0a28b818>
>
> Now this should be the history for running emacs from a terminal window
> reading your usual .emacs.
>
>  > ConfigureNotify, PS=1032x840, XS=200x175, DS=1032x840
>
> This is the usual unpleasant ConfigureNotify event ...
>
>  > xg_frame_resized, changed, PS=1032x840, XS=200x175
>  > change_frame_size_1, delayed, PS=1032x840, XS=200x175, DS=1032x840
>  > change_frame_size (5), TS=1000x840~>168x175, TC=100x40~>16x8, 
> NS=1032x840~>200x175, IS=1032x840~>200x175, MS=20x42 IH IV
>
> ... that allots us a 16x8 window ...
>
>  > ConfigureNotify, PS=200x175, XS=192x168
>
> ... here we get another ConfigureNotify with about the same size ...
>
>  > xg_frame_resized, changed, PS=200x175, XS=192x168
>  > change_frame_size_1, delayed, PS=200x175, XS=192x168
>  > change_frame_size (5), TS=168x175~>160x168, NS=200x175~>192x168, 
> IS=200x175~>192x168, MS=20x42 IH IV
>  > tool-bar-lines (2), MS=100x105
>  > xg_frame_set_char_size, visible, PS=192x168, XS=192x168
>
> ... which we here use in our own request (this one should cause the
> usual GTK warnings) ...
>
>  > ConfigureNotify, PS=192x168, XS=192x168
>  > xg_frame_resized, unchanged, PS=192x168, XS=192x168
>  > ConfigureNotify, PS=192x168, XS=1920x977
>
> ... but here we miraculously get a ConfigureNotify event ...
>
>  > xg_frame_resized, changed, PS=192x168, XS=1920x977
>  > change_frame_size_1, delayed, PS=192x168, XS=1920x977
>  > change_frame_size (5), TS=160x168~>1888x977, TC=16x8~>188x46, 
> NS=192x168~>1920x977, IS=192x168~>1920x977, MS=20x42 IH IV
>
> ... that makes us resize the frame to 188x46 characters as above.  You
> seem to confirm that here ...
>
>  > Now emacs still starts up with a small window (15x7), but it does seem
>  > to have read more of the .emacs file than before (perhaps all?).
>
> ... but can you explain the 188x46 size from your .emacs?

No, those values just do not appear.
>
>  > But
>  > the GNU Emacs splash screen does not appear.
>
> Do you see it normally when starting emacs?

Yes, if I explicitly load my .emacs and eval-buffer that!

>
> martin


cheers,
-- John Hurst
--
-- ajh AT ajhurst DOT org                       ~ ~~~&#:
--  (mob 0407 569 292)              _..___  ---____@___H__
-- (local)  ajh.co                  |_____[_|_________[__]_
-- (global) ajhurst.org              oo oo  oo O--O--O o=o
--
-- Hurst's Third Law of telecommunications: 
--    ISPs are not as smart as spammers

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

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

 > I have to admit that I am getting out of my depth here.  I have
 > written lots of emacs lisp programs, but not using many of the
 > features that you talk about.  Hence I may get confused at times (:-(

In the area of Emacs/WM interactions I'm confused all the time.

 >> This history is remarkable because I nowhere see that small frame size
 >> in the ConfigureNotify events you got.  Hence, you should not have seen
 >> any strange resizings and no GTK warnings either.  Am I right?
 >
 > Unfortunately, no.  Still same small window, and 4 GTK warnings

This would mean that the frame size history would lie.  Please repeat
the experiment:

(1) The early-init.el file has to contain

(setq frame-size-history '(100))
(defun resize-me (frame)
   (set-frame-size frame 90 42))
(add-hook 'after-make-frame-functions 'resize-me)

and there should be no .emacs file, no resources for Emacs.

(2) Run emacs from the launch bar.

(3) Maximize the emacs frame and evaluate (frame--size-history).

(4) Post the contents of the *frame-size-history* buffer here.

 >> At the very end it makes a frame that is 188x46 characters large so IIUC
 >> more than you asked for.  Does this size figure anywhere in one of your
 >> resources?
 >
 > No.

Do you see a mode line and a minibuffer window in that small frame.
Could you post a screenshot of it?

 > I think it was
 > ((outer-position 1214 . 79) (outer-size 220 . 300) (external-border-size 14 . 17) (outer-border-width . 0) (title-bar-size 0 . 32) (menu-bar-external . t) (menu-bar-size 192 . 25) (tab-bar-size 0 . 0) (tool-bar-external . t) (tool-bar-position . top) (tool-bar-size 192 . 41) (internal-border-width . 0))
 > but I had to resize the window to read it!

What do (frame-width) and (frame-height) get you for that frame?

Thanks, martin

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

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

 > Sorry I haven't responded sooner!  However, the heat has gone off the
 > problem, because I now find that if I invoke emacs from the command
 > line, rather than the launch pad, it opens quite normally, and in line
 > with the expected behaviour from the .emacs file.  So it is quite
 > useable again!

Thanks.  We could add the following text to etc/PROBLEMS.

*** Gnome desktop does not respect frame size specified in .Xresources

This has been observed when running a GTK+ build of Emacs 29 from the
launch pad on Ubuntu 24.04 with mutter as window manager.  The problem
can be resolved by running Emacs from the command line instead.

Do you think it describes the problem well enough?  Eli WDYT?

martin

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[John Hurst]

Yep.  That captures it well.  Thanks.

cheers,
-- John Hurst
--
-- ajh AT ajhurst DOT org                       ~ ~~~&#:
--  (mob 0407 569 292)              _..___  ---____@___H__
-- (local)  ajh.co                  |_____[_|_________[__]_
-- (global) ajhurst.org              oo oo  oo O--O--O o=o
--
-- Hurst's Third Law of telecommunications: 
--    ISPs are not as smart as spammers

On Sat, 16 Nov 2024, at 19:59, martin rudalics wrote:
>> Sorry I haven't responded sooner!  However, the heat has gone off the
>  > problem, because I now find that if I invoke emacs from the command
>  > line, rather than the launch pad, it opens quite normally, and in line
>  > with the expected behaviour from the .emacs file.  So it is quite
>  > useable again!
>
> Thanks.  We could add the following text to etc/PROBLEMS.
>
> *** Gnome desktop does not respect frame size specified in .Xresources
>
> This has been observed when running a GTK+ build of Emacs 29 from the
> launch pad on Ubuntu 24.04 with mutter as window manager.  The problem
> can be resolved by running Emacs from the command line instead.
>
> Do you think it describes the problem well enough?  Eli WDYT?
>
> martin

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

[Eli Zaretskii]

> Cc: 73244@debbugs.gnu.org
> Date: Sat, 16 Nov 2024 09:59:21 +0100
> From:  martin rudalics via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
>  > Sorry I haven't responded sooner!  However, the heat has gone off the
>  > problem, because I now find that if I invoke emacs from the command
>  > line, rather than the launch pad, it opens quite normally, and in line
>  > with the expected behaviour from the .emacs file.  So it is quite
>  > useable again!
> 
> Thanks.  We could add the following text to etc/PROBLEMS.
> 
> *** Gnome desktop does not respect frame size specified in .Xresources
> 
> This has been observed when running a GTK+ build of Emacs 29 from the
> launch pad on Ubuntu 24.04 with mutter as window manager.  The problem
> can be resolved by running Emacs from the command line instead.
> 
> Do you think it describes the problem well enough?  Eli WDYT?

SGTM, assuming we think the description is accurate.

Thanks.

bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41

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

 > SGTM, assuming we think the description is accurate.

Pushed to the release branch.

martin