Your message dated Fri, 25 Sep 2026 10:01:31 -0400
with message-id <[email protected]>
and subject line Re: Bug#1146499: Acknowledgement (firefox 155.0: Cannot type
various non-ASCII characters)
has caused the Debian Bug report #1146499,
regarding firefox 155.0: Cannot type various non-ASCII characters
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1146499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1146499
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: firefox
Version: 155.0-1
Severity: important
On my system, I have various XCompose definitions, such as
<Multi_key> <apostrophe> <a> for á
<Multi_key> <asterisk> <D> for Δ
<Multi_key> <E> <equal> for €
Multi_key> <plus> <minus> for ±
<Multi_key> <minus> <n> for –
These all worked in Firefox 154.0.1-1, but no longer work in 155.0-1,
whether in the address bar, search bar, or a textarea in a page.
I've tested this with fresh profiles, extracting
firefox_154.0.1-1_amd64.deb to a temporary directory and running
./usr/lib/firefox/firefox-bin --profile /tmp/x/ff/profile --new-instance
(which runs 154, confirmed via Help > About Firefox) versus
/usr/lib/firefox/firefox-bin --profile /tmp/x/ff/profile2 --new-instance
(which runs 155, confirmed via Help > About Firefox).
On the other hand, <Multi_key> <P> <o> <o> that I have for 💩 does still
work.
Copy-pasting the characters does still work.
I don't know if this is specific to Debian or exists upstream. If the
latter, please forward it there. 🙂
I set the severity on this report as "important", since being able to
enter characters like `á` or `€` from the keyboard is at the least a
major effect on the usability of the package.
--- End Message ---
--- Begin Message ---
Version: 156.0-1
Seems to be working again in 156.0-1. Presumably it was fixed upstream.
--- End Message ---
