unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David McCracken <davidm@ixont.com>
To: 71162@debbugs.gnu.org
Subject: bug#71162: In Linux Emacs 27.1 rejects custom toolbar icons
Date: Sun, 26 May 2024 13:54:07 -0700	[thread overview]
Message-ID: <46e97c25-b7e7-4042-9a97-bc277816a1de@ixont.com> (raw)
In-Reply-To: <e197ea19-3f58-4ece-a043-d994a5bfaef7@ixont.com>

I decided that I could test 26.3 on the newer Ubuntu by copying some of 
the Emacs files from the other computer. I copied the emacs executable 
(located in /etc/alternatives/emacs pointed to by /usr/bin/emacs 
symlink) and recursively copied /usr/share/emacs/26.3 to 
/usr/share/emacs. I didn't change /usr/share/emacs/site-lisp or any of 
the files in /etc/emacs or usr/lib/emacs. Directly invoking the 26.3 
executable revealed that it wanted 
/usr/lib/x86_64-linux-gnu/libotf.so.0. The 27.1 installation has only 
libotf.so.1 and libotf.so.1.0.0, so I copied libotf.so.0 into the 
directory. Then 26.3 ran and correctly displayed my toolbar icons 
located in ~/icons. Unlike the 27.1 bug report, in this case the 
reporter does not show Recent messages Invalid XPM3 file.

To investigate whether the problems are caused by libotf.so, I copied 
libotf.so.0 over libotf.so.1 but then emacs 27.1 complained about a 
missing symbol definition. I did the inverse, copying libotf.so.1 over 
libotf.so.0. Emacs 26.3 was able to run with this. It continued to show 
my icons and not report the files as invalid. Therefore, the root of the 
problems is either in the emacs executable or /usr/share/emacs/27.1.

In my Windows computer with Emacs 29.1 the bug reporter does not 
complain about my icon files. The name of the char array in the xpm file 
seems to be immaterial. I tried many alternatives to * filespec, 
including simply filespec and blank, and nothing changed the 27.1 bug 
report and failure to display the icons. I tested these alternatives in 
the Windows computer with Emacs 29.1 and they didn't change anything. I 
think this is essentially a comment, especially considering that 
definining an unnamed array is not legal in C. Even if this were a 
problem, it would not account for why Linux-Emacs 27.1 rejects its own 
xpm files if located anywhere but its own images directory.

Although I would like to help get to the bottom of these problems, I 
would still like to know how to install an Emacs downrev in Linux. It is 
easy in Windows since all versions are available in zip files that I can 
unzip anywhere I want.







  parent reply	other threads:[~2024-05-26 20:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24  4:08 bug#71162: bug-gnu-emacs@gnu.org David McCracken
2024-05-24  6:15 ` Eli Zaretskii
     [not found]   ` <9002e131-3466-4a73-a88c-bad260e5b886@ixont.com>
2024-05-25  6:09     ` Eli Zaretskii
2024-05-25 19:08       ` David McCracken
2024-05-26  4:44         ` Eli Zaretskii
2024-05-25 20:04   ` David McCracken
2024-05-27  4:16   ` David McCracken
2024-05-27 11:20     ` bug#71162: In Linux Emacs 27.1 rejects custom toolbar icons Eli Zaretskii
2024-05-25 10:42 ` bug#71162: bug-gnu-emacs@gnu.org Benjamin Riefenstahl
2024-05-26 20:54 ` David McCracken [this message]
2024-05-28  3:56 ` bug#71162: Linux-Emacs > 26 icons David McCracken

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46e97c25-b7e7-4042-9a97-bc277816a1de@ixont.com \
    --to=davidm@ixont.com \
    --cc=71162@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).