Page 1 of 1

DEVS: Emacs 28 in current MX-23.5_x64 problematic

Posted: Wed Jan 29, 2025 1:27 am
by zimbodel
To developers: packager

Is there any chance to have Emacs Ver 29 in the repositories soon ?
I ask as maybe it is scheduled to be included.
Reason below.......

I confirmed from gnu emacs developers that Emacs Version 28 has issues, and they recommend immediately upgrading to Version 29.

Version 28 will crash under certain circumstances, but might work for some users.
Emacs 28 as what is the highest available in Mx23.5 apt repositories crashes on some of my clients.
Installed new on two clients. Emacs crashes on one but not the other. Absolutely identical fresh installations of MX23.5 from same DVD.
I activated backports and testing, but there was no emacs 29 in development, so I need to compile from scratch.

Here is the advice from GNU Emacs Dev after my bug submission.
Their response is at the bottom of the bug report.

=======================================================================================
How do I resolve this ?
Brand new install of MX23.5

Terminal output:
---------------

$ emacs

(emacs:38851): Gtk-WARNING **: 13:22:04.395: Failed to parse
/home/noshow/.config/gtk-3.0/settings.ini: Key file does not start
with a group
X protocol error: BadMatch (invalid parameter attributes) on protocol
request 139
When compiled with GTK, Emacs cannot recover from X disconnects.
This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221
For details, see etc/PROBLEMS.
Fatal error 6: Aborted
Backtrace:
emacs(+0x1536c3)[0x561329bfe6c3]
emacs(+0x48835)[0x561329af3835]
emacs(+0x48d25)[0x561329af3d25]
emacs(+0x47d9e)[0x561329af2d9e]
emacs(+0x106e8a)[0x561329bb1e8a]
emacs(+0x106f0d)[0x561329bb1f0d]
/lib/x86_64-linux-gnu/libX11.so.6(_XError+0x11b)[0x7f38d462d9eb]
/lib/x86_64-linux-gnu/libX11.so.6(+0x43657)[0x7f38d462a657]
/lib/x86_64-linux-gnu/libX11.so.6(+0x436f5)[0x7f38d462a6f5]
/lib/x86_64-linux-gnu/libX11.so.6(_XReply+0x1cd)[0x7f38d462b84d]
/lib/x86_64-linux-gnu/libX11.so.6(XParseColor+0x1ec)[0x7f38d461bd9c]
emacs(+0x10c979)[0x561329bb7979]
emacs(+0x11c28e)[0x561329bc728e]
emacs(+0x10054c)[0x561329bab54c]
emacs(+0x101e10)[0x561329bace10]
emacs(+0x103fd8)[0x561329baefd8]
emacs(+0x6a642)[0x561329b15642]
emacs(+0x82004)[0x561329b2d004]
emacs(+0x7c756)[0x561329b27756]
emacs(+0x84348)[0x561329b2f348]
emacs(+0x8223d)[0x561329b2d23d]
emacs(+0x7f728)[0x561329b2a728]
emacs(+0x848ce)[0x561329b2f8ce]
emacs(+0x861c6)[0x561329b311c6]
emacs(+0x9111c)[0x561329b3c11c]
emacs(+0x6aee4)[0x561329b15ee4]
emacs(+0x94dd1)[0x561329b3fdd1]
emacs(+0x951e9)[0x561329b401e9]
emacs(+0x954f8)[0x561329b404f8]
emacs(+0x1aed2a)[0x561329c59d2a]
emacs(+0x1b811b)[0x561329c6311b]


Emacs 28.2 is known to exhibit this problem. Please upgrade to Emacs
29.

===========================================================================

Re: DEVS: Emacs 28 in current MX-23.5_x64 problematic

Posted: Wed Jan 29, 2025 2:19 am
by zimbodel
Update:
I can confirm that the GNU devs advice works. Compiled emacs 29.5 from scratch and it works perfectly.
Best is to blacklist emacs 28.x in apt.

Re: DEVS: Emacs 28 in current MX-23.5_x64 problematic

Posted: Wed Jan 29, 2025 3:10 am
by asqwerth
Mods, I think this should be in the package requests section.

Re: DEVS: Emacs 28 in current MX-23.5_x64 problematic

Posted: Wed Jan 29, 2025 4:08 am
by Eadwine Rose
Moved.

Re: DEVS: Emacs 28 in current MX-23.5_x64 problematic

Posted: Sat Feb 01, 2025 1:35 pm
by timkb4cq
Emacs 29.4 is available in bookworm backports, easily installed with the MX Package Installer.

Re: DEVS: Emacs 28 in current MX-23.5_x64 problematic

Posted: Sat Feb 01, 2025 3:49 pm
by DukeComposed
timkb4cq wrote: Sat Feb 01, 2025 1:35 pm Emacs 29.4 is available in bookworm backports, easily installed with the MX Package Installer.
Thanks for pointing this out; I think I settled on 28.2 for my MX-23 machines after doing a fair bit of experimentation trying to get the Emacs 29 flatpak working with Doom Emacs with limited success. The flatpak worked, but it has limited utility if you expect to invoke a highly customized configuration or operating environment, which Doom certainly is.

Upgrading from 28.2 to 29.4 with the backport packages was a matter of just recompiling the packages with "doom sync -e" and that was about it.