Your message dated Sun, 21 Jun 2026 20:04:11 +0800
with message-id <[email protected]>
and subject line Re: Bug#1140411: kitty: Kitty 0.47.3-1 doesn't show my duck
anymore: 🦆
has caused the Debian Bug report #1140411,
regarding kitty: Kitty 0.47.3-1 doesn't show my duck anymore: 🦆
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.)
--
1140411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140411
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kitty
Version: 0.47.0-3
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
I use a rather quircky duck in my prompt as a separator and it suddenly stopped
working for one reason or the other. I first thought it had to do with my font,
so I did all the things you would think of:
fc-list :family="CommitMono"
sudo fc-cache -fv
fc-cache -fv
I also grabbed a newer version of CommitMono, with these settings:
{
"alternates" : {
"cv01" : false,
"cv02" : false,
"cv03" : false,
"cv04" : false,
"cv05" : false,
"cv06" : false,
"cv07" : false,
"cv08" : false,
"cv09" : false,
"cv10" : false,
"cv11" : false
},
"features" : {
"ss01" : true,
"ss02" : true,
"ss03" : true,
"ss04" : true,
"ss05" : true
},
"italic" : false,
"letterSpacing" : 0,
"lineHeight" : 1,
"weight" : 400
}
To no avail.
When you have Commit Mono installed (or perhaps any other nerdfont) from
https://commitmono.com/ and open the Unicode menu (ctrl+shift+u on my system)
and you search by name (f2) for duck and select the first option, U+1f986, you
would see a nice little ducky.
With kitty 0.47.3-1 you no longer have that. It becomes a small red-ish dot.
I reverted back to kitty 0.47.0-3 and the duck re-appears.
I marked the bug as important, as I am a bit cautious as I don't want to bump
it to serious, although I am convinced it might be a serious bug.
Cheers,
Wesley
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (900, 'unstable'), (500, 'testing'), (100, 'experimental'), (10,
'stable-updates'), (10, 'stable-security'), (10, 'oldstable-updates'), (10,
'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 7.0.12+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages kitty depends on:
ii kitty-shell-integration 0.47.3-1
ii kitty-terminfo 0.47.3-1
ii libc6 2.42-16
ii libcairo2 1.18.4-3+b1
ii libdbus-1-3 1.16.2-5+b1
ii libfreetype6 2.14.3+dfsg-1
ii libharfbuzz0b 12.3.2-2+b2
ii liblcms2-2 2.19.1-1
ii libpng16-16t64 1.6.58-1
ii libpython3.13 3.13.14-1
ii libssl3t64 3.6.3-1
ii libwayland-client0 1.25.0-2
ii libx11-6 2:1.8.13-1
ii libx11-xcb1 2:1.8.13-1
ii libxcursor1 1:1.2.3-1+b2
ii libxkbcommon-x11-0 1.13.1-1
ii libxkbcommon0 1.13.1-1
ii libxxhash0 0.8.3-2+b2
ii python3 3.13.9-3+b1
ii python3.13 3.13.14-1
ii zlib1g 1:1.3.dfsg+really1.3.2-3
Versions of packages kitty recommends:
ii kitty-doc 0.47.3-1
ii libcanberra0t64 [libcanberra0] 0.30-12.2+b2
Versions of packages kitty suggests:
ii fonts-noto-color-emoji 2.051-1
ii imagemagick 8:7.1.2.25+dfsg1-2
ii imagemagick-7.q16 [imagemagick] 8:7.1.2.25+dfsg1-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Done: Maytham Alsudany <[email protected]>
Version: 0.47.4-1
On Fri, 2026-06-19 at 18:17 -0400, Wesley Schwengle wrote:
> Package: kitty
> Version: 0.47.0-3
> Severity: important
> X-Debbugs-Cc: [email protected]
>
> Dear Maintainer,
>
> I use a rather quircky duck in my prompt as a separator and it suddenly
> stopped
> working for one reason or the other.
[...]
I've confirmed that this is fixed as of kitty 0.47.4, which has just
been uploaded.
> I marked the bug as important, as I am a bit cautious as I don't want to bump
> it to serious, although I am convinced it might be a serious bug.
No, it's not serious, as it is not a policy violation and does not
seriously impede you're ability to use kitty (you can still run
commands).
--
Maytham
signature.asc
Description: This is a digitally signed message part
--- End Message ---
